[Chandler-dev] Edit/update (email sharing) model thoughts
Jeffrey Harris
jeffrey at osafoundation.org
Thu Dec 7 21:47:40 PST 2006
Hi Phillip,
> I'm a little bit confused - I've been assuming that the process of
> sharing items *via* email is entirely orthogonal to whether the items
> *being* shared are themselves emails. In other words, for sharing
> purposes, I'm assuming that there are distinct email messages carrying
> update "payloads", and that these emails need not be items at all;
> they're just a transport mechanism and it doesn't matter whether they
> are ever seen or edited in the UI at all. In other words, I'm thinking
> of email as just a background transport mechanism for sharing protocol
> transmissions.
Oops, I should definitely have included some preamble about edits and
updates. The context throughout my message was of implementing the
stamping storyboards
(http://wiki.osafoundation.org/bin/view/Journal/StampingStoryboards).
The idea is that items are only shared via email when a Chandler user
addresses an item and hits send or update. So while it might be
perfectly reasonable to share items over email in a more general way, I
think that's not where our focus should be.
> That being the case, it would be helpful to know which kind of emails
> you're talking about here, and throughout your message. :) Without
> that information, I can't tell what the rest of your post is proposing,
> or what problem it's intended to solve.
>
> (I also have trouble wrapping my brain around the idea of a "changing"
> email, but that may or may not be related. ;) )
Changing email is definitely related, and it's certainly confusing at first.
The crux of the communication stamp is that the same item can be edited
and shared throughout a process of sending drafts, normally sending the
item, or sending updates after the item's been normally sent.
So when I talked about emails, I was referring to updates (i.e., drafts
of not-yet-sent items, and updates to previously sent items).
Now that I think about it, I'm not actually sure what the payload of a
normal send should be. Maybe the same as an update?
Sincerely,
Jeffrey
More information about the chandler-dev
mailing list