After talking a bit with Jeffrey, I understand his write-up a bit
better and think it might be a good interim plan for Preview. But of
course, ultimately, this, like the original proposal requires Bryan
input and evaluation.
Let me see if I can re-summarize what Jeffrey said to make sure I
have it right.
When importing an .ics file or subscribing to a collection...
+ Auto-triage items into the DONE and LATER sections in the order of
the Date that appears in the Date column for any given item. For
example:
- Yesterday's event is auto-triaged to DONE before This morning's event.
- Tomorrow's event is auto-triaged to LATER before Tonight's event.
Note: Items are not auto-triaged if triage status is shared.
Nice-to-have Addendum to Date column behavior: Event start date wins
over Custom alarm dates in the DONE section *only*.
But still...
+ After the initial import / subscribe, items will be order in the
DONE and LATER sections in the order in which they were triaged to
DONE and LATER, NOT in accordance to the Date that appears in the
Date column for any given item.
I think while this doesn't solve all the use cases outlined in my
original proposal, it does address the rather disorienting experience
of loading in a whole bunch of items into Chandler and having
Chandler auto-triaging in what appears to the user to be a fairly
arbitrary way. Instead, it roughly approximates the order in which
items would have been triaged to LATER and DONE if the user had
manually created and triaged the items one-at-a-time.
Post-Preview...
+ I think we will still want to revisit the original Proposal I
posted, including ordering items in the LATER Section differently
from ordering items in the DONE Section.
Mimi
On May 9, 2007, at 12:47 PM, Jeffrey Harris wrote:
=======
When importing an .ics file or subscribing for the first time to a
collection where triage-status isn't shared, set DONE items
triageStatusChanged attribute (the attribute that controls sorting
within a section) so that older events are sorted later.
=======
It seems to me this is the desirable behavior for items in LATER, too,
not just DONE; if the initial sort order was going to be random or
arbitrary, it'd be nice for all newly imported items to be sorted
based
on the relevant date, not which item we happened to import first,
which
is what happens now.
Usually there aren't very many NOW events in any given .ics file or
collection, but I suppose the sort for those few NOW events would
ideally be the reverse of DONE, events in progress that start earlier
appear higher on the list?
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
