"If you define cowardice as running away at the first sign of danger, screaming and tripping and begging for mercy, then yes, Mr. Brave man, I guess I'm a coward."
- Jack Handy, Deep Thoughts
Monday, August 21, 2006
OK, so what's the status of Bloo version 1.00 release candidate 1?
Well, I'm rewriting Bloo.
Ha ha ha! Just kidding. I'm not rewriting it. But I am re-factoring the heck out of it right now. Here are the high points
- Time - I'm standardizing the internal date and time storage to GMT. As a coder I'm kind of hooked on platonic ideals; GMT is way more platonic than server time. I want Bloo to be easy to configure even if the server is on the space statio. And of course, the time will be adjusted to local time on output, but by selecting a timezone - away with the klunky "hours different from GMT" setting!
- Optimization - The current version of Bloo loads in its entirety every time you bring it up. The new version has a much more intelligent load manager and only loads the SnapOn packages it needs. Which brings me to . . .
- SnapOns - I departed awhile ago from a philosophy that I am now getting back to. In Bloo, everything is supposed to be a SnapOn. Everything. Well, in the current version that's not exactly true. But the new version loads every aspect of the system as a SnapOn package. This means the core SnapOn packages (Post, PostAdmin, Comment, etc) without which the system won't run, and also the extension SnapOn packages (BlooQuote, the spell checker, Simple Human Check - these are what are often referred to as simply "SnapOns" because they "Snap On" to Bloo core. But they are no different than the core SnapOns, except for the fact that they are loaded selectively). And Themes will be SnapOn packages too. Everything's a SnapOn, darnit. Which brings me to . . .
- SnapOn Servers - this is perhaps the most exciting part of the new release, from a user point of view. Currently, to get new Bloo functionality you have to wait for me to release a new version. But when this version comes out I will enable the ability for Bloo blogs to also be SnapOn Servers - this means that any kind of Extension or Theme SnapOn can be detected from a SnapOn server and installed on a user's blog. This is also exciting for me because the first SnapOn server will be this blog - and that means I'll be able to deliver new functionality more "on the fly" than ever before. And this is a very "Web 2.0" thing to do . . .
Of course, all of this is taking time. But I'm very excited about this beta release, leading up to the first production release of Bloo. I plan on expanding the number of Bloo test sites as well.
Watch me for the changes . . .