At <http://lists.osafoundation.org/pipermail/chandler-dev/2008-March/009782. html> (referred from <https://bugzilla.osafoundation.org/show_bug.cgi?id=11936>), Randy Letness wrote:
> Mimi Yin wrote: >> 2. Phase 2: With a lot more server work, the server can keep a >> log of *what changes were made* on an item over time: >> - Lars changed the Title of xxx to yyy at zzz-1 time >> - Lars changed the Notes of xxx to yyy at zzz-2 time >> - Lars changed the Notes of xxx to yyy at zzz-3 time >> >> * The server would be able to track changes at the granularity of >> "per edit session" or "per set of changes committed to the server >> when user clicks [Save] button" >> >> * The server won't have this kind of information from syncing >> Desktop clients. Instead, all edits will be lumped together with >> the last edit time: >> - Lars changed the Title of xxx to yyy at zzz-3 time >> - Lars changed the Notes of xxx to yyy at zzz-3 time >> - Lars changed the Notes of xxx to yyy at zzz-3 time >> *3. Phase 3:* With additional work on the Desktop client, we can >> keep a log on the Desktop client for every edit to every >> attribute over time, just like the server in Phase 2. >> >> Both web and desktop client will eventually need to understand >> the difference between users manually assigning triage status to >> items and Chandler auto-triaging items to NOW based on event >> start date/times and *shared* alarm date/times. >> >> Randy, does this sound right to you? > > Yes, with the third phase still being a little fuzzy. > > -Randy Does Google Wave change any thinking in these areas? The 'Playback' feature appears at around 13:10 in the Google Wave Preview movie. A little discussion: <http://chandlerproject.org/script/getIrcTranscript.cgi?messagesOnly=true &channel=chandler&date=20090531> Regards Graham
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
