| To continue the email summaries.... A response by Ted in the "bridging the gap thread" prompted Katie to start a new thread on the list assess people's opinions on the minimal email feature set they would need before they would use Chandler. http://lists.osafoundation.org/pipermail/design/2006-July/005028.html Assumption: Basic composition and reply, forward etc - some people experimenting with sending out Chandler notifications today. Some people replied with a few suggestions but most of the responses to this particular question were handled in the "What is the minimum feature set we can put up with in an early release of Chandler?" email thread: http://lists.osafoundation.org/pipermail/design/2006-August/005205.html. A few additional items... + Since we are able to "send" items to others we need to be able to keep track of who this was sent to, when it was sent and managing any replies. + If Chandler isn't my principle email client but it should be a target to receive email content from others. + A goal in the Beta timeframe could be the ability to file a bug from Chandler + Larger detail view for editing/viewing email + Affordances for Read/Unread + Address auto-completion + Keyboard navigation + Sorting + Filtering or tagging with rules + Attachments + HTML email display + BCC The discussion really got caught up in the long-term versus short-term goals for Chandler. To summarize, some of the major points.... + If we want people to abandon their current email clients and switch to Chandler, we need to meet the bar of what they use today. + Having a full-fledged email client is still in the longer term vision for Chandler. + Even if Chandler is a replacement email client someday, we can't assume that everyone will want to switch and need a way for Chandler to co-exist with other products and allow users the flexibility of using multiple tools. + If we go with a strategy of bridging the gap for the short term, this is still a solution we will need for the long term. + In the meantime, we need enough basic functionality so we can show off the integrated features. Sheila |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
