So what did I say to the friendly bank teller about last night's storm? "Oh, we're not getting anything"? Well, at least it was the easy-to-shovel kind of snow.
I started using Chandler
0.6 last week. Previously, I've used pen on my Futurama wall calendar (hmm, February: the many loves of Bender!) and the PalmOS calendar. Chandler 0.6 is better than paper, but not nearly as good as my palm pilot, which is practically a decade old.
The data entry is clumsy and unintuitive, at least from a mostly keyboard-using viewpoint. I have to type 2/15/06, not 15 or 2/15. I have to type "4:00 PM", not 4pm or "even 4:00pm". You get more syntactical freedom with the at
command. I have to calculate the event length in my head; it only accepts end times, not event lengths. It supports multiple timezones, but the start and endtime must be in the same zone. This sounds a little nitpicky, but one of the first things I did to try it out was enter the times for my flights next week.
It's not snappy on my dual AMD 1900+ CPUs. It takes forever to load. The events lag behind my pointer as I drag them across the calendar. I'm assuming that it's loaded with helpful debug stuff that's causing the slowness.
They break the important rule of being reluctant to destroy data. No prompt for deleting an event (understandable), and no prompt for emptying the trash (unforgivable). Oh, and it seems to sync with something, but that something isn't my motorola phone.
But hey it's written in python, and I like their 1.0 philosophy
. So I'll keep my eye on future releases.