Last week Chandler hit a milestone that we’ve been calling “Preview”. Preview is a coordinated release of the Chandler Desktop application, the Chandler Server (Cosmo), and a free sharing service, Chandler Hub. Chandler Server not only provides calendar and general item sharing services for Chandler Desktop, it also includes an AJAXy UI that implements a decent slice of the functionality of the desktop. We’ll be working to increase the coverage of that slice over time. Chandler Hub is running on top of the Chandler Server software, and anyone who wants to could run a similar service by grabbing the code and installing it.
Over the years, many people have said to me, “let me know when Chandler is usable”. This is your notice that we now consider Chandler usable. The release numbers on the desktop and server are at 0.7 – so we are not saying that Chandler is feature complete, but the current features are usable. I’ve been using the calendar features for quite some time.
There are some important resources that you should take some time to look at, including:
- A revamped vision document
- A “Getting Started Guide“
- Screenshots
- Screencasts
I’d also like to highlight some of the interesting work that has been going on in the various Chandler projects: Brian Moseley has written a few blog posts about the work that he’s done using REST/Atom to provide services for the AJAX Web UI of Chandler Server. Jared Rhine has written a thorough and thoughtful post about what it means to be/run an “open service”. The OSAF QA team has built Windmill, a great tool for testing AJAXy web applications.
There is plenty of stuff going on in the various projects, and a lot of things left to do. We’d love to work with designers, developers, testers, and writers to bring Chandler to its fullest potential.
I’m simply awed by the Chandler Desktop processor and memory requirements!
Pentium(R) 4 2.8 GHz
Min 512 MB
Recommended 1 GB
Isaac,
I think we recommend approximately a 2.0 GHz P4 and that model of P4 has been available from Intel since April of 2002 so I don’t think we are asking for Gamer-quality gear 🙂
Memory on the other hand … we are a PIM and as such fall prey to the sins of memory consumption like most others.
I was so blinded by the memory requirements that I completely misread the recommended processor.
Yup, OSAF hasn’t done much with memory use. We know that’s something we need to work on before 1.0. For now, we’re hoping potential users will overlook the footprint and give us feedback on the feature set.
Memory use is not good. What’s worse, Chandler is a CPU hog. I know my Dell 600m is geting a bit on the old side but we’re talking about a PIM. Can’t use it with the CPU getting pegged most the time by pythonw. A rewrite to a lighter footprint is in order.