Hi,
Couple of weeks ago as well as last week, I asked and took notes of what
is preventing interns and SoC students to adopt Chandler as a daily
tool. Here's a summary.
1- Performance: this is the biggest issue by a long shot and touch
various aspects of performance:
- interaction with Cosmo: sharing performance, sync and restore
performance
- pure UI performance (switching between calendars or views)
- memory footprint
- disk footprint (not a big issue for interns but thought it would
be for casual downloaders)
2- Dev documentation: this is a little deeper than a casual user would
note for sure but, still, worth mentioning. Our developer documentation
(for Chandler in particular) is lacking big time. Diving into Chandler's
is devilishly difficult and remote students particularly really suffered
through it.
3- Month View: was mentioned as a clearly missing piece of the calendar.
It's also a piece that's common in most calendar apps.
4- Scripting: I put there several mentions of ways of doing things with
a command line mode within Chandler. Darshana's NLP will help but won't
solve everything. May be a little advanced for sure but, since we're
trying to attract early adopters, worth mentioning.
That's pretty much it. The good news is that it's a short list and none
of this was a discovery but it's good to be reminded sometimes.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
