[Design] [Sum] Oct 2-8th

[Sheila Mooney]

New Threads:

Mimi started a thread on visual treatments of empty collections. Mimi  
has been thinking about enhancements for the readability of  
collections when there are no items and when the collection is  
selected and has focus. Empty collections are currently grey which  
can make users think they are disabled.
+ Mimi is proposing that we get rid of special visual treatment for  
empty collections.
+ +1 from Jeffrey
http://lists.osafoundation.org/pipermail/design/2006-October/005517.html

Mimi summarized an off-list discussion relating to forward/reply/ 
reply all for stamped items.
+ Reply and reply all are simply a message. If the item is stamped as  
an event, we copy the details into the note and it's sent as a simple  
message.
+ If we forward an item stamped as an event, we create an ics  
attachment. Chandler users receive this as a mail time stamped as an  
event. Non-Chandler users receive a message with an ics attachment.
http://lists.osafoundation.org/pipermail/design/2006-October/005519.html

Sheila posted that we have iterated quite a bit on the sidebar icons  
and have reached a design we are happy with for Preview. We will  
focus our attention on completing other features and addressing  
performance and stability.
http://lists.osafoundation.org/pipermail/design/2006-October/005521.html

BCM replied to Mimi's post about the Usage Scenarios for GData/Atom.  
He was quite pleased with the extensive list of use cases that Mimi  
came up with.
http://lists.osafoundation.org/pipermail/design/2006-October/005525.html

Mimi posted about  Stamping and Date/Time Parsing. When users add  
emails to the special Chandler Events IMAP folder, we will attempt to  
parse any date time information in the email and automatically create  
an event in Chandler. If user receives an email in Chandler via  
special Chandler headers or POP mail and decides to Stamp that  
message to add it to their calendar, Chandler should also  
automatically parse any date/time information in the message.
+ Mimi is wondering if this is alot of extra work to implement.
+ Darshana replied that she had already implemented this. She is  
running into one problem where all date/time info is getting parsed  
even if it's not event information.
+ Mimi updated the spec with details that we will attempt to parse  
date/time information in the title and notes field. If we can't find  
any date/time information we simply don't stamp it as an event.

Philippe responded to Mimi's proposal that In and Out Collections  
should appear out of the box. He thought this was a good idea.
http://lists.osafoundation.org/pipermail/design/2006-October/005535.html

Mimi sent out a Item Sharing Proposal for Preview. Per Morgen's  
request, she followed up with a detailed workflow we want to support.  
Basically item sharing allows people who are not using Chandler to  
participate in the collaboration scenarios. We haven't yet decided if  
this will be in Preview or not. We are still exploring options via  
discussions on the list.
http://lists.osafoundation.org/pipermail/design/2006-October/005536.html

John posted to the list about Selections without focus in Chandler.  
John is suggesting that people are confused when a command doesn't  
work on a selection that doesn't have focus. He suggests that the  
difference between focused selections and non-focused selections be  
more distinct. Proposal: drawing the non-focused selection in gray  
rather than a lighter shade of the selection color.
+ Bear asked if the keyboard focus should be where the attention of  
the user is - if we support use without a mouse.
+ Mimi sent out some background on why the focus doesn't shift to the  
sidebar when you single click on a collection.
+ Davor commented that he doesn't like the way the keyboard focus  
sometimes gets stuck in the folder view when using Thunderbird  
(doesn't want to delete a collection). He suggests that if the  
sidebar has to get focus, we could have a keyboard shortcut that  
rotates the focus to different places.
+ Mimi replied that we plan to support navigation between panes with  
the tab key.
http://lists.osafoundation.org/pipermail/design/2006-October/005541.html

Sheila sent out a first draft of the Preview email spec.
http://lists.osafoundation.org/pipermail/design/2006-October/005548.html

Mimi forwarded a bug and discussion to the list - All recurring mail  
occurrences appear in the In collection. It relates to what happens  
when we email recurring events. Since this post, we have closed a  
proposal for handling recurring events, stamping, email. A summary  
for the list is pending.
http://lists.osafoundation.org/pipermail/design/2006-October/005542.html

Continued Discussions:

Discussions continued around Sharing the BCC field.
+ Brian K expressed concern about the perf implications for sharing  
items and what happens if there is an error of the server is down. He  
was also worried about the custom work required to handle BCC  
differently for item sharing.
+ Sheila replied that we were simply brainstorming options to tease  
out all the issues. Item sharing is a "maybe" for Preview. We have  
also proposed not to share the BCC field for Preview either but Mimi  
simply wanted to explore the issues on the list.
http://lists.osafoundation.org/pipermail/design/2006-October/005518.html



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20061011/ce2c2d01/attachment.html