In-line... On 2/12/07, Philippe Bossut <[EMAIL PROTECTED]> wrote:
Hi Mimi, See inline: Mimi Yin wrote: > > On Feb 10, 2007, at 1:48 AM, Philippe Bossut wrote: > >> >> - in "Read/Unread status Workflow", there's this puzzling sentence: >> "Not-new tems are not marked as Unread when they are 'tickled' >> into the NOW section" >> ?? Lots of negation are hard to decipher... but anyway, my >> understanding is that this could simply be rewritten as: >> "The read/unread status is not changed when items are tickled in >> the NOW section" >> Is that correct? > > That sounds better. I'm just trying to figure out, is it possible to > have a New item that is tickled? I guess what it is is that Tickling > to NOW in and of itself does not result in a change to Unread status. I think that, generally speaking, the read/unread status is never automatically changed from unread to read and is changed from read to unread only when attributes are changed by others sharees (through email edit/update or Cosmo sharing). "Tickling" (a change of triage status triggered by time) should never change that status from read to unread. So, for a New item (which is therefore "read"), the status is not changed to unread even if it's immediately tickled.
New items are sometimes 'Read' and sometimes 'Unread' depending on who created them and how they were created. What I'm worried about is that New items that should techically be marked as Unread (e.g. New message items, New items created by sharees, New items created by you in the CLI text field) would lose Unread status because for some other reason, they get 'Tickled' right away. Mostly, it seems like tickling should not affect Read/Unread status in any way.
>> >> - "However, ticklers and start date/times that auto-triage the item >> and triage status changes invoked by explicit user action DO >> permanently affect the explicit and ARE shared." >> ?? Unclear. I suppose that could be summarized simply by "Color >> triage status are shared". >> >> - "If Triage status is shared, then the order of items in the >> collection is shared as well" >> I don't think there is anything like an "order of items" in >> collections, at least, not one that's surfaced to users except for >> the "section triage status". But since this one is precisely not >> shared, I really don't understand what this "order of items" refers >> to. The other "order" is the one induced by when an item has been >> moved to a particular section but again, since this "section triage >> status" is not shared and, potentially, different between sharees, >> its order cannot be shared either. > > When Purged, items need to appear in the same order for all sharees. > This doesn't mean there's a specific mechanism for ordering (although > in the future, we will want to have one). Just that the way triage > sorting, tickling and purging works should result in the same triage > sort order across Chandlers. I see several issues here: - First, triage status is not always shared so, clearly, in such a case, Purge by someone should have no influence on other sharees
Well the Purge workflow has no affect on sharees whether or not triage status is shared. Sharees only ever see each other's Color triage status, if triage status is shared at all. Section triage status is personal.
- Second, since the "triage section" can (and will) be different for different people, I don't understand how the order can be the same for all sharees. e.g. if I triage something from Now to Done, the item will move to my Done section (after purge) but it will stay in the Now section of sharees though the "Color triage status" will be Done (as explained later in the spec). With such rules, I feel that the "order" is something specific to the current users so that stuff that needs his/her attention stays under his/her nose though they may be in different places for others.
Let me try again. If triage status is shared...if everyone Purged, they would see the items in the same order. I'm assuming that since everyone has the same rules for how items sort in each triage section, this will happen for free? Here, I am assuming that "order" means the relation of an item to others
within a section (first, second, third in the Now section for instance). If you mean something else, please let's define what you mean by "order" 'cause I'm really lost...
No that's my understanding of order as well. :o) I'll come find you tomorrow to chat. Thanks for reviewing the spec so carefully Philippe, Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
