On 14 Feb, 2007, at 17:24, Morgen Sagen wrote:
...
Here is my take on what's realistic for Preview:
Whenever the user makes a change to an item in the detail view or
the week view, the lastModifiedBy attribute for that item gets set
to 'My' email address *** and the lastModified (time) attribute
gets set to "now". This updates the byline in the detail view to
say "Edited by me on ...".
If a change comes in via edit/update email or via server sharing,
the update will contain a lastModifedBy email address and a
lastModifiedTime. Regardless of whether any changes from that
update are actually applied (because of filtering or conflict), the
byline will update to show the new lastModifiedBy and lastModified
(time) -- but only if the incoming lastModified (time) is more
recent than the item's current lastModified (time).
This means that if A sends a change to B, and B makes no changes
but forwards that change to C, C will see that the change was made
by A.
If A sends a change to B, and B has also made a change, whoever
made the change more recently will be in the byline.
Jeffrey and I discussed a way to perhaps skip the setting of
lastModifiedBy if none of the other changes are applied, but this
would need to be post-Preview.
I'll +1 that (not that we were calling for a vote ;).
*** 'My' email address: have we determined which of the possible
several email address to use? And what if the user hasn't entered
one?
Maybe the following (from the latest Stamping spec) is helpful. In
the case where there's no account info, and the user isn't even
trying to send or share, we could also treat local changes as
anonymous, i.e. omit the "by" from the byline (how paradoxical is
that?).
--Grant
Nuances of the byline:
When editing and updating items in Chandler, the Addressing fields
stay the same, the item UUID stays the same, the iCAL UID stays the
same. The only change is in the byline. The byline changes from
displaying in static text, whoever last created, sent, edited or
updated the item to a pulldown where the user can select an email
address with which to send the update.
If the user has no email accounts, we display the email address
associated with their sharing account. When the user tries to Send
the item, we pop-up a dialog that says: We do not have an email
account for this email address. [Cancel] [Add email account]
If there is no sharing account, then we display: Add email account in
the pulldown.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
