0.0.5 Released

I just released Foxkit 0.0.5, you can get the source from the Google Code Page.

Right before the release I was working on trying to get windows/tabs opened by Javascript to work, but the changes were getting to the point of creating a lot of extra complexity and even then it was causing other functionality to result in seg faults so I ended up just reverting all the changes. Later I'll have to think some more about a better design that'll be able to handle this situation (unfortunately signals can't have a return value which I had forgotten).

Depending on how long that takes it might just be a release just on it's own, or if it's easier than I expect I might also work on trying to get error pages to work properly then release 0.0.6. For 0.1.0 I wanna get both the javascript tabs/windows working properly and error pages working okay, along with a couple more things I think up along the way.

Edit: Finishing the cmake files so that it'll actually install would be a good thing to also do :P Shouldn't really be that hard, just take some time looking through the documentation or some other project's files at worst.

New Blog, Foxkit's current status

It has been quite a while since I last made a release of Foxkit (KDE-Apps page, Google Project's Download Page), but the Git repository is still alive! I've done quite a bit of development since the 0.0.2 release, including adding support for Cookies (and the start of support for multiple cookie jars), better tab handling, massive amount of code cleanups, and lots of other things I long since forgot.

I'm hoping to release the next version of Foxkit sometime next week, probably with a 0.0.5 version number. So far I've done a pretty lousy job of following my roadmap, but hopefully in the future I'll be more flexible with it, and maybe try to switch to time-based releases (maybe once a month?). I've decided the only show stopper for the next release will be to have Foxkit's cookies stored in a better place than /dev/shm (generally a tmpfs filesystem on Linux... trashed when the system reboots), theres probably a KDE directory that stuff like thats supposed to go into. After this next release I'm wanting to add support to query Solid to check to see if the network is up or not, as well as add error pages (silent errors are evil!).

Edit: Just commented the change to use KStandardDirs::locateLocal("appdata", "cookies.db"); instead of /dev/shm/cookies.db :P