2009-05-22 21:19:34
I missed the last week's edition, so this has a little more scope, but I've been pretty slammed at work so not much has been going on.
These past two weeks have brought a number of bugfixes in the experimental branch, but the main improvements were the addition of the state change hook (which will eventually be used for integration with other readers, like Google Reader), and the start of the validating modular configuration code (in the exp-cfg branch). I'm very pleased with how the new configuration code is going and it should offer much more informative configuration error messages and is much stricter so that strange crashes don't come from strange corner cases in the config.
Unfortunately, I've gone down some developer blind alleys in the past week. The first of which is that I finally got around to determining just how difficult integrating with GReader is going to be. As a result, I'm going to have to delay that until sometime after 0.7.0 because the update is already going to add enough features with their corresponding bugs that I'd like to get it out there. I am, however, going to add some changes that make GReader integration less difficult before the release.
The second is getting Canto to work on FreeBSD. I'm a Linux user/developer by
choice and by trade, but I'm never averse to expanding Canto's range to similar
operating systems. With this, I struggled for a little while, and ended up
submitting a bug in the Python tracker about
it because the WINDOW taken from the Python object is somehow not valid.
I'm not sure if the Python tracker is really the best place for it, but I'm
hoping that someone who knows a lot more about Python internals will take a look
and help me out.
Any experienced FreeBSD programmers that want to take a look at it are certainly welcome to take a look as well, my experience with FreeBSD is very limited. I still hope that any changes won't be have to be very invasive so I can add FreeBSD support without adding much complexity.
Have fun! Submit bugs!