Grant Baillie wrote: > Explicit non-goals: > > * Persistence layer: i.e. not saving user data (import from a format > like .ics is possible, especially for performance testing purposes). > * Sharing/email import. > > The lack of persistence is likely to be controversial in some quarters.
You could say! :) Or maybe I did not understand the high level plan. Let me clarify: Is the plan to have testable, scriptable, extensible, high-performance Chandler UI that does not save anything anywhere (except RAM)? That is quite a bit different from what I thought the project was going to be. Still, I do see some value in that, and if you can really pull all that off in 2 months I am not worried one way or another. So assuming for a moment that I understood correctly, is the next step after that finding a backend that meets the performance etc. requirements of that non-persistent-Chandler? -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
