Sorry for the flurry of releases… this changes the input of the ‘data source’ field, so you don’t have to strip the http from the beginning. If you’ve already set jNag up and you’re upgrading your client it should handle this automatically.
For my day job I work for a specialist engineering company, tyrrell systems ltd who work in the field of intelligent building management systems. One of the systems we spend a lot of time with is Obsys, from North Building technologies. Basically this software allows wide ranging integration of building systems (air conditioning, intruder detection, […]
So, several people on the forum have pointed out that the zip for 0.75 didn’t actually include the server component or the instructions for installation. Sorry about that, I’ve now updated the download to include those. [download id=”7″ format=”1″]
I was going to wait until the end of the week, but I don’t think I’m going to add anything else new before then so here it is (click the ‘read more link for the download)
I’ve had a few people getting in touch through the ‘comments’ and ‘contact me’ sections of this site, but starting from tomorrow (or maybe the day after depending on my availability) I’ll be launching a forum so I can answer queries more easily and solicit suggestions on new features to add.
So, I’ve starting looking into adding advertising into jNag to cover server costs etc and perhaps cover the $99 fee that I’d need to pay to develop an iPhone app. The latest version in the git repository has this code added, but I’m unsure whether to leave it in there or not.
Since I’ve now got a github page where you can download the latest and greatest changes to jNag in between releases, I thought I’d start posting a little summary of those changes so you know what’s coming up in the next version. here’s the changes I’ve made in the last couple of days:
So, here’s a quick insight into what I’m working on for the next release. Rather than rush this out in a couple of days like I have been doing, I’m planning on taking my time with this and maybe pushing it out at the end of next week.
The current version does not support HTTPS (although it’s easy enough to hack in). I’m releasing a fix for this later on this evening (when I get home from work in an hour or so) Thanks to Hubert de Heer for reporting this issue, and Christian Kreidl for reporting and independently fixing the problem as […]
Not much more to say really… the current android client is just a straight copy of the web client, so no device notifications as yet. Search for it on the market!