Thanks Grant, see below...
On Aug 3, 2006, at 10:09 AM, Grant Baillie wrote:
1) I now have 82 events in my dashboard, all with a triage status
of "Now". Maybe this is a one-off state of affairs (i.e. first
importing a pile of events with no triage status from another
client), but maybe it would be better to have imported past events
show up as "Done", and future as "Later"? We do something a little
like this with recurring events with reminders (i.e. treat past
reminders as having expired by default).
Yes, Jeffrey and I had a discussion on the list about this exact
functionality and it is in the 0.7 Dashboard Spec under Alpha 5
Dashboard. :o) http://lists.osafoundation.org/pipermail/design/2006-
July/004926.html
2) Some of those events were recurring (weekly/biweekly) meetings.
Changing them to "Done" seemed to have changed all recurrences to
"Done" (maybe this is just a bug). But, anyway, that started me
wondering how recurrence will interact with triage status and
ticklers. Is the following a reasonable outline for how this might
work?
- I create an event; it starts off as "Now", and stays that way
when I make it recur.
- I change the status to "Later" (for all occurrences).
- When the first occurrence rolls around (or one of its ticklers
fires), just that event changes to "Now". There's an entry in my
"Later" section for the remaining events. Probably its date shows
up as the start of the first remaining event.
- At some point, I change the first occurrence to "Done".
That sounds right. We started this conversation back in 0.6 with Alec
and Jeffrey (re: how do we display recurring events in the table?) It
seems like we not only want at least 1 instance of each recurring
event in each Triage section. We also want 'detached' instances to
appear as their own thing (e.g. The 4th instance is at 10AM instead
of 2PM). I will add this to the spec.
Mimi :o)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
