| New Threads: Mimi forwarded a bug that Priscilla logged to the design list - [Bug 6707] Dashboard upcoming days "Monday", not last week. We currently use proper names like Monday, Tuesday in the date column of the summary table view. There seemed to be confusion about whether a particular day ie: Monday meant the past Monday or the upcoming Monday. This really depends on what day of the week you currently are on. + Mimi suggested that we could... + Get rid of the proper nouns and just use Yesterday, Today and Tomorrow. + We could distinguish between Tuesday and Next Tuesday. + The consensus was to get rid of the proper nouns and just use Yesterday, Today and Tomorrow. Mimi compiled a list of Usage Scenarios for GData/Atom Sheila sent out an email summarizing some updates to the stamping spec. In discussing the Alpha5 work with Bryan S, Grant and Philippe, we decided that some specifics regarding what appears in the detail view and the behavior of the addressing fields needed some clarifications. The PPD team held a design session on Email - the plan for Preview and 1.0. We discussed the 1.0 strategy and also some specific issues around the Preview goals. Brian K had a bunch of questions which related to stamping and email. We came out of the meeting with a set of next actions. + updates to the spec for Chandler as an IMAP server solution + updates to the spec for setting up Chandler IMAP folders for IMAP users + extract relevant portions of stamping spec and add to email spec - storyboards + design to mock up workflows for auto-detection of email account settings + list of continued architecture discussions A follow-up from the email discussion was to explore if we could have support for Rich text in Chandler desktop in the Preview or 1.0 timeframe. Although we are not looking to replace people's email client's with a super rich composition environment we would like enough so that user's can type up a meeting agenda. Mimi put together a list of the things we are hoping to support and asked about the wx work required. + Brian K doesn't feel that the current detail view size is realistic for email composition. He suggests a popup window or changing the layout for email. + Robin responded that there is a wxRichTextCtrl that can handle manipulating the font characteristics and styles. It can handle inline images but doesn't have Dnd support yet. He said that other than Dnd the only thing missing is the ability to read/write standard formats such as RTF or HTML. He pointed out that the wxRichTextCtrl currently uses a custom XML format. + Philippe expressed concern about the custom XML format since we can't really send around custom XML. He also added that he wished we had the ability to detect URLs (color them etc). + BKirsch - per Robin's response, he would prefer to leverage the HTML format. + Grant - +1 to the HTML and added that the URL detection should be for all notes. + Robin - URL detection shouldn't be very difficult. Ted forwarded his feedback about the Cosmo 0.5 spec update to the design list. Mimi sent a proposal to the list suggesting that In and Out Collections should appear out of the box. Given that communications will be a major part of the dashboard in 0.7 it just makes sense to have them there and not only when you setup incoming email accounts. You can send mail but you don't see any Out collection. Mimi sent an email summarizing the issues around sharing the BCC field. If we want to consider doing item sharing for Preview or 1.0, there are some specific issues around whether or not users want to share the BBC field depending on if they are sharing a collection or a single item. Mimi has summarized the concerns and potential options. Continued Discussions: The discussion continued around the Proposal: have an en-US localization egg. + Heikki had some questions about the performance and footprint issues with having a en-US locale file. He also wondered if it would contain only last minute working fixes or the full localization. + Philippe replied that modified strings would be a good solution so we don't duplicate what's in the code. He also pointed out that the performance issues would not be worse than what happens with the other languages currently. + I am not sure if we came to any decision on this since the thread ended here. There was further discussion on Alternate sidebar designs for icons and the overlay state -- last call for votes. + Mimi responded with a proposal to address the "eye" mouse over icon that people were concerned with. She explained that we were trying to make the mouse over icon look like a tab that slides out over the collection icon. We currently have a gap on the left side that makes it hard to see that the mouseover icon is supposed to be attached. Mimi proposed that we try the checkmark icon again. + Priscilla suggested we could show a bit of the unchecked/unoverlayed state peeking out on the left hand side. It might have the visual effect of something that slides out. Mimi sent out an animated gif for people to look at. + John suggested that an animated tab might not be that much work. + Jeffrey liked the "peek-a-boo" tab. + Davor said that the screenshot suggests that it's an action spot but users may not know they should click. Other Stuff: Pieter sent a post about Labeling workflow - keyboard shortcuts. He has recently begun to use a a Firefox/Gmail Greasemonkey macro-script called "Gmail Macros". |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
