Two months already since I made iObserve free, and a month since I started to work in my new startup. And a month without any code! How bizarre! Sorry guys, but as you may have guessed, I made no progress at all on the iObserve front. In fact, during the last month I had only my 7-years old MacBook Pro. Tough to run Xcode and code confortably with it. Now that I received the latest high-end Retina, things have much improved!

Here is the situation at onekiloparsec's:

  • iObserve 1.5 is still ongoing. Sky maps coming, along with various bugfixes coming, especially that factor 15 for Right Ascensions when entering coordinates manually. I was planning to put in place an update mechanism outside the MacAppStore, but given the time it takes, I'll skip it for now. So expect a regular update in the MAS. I can't make plans for when, but this is definitely on top of the list.
  • I've received a request to support PixInsight XISF in QLFits. That's very interesting, as I didn't know about before. I'll have to check that. Love new stuff.
  • KPCTabsControl has been updated to play better with AutoLayout projects, because of a developer request. Great spirit among developers around the world; open source can be really cool sometimes.
  • SwiftAA is stucked in between version 1.0 and 2.0. I really wish I could finish this soon. This is key for the future, but I am stuck on how I should translate pure C++ style / syntax in the most useful / modern Swift style and syntax. Life can be hard sometimes. ;-)
  • Because of SwiftAA is stuck, so is iObserve 2 too... But anyway, this new app depends on the development of arcsecond.io. And I am wondering I could write things in Swift. Probably not on the server side (even if it is possible right now).

But you know what? I've been thinking a lot about arcsecond.io lately. I regularly receive emails from the backend about this or this not working well (for instance, duplicate Observatories, yes, I look at you, Crete). I am all aware of it! And I need to do something about it, definitely. Enough said for now. More on that later.

Most welcome to send comments and feedbacks if you can help or discuss. Stay tuned, as always.