Re: Call for Open Design Issues

Mimi Yin <[email protected]>
Newsgroups gmane.org.osaf.design
Message-ID <[email protected]>
Yes, that's weird that the dialog says Occurrences and then Items. We  
don't have any immediate plans however.

On the Desktop, the dialog reads:

===
Recurring Event Change
------
"Event Title" is a recurring event. Do you want to change (remove):

[Cancel]          [All Events] [Future Events] [This Event]
===

Mimi

On Oct 15, 2007, at 3:43 PM, Matthew Eernisse wrote:

>
> Currently, the text of the dialog is:
>
> "This is a recurring event. Which occurrences do you wish to change?"
>
> And there are three buttons:
>
> All Items, All Future Items, and Only This Item
>
> So we have three different terms we're using in kind of a mushy way  
> to refer both to the entire recurrence series, and the individual  
> items in the series. Sure, you can likely intuit more-or-less what  
> it means, but it's not ideal. I think we can do better.
>
> A few thoughts:
>
> 1. Whatever term we use for the individual occurrences, it should  
> be the word on the buttons. We shouldn't ask them what they want to  
> do with certain 'occurrences,' and then say 'items' on the buttons.  
> Inconsistency is fine, when it serves a significant purpose.  
> "'Occurrence' is too long a word for a button" doesn't seem that  
> compelling as a reason to use two different words.
>
> 2. I think it might make sense to avoid the word 'event,' since  
> you're changing/removing more than the event-ness. Can items recur  
> without an event stamp? If that's possible, you could see this  
> dialog in association with recurring items in list view that are  
> not even events.
>
> I'd like to propose something like this:
>
> "This is a recurring item. Which items in the series do you wish to  
> change?"
>
> All Items, All Future Items, and Only This Item
>
> Thanks.
>
>
> Matthew
>
> p.s. Hope you have a good vacation, Mimi. :)
>
>
> Mimi Yin wrote:
>> I am leaving for vacation this Saturday for 2 weeks. Are there any  
>> open issues that need to be resolved before then? Bugs? Mock-ups?  
>> etc.
>> What I currently have on my plate includes:
>> 1. Staff Mtg Presentation: Setting up KEI Creative to use Chandler  
>> to collaborate on projects
>> 2. Syncing up with Philippe for Desktop 1.0 Planning
>> 3. Preparation for FLOSS Usability Sprint in Nov.
>> 4. Work through some design issues for Multi-Week view (Reid/Jeffrey)
>> 5. Sample data set for Desktop OOTB experience
>> 6. Summarize design list for last couple of weeks
>> 7. Calendar colors on Chandler Hub
>> Close out some threads / bugs on the Design List:
>> + Improvements to the reload dialog has been hanging open for some  
>> time.
>> + Reconciling various sharing URLs
>> What's missing?
>> Mimi
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.