[Design] Questions about ticklers/reminders

[Mimi Yin]

Hi Grant...see below...

On Jul 28, 2006, at 10:25 AM, Grant Baillie wrote:

> I was reading the Dashboard spec and wasn't quite sure about a  
> couple of things.
>
> Currently, in Chandler we have reminders that are relative to event  
> start-times. If I understand right, reminders with fixed times  
> could be applied to any Item, and these are called "custom date  
> ticklers". (I'm not really so sure why these are more "custom" that  
> the event-relative reminders, though).

The custom-date ticklers are more custom in the sense that they are  
not tied to an event start date/time. :o)

> Also, when either kind of reminder is fired, the triage status of  
> the corresponding Item is supposed to change to "Now".
>
> The things I wasn't sure of were:
>
> 1) Will we still use the current reminder dialog? (Some might find  
> it handy in cases where an alarm goes off and the item is already  
> triaged as "Now". This would often be the case if you have a  
> reminder set to display 5 minutes before an event, because events  
> are promoted to "Now" at the start of their day).

Start of their day or Start-time. I think it should be Start-time,  
though I can believe that the spec is unclear or even directly  
contradictory.
+ If there is an alarm set to 5 minutes before the event...the event  
should enter into NOW 5 minutes before the event start-time.

However...
+ If there is a custom-date tickler (say for Mar 1st, 2007), the  
event enters NOW on Mar 1st 2007.
+ If the event start date/time is March 15th, 2007 at 2PM...The event  
re-enters NOW at the event start-time; OR
+ You could re-set the alarm to be 15 minutes before the event start  
time...at which point the event will re-enter NOW 15 minutes to 2PM  
on March 15th.

>
> 2) Assuming we have the dialog, and it displays an alarm, and the  
> user "snoozes" it, or dismisses it, is the triage status of the  
> item affected?

What does snooze do? Snooze for 15 minutes? Can we specify for how  
long? If we can, we could defer it to LATER and have it re-enter NOW  
when the alarm goes off again...OR

We can just leave it in NOW have it re-enter NOW again in 15 minutes  
(or whatever the default snooze time is).

>
> 3) If you set a custom-date tickler on a recurring event, it  
> doesn't make sense to add it for all future events. Do we show the  
> recurrence change dialog, with just "Cancel" and "Change This"  
> enabled? Or maybe just assume the user knows what they're doing and  
> just make the change.

Ooh, good point. I like the first approach better. Make it clear that  
it can only apply to the selected instance of the recurring event.

>
> --Grant
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design