On Tue, 27 May 2008, Frank Niessink wrote: > PS: I'm getting more and more excited about this. We may also want to > think about making syncing the primary persistence mechanism so we > could add different back ends that support multiple users more easily > (e.g. a database).
Okay, after further reading, almost everything is there in icalendar: parent/child relationship, attachments, I think notes may be represented as VJOURNAL objects with no date. The only thing missing is hierarchical categories. For the multi-user thing, I don't think that a synchronization-based mechanism would work (at least when using SyncML). It only has a global "changed" flag for each object; so for instance if user A changes a task's priority, and user B changes its description, there's a conflict. IMO, this use case should not require user intervention. This could be solved by considering all objects properties as separate objects (priority, description, etc) linked by the object unique ID, but 1) That begins to be a bit complicated 2) We couldn't use iCalendar format for that, so the whole "sharing with mobile devices" aspect is lost. Actually, I have some ideas about a multi-user system for TaskCoach, but I have to think a bit about it first. And finish my current SyncML pet project :)
