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.
- "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
- 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.
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...
- "Create a new event by double clicking on the calendar that is
happening right now"
Define "right now" (for this example and all other places where
"right now" appears in the autotriage spec). Is that within +/- 1
hour of current time? Sometime today? I think that "right now" should
be "today" 'cause I think that creating an event for, say, this
afternoon when it's 9am is not enough to park the event in "later".
This is debatable. Anyway, we need a definition of this concept. This
definition will mechanically influence what is "in the future" (after
"right now") and what is "in the past" (before "right now").
I mean "Right now" in a literal way. If the event is scheduled for
Today at 10:42AM and it is 10:41AM, the event would not be right now.
If an event is scheduled for Today from 10:40AM-11:42AM and it is
10:41AM, the event is NOW. This only affects the Color triage status,
not the Section triage status. Newly created events will show up in
the NOW section regardless of what Color triage status they receive. I
will clarify that in the spec.
So that means that most events will be created with a "Color triage" of
"Later" and a "section triage" of "Now"... Hmmm... OK... At least it
leaves "Now" relatively empty and it maintains everything consistent. I
think it's good.
Thanks for the detailed answers Mimi.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
