Hi, see below...
On Mar 8, 2007, at 2:16 PM, Grant Baillie wrote:
...
Issues:
- For an item I (local user) edit, it appears that the transition
from "Edited by" to "Updated by" happens after the next sync
(manual or background). Is that correct?
Well, it's what I intended :). From the sending client's point of
view, we have to package up the item into an email and hand the
email off to your SMTP server. We only really know the item has
been sent when the server accepts it(*). So, the "sent" state (or
possibly "error" state) only happens well after the item has been
emailified. It's certainly possible to try to get tricky, and pre-
mark the item as sent and attempt to restore its old state on
failure, but for the moment I think it's better to keep things simple.
On the other hand, the recipient of an email item knows that it has
indeed been sent (or updated), so perhaps in this case the proper
way to share this state correctly (have recipients update the
lastModifiedBy/lastModified/lastModification).
That sounds good.
- For an item which is both shared and emailed, I suppose the
emailness overwrite the shareness and then the byline should say
"Send as <lastModifiedby>" rather than "Edited by
<lastModifiedby>" when editing. What if the item is synced but not
sent? I still think it should say "Send as" and not switch to
"Updated by" (i.e. emailness always win). Is that ok?
Actually, the stamping spec currently has this the other way around.
Oh is that true? Where do you see that Grant? So long as the item has
not been Sent, the Send as: field prevails. 'Updated by' only appears
if the item has been 'Updated' by clicking on the 'Update' button in
the toolbar. Hopefully, I'm not misunderstanding everybody.
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
