A couple of months ago, I announced the creation of an Open Source Calendar Component for Flex 2.
Despite saying at the time that it’d be ready when its ready, I’ve been pretty much inundated with requests asking whether its ready, when it would be ready, why it wasn’t ready or could an early version be made ready. I nearly added the word ready to my email spam filter.
However, during the intervening time, something else happened; my thinking around what ready meant actually changed – I realised that it wasn’t just a Calendar Component we were building, but a fully fledged Scheduling Framework. I also realised that saying whether it was ready or not was not really my decision.
You see, a framework like this cannot just be built with no regards to how it will be used. We’ve built some samples which we’ll be releasing alongside the framework, but it’ll be the real-life applications that will truly test-drive the APIs, the scalability and the performance of the framework.
So, I’ve decided the framework won’t be released when its ready after all; it’ll be released when its nearly ready. And nearly is within the next couple of weeks, hopefully by the time I’m presenting at Max 2006.
It has also been decided that this early-release version of the framework will be released on Adobe Labs.
So, keep an eye on my blog and I’ll let you know more soon. In the meantime, here’s another screenshot of the Scheduling Framework in use.