Hi Mimi,
I've been mulling over this one too for a while. I think the problem I'm
blocked on is, if/when we sort the LATER section correctly (meaning
sub-sorted by Date), how should an event with a custom tickler alarm be
sorted?
For example, should the July 4th wedding appear after items set for July
3rd and before items set for July 5th? Or should it appear amongst the
late June items?
(I have been assuming that it would appear amongst the late June items,
the use case being: I'm scanning my LATER section to see what's coming
up just over the horizon.)
In the long term, I think we *definitely* want a quick and easy way to
spawn a linked item, which can appear separately, at a different time,
in the list view.
In the short term, since we're not doing that right now, I'd like to go
for the simpler approach: If it's a future event with an earlier alarm,
ignore the alarm for sorting/display purposes.
I know that by doing this we'd lose the ability to scan quickly for the
do-subtask-implied-by-alarm workflow, but it's not like the information
is gone. It'll still pop-to-now on time, and I can select the event to
look at the alarm.
The win of simplifying the mental model for beginning users just seems a
lot bigger than the utility of scan-for-next-alarm-on-event, it seems to
me. And note that we'd only lose scanning for alarms on events, alarm
dates for non-events would continue to be listed.
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
