[Design] [Please Review] Dashboard Spec Update - Recurring Events

[Mimi Yin]

See inline...

On Feb 26, 2007, at 6:43 PM, Grant Baillie wrote:

>
> On 26 Feb, 2007, at 18:32, Mimi Yin wrote:
>
>> Okay, so are we saying that Triaging, Adding/Removing Custom  
>> reminders will always apply to individual occurrences no matter  
>> where you are, Dashboard or Calendar?
>
> That sounds right to me.

Okay, will update spec thusly.

>
>> Invoking the Task stamp I think should pop-up the dialog asking  
>> users if they want to apply/remove the stamp to the entire series,  
>> the single occurrence or this and future occurrences, regardless  
>> of where you are. Is this consistent with how you're thinking  
>> about things? or would this require reworking?
>
> There are some changes required here, so far as I can tell. In  
> general stamping and unstamping of occurrences is pretty broken  
> right now, but I'm hoping the changes I'm working on for bug 7446  
> will help out muchly.

Will update spec thusly.

>
>> And Marking as Read/Unread/Needs reply always applies to the  
>> entire series?
>
> For some reason, the Read/Unread case seems more compelling to me  
> than Needs Reply. But I'd be happy to try Needs Reply this way, and  
> raise a hue and cry if it's not meeting my needs :).

I agree, but I think we can't get around the widget problem Jeffrey  
pointed out. If we make Read/Unread apply to the entire  
series...it'll be hard to make Needs reply apply to individual  
occurrences...we can re-address after Preview :)

>
> --Grant
>
>>
>> Mimi
>>
>> On Feb 26, 2007, at 5:14 PM, Jeffrey Harris wrote:
>>
>>> Hi Mimi,
>>>
>>>> There is also the issue of triaging and marking recurring events as
>>>> read/unread/needs reply, also pasted below. Jeffrey, are we really
>>>> applying explicit triaging to the entire series? I couldn't  
>>>> remember if
>>>> we only agreed to do that with Read/Unread/Needs reply status or  
>>>> if we
>>>> are doing that with Triage as well.
>>>
>>> I think triage status should continue to apply to individual
>>> occurrences.  There's fairly elaborate code to make triage status
>>> per-occurrence based on start time, making triage changes apply in a
>>> different way would be a lot of design back and forth and  
>>> implementation
>>> time.
>>>
>>>> *Also...the stuff in the Triaging/Marking as Read/Unread  
>>>> section, should
>>>> the same rules apply to Stamping to Add to/Remove from Task list  
>>>> and
>>>> Adding/Removing Reminders? Both can be done from the Dashboard.*
>>>
>>> Currently we only allow stamping as a task to apply to individual
>>> occurrences.  That was before the recurrence branch landed, I  
>>> think it
>>> would be reasonable to allow either now, but at least in the  
>>> dashboard,
>>> I'm happy with the task stamp always applying to individual  
>>> occurrences.
>>>
>>> Reminders added through the dashboard are absolute reminders.   
>>> Right now
>>> you can't add a reminder to a recurring event through the dashboard,
>>> that's bug 8214.  When you can, I'd say that to be consistent we  
>>> should
>>> add an absolute reminder to individual occurrences, not make  
>>> reminder
>>> changes apply to all occurrences.  Setting a later 5PM/8AM absolute
>>> reminder when looking at an occurrence just seems like a one off
>>> behavior, not something likely to apply to all occurrences.
>>>
>>> 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
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design