- Revision
- 919
- Author
- sheila
- Date
- 2006-08-07 18:25:06 -0700 (Mon, 07 Aug 2006)
Log Message
Email spec with Alpha4 details for Reply, Reply All and Forward.
Added Paths
Diff
Added: trunk/docs/specs/rel0_7/Email-0.7.html (918 => 919)
--- trunk/docs/specs/rel0_7/Email-0.7.html 2006-08-08 01:17:31 UTC (rev 918) +++ trunk/docs/specs/rel0_7/Email-0.7.html 2006-08-08 01:25:06 UTC (rev 919) @@ -0,0 +1,189 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <title>OSAF - Email Spec</title> + <link href="" type="text/css" rel="stylesheet"> + <meta http-equiv="Content-type" + content="text/html; charset=iso-8859-1"> + <meta http-equiv="Content-Language" content="en-us"> + <meta name="description" content="OSAF Project Specification"> + <meta name="keywords" content="OSAF, Open Source, Specification"> +</head> +<body> +<div id="masthead"> +<div id="breadcrumbs"><a + href="" +Home</a> > <a + href="" +> <a + href="" +> This Doc </div> +<h1>0.7 Email<br> +</h1> +<table width="100%"> + <tbody> + <tr> + <td width="33%">Authors: <a + href="" PROTECTED]">Sheila Mooney</a><a + href="" PROTECTED]"><br> + </a></td> + <td width="33%">Last edited:<!-- #BeginDate format:Am1a --> +August 4, +2006<!-- #EndDate --> </td> + <td width="33%">Creation date: August 4, +2006</td> + </tr> + </tbody> +</table> +</div> +<div id="maincontent"> +<dl> + <dt>Sheila Mooney</dt> + <dd>Spec owner <br> + </dd> + <dt>Alec Flett<br> + </dt> + <dd>Spec contributor</dd> +</dl> +<h2><br> +</h2> +<h2>Overview</h2> +<p>This specification details the Email features and strategy in the +0.7/Beta timeframe. In the long term, we envision Chandler to provide +all the features of a full fledged email client. However, we realize +that in the short or medium term (Beta/1.0) this is not realistic. In +addition, users's are very attached to their email clients and it's +conceivable that even when Chandler supports all these features, people +will still want to keep using their exisiting email clients. Therefore +in the short term we will focus on exploring ways in which Chandler can +bridge the gap and co-exist with other email clients. We feel this is +not only doable in the short term but also will be required in the +longer term as well.<br> +</p> +<div class="issue">This is as much as we are going to add about the 0.7 +and 1.0 plan. That is emerging from the discussions on the list and +will be added to this spec soon.</div> +<h2>Goals</h2> +<h2>User Scenerios</h2> +<ul> +</ul> +<h2>Alpha 4 Email</h2> +<p>While we work out the details of the larger 1.0 and Beta Email +strategy, the +goals for Alpha4 will focus on putting in the infrastructure and +minimal UI to support Reply, Reply All and Forward. These features +support the Dashboard and fall into the category of "minimal +requirements for email", meaning that we will need them regardless of +what +strategy we decide to pursue for 1.0. <br> +</p> +<p>The plan is to keep +this as simple as possible for Alpha4. It's more about getting +something working. We do not expect the UI to be particularly +polished will be assuming no major changes to the detail view. We know +that the size of the notes field and the detail view is not ideal for +composing email but we will defer addressing the issue of a larger or +separate detail view until post Alpha4. The notes field should scroll +as it does today.<br> +</p> +<p><b>Toolbar Changes:</b></p> +<p>We will be adding 3 new toolbar items for Reply, Reply All and +Forward positioned to the right of the New button and to the left of +the Search box. We will not have menu items for Reply, Reply All, +Forward. The Send button will move the far right of the toolbar. See +mockup below.<br> +</p> +<p>We will also insert some extra space between the app bar buttons, +the toolbar buttons and the search box. It would make the toolbar +elements look like they are 3 distinct groups.<br> +</p> +<p><br> +<img alt="" src="" + style="width: 1060px; height: 57px;"><br> +</p> +<p><b>Reply Behavior:</b></p> +<p>For Alpha4 we are not going to handle anything but the display of +plain text as we do in Chandler today. If users receive an email with +complex formatting we will only display the plain text version, if +available, in the reply thread in the detail view, otherwise we display +nothing (I believe this is how we handle HTML emails now).<br> +</p> +<p>We will not be providing any UI to display threads for Alpha4. At a +user perspective, the emails are in now way connected although we may +have +these thread relationships under the hood. Handling threads are part of +clusters which has been deferred past the Beta release.<br> +</p> +<p>When the user clicks on Reply, Reply All or Forward we will +obviously update the From and To fields accordingly. Clicking Reply +populates the To field with the email address from which I received the +email and automatically inserts the cursor at the top of the notes +field. Similarly, Reply All would add the email of the person I +received this from to the To: field and everyone else in the original +To: or CC: fields would get listed in the CC: field of the reply. +Forward blanks out the contents of the To: and CC: fields and put the +curson in the To: field.<br> +</p> +<p>If you Reply, Reply All or Forward and don't hit send, we handle +this the way we handle draft items currently. We could stamp and item, +fill out the details but never hit Send. We do not prompt the user but +simply save the item and mark it as a draft in the communication column +of the dashboard. As with other newly created items, it simply +appears in the Now section of your dashboard.<br> +</p> +<p>Below are 3 mockups for the detail view when you hit Reply, Reply +All or Forward. PLEASE NOTE: The mockups are based on what the app +looks like today. We have not included any additional fields in the +detail view that are part of the stamping spec ie: Send via, Sent By, +Edited By etc. We don't know how much of this work will get done in +Alpha4 and did not add it since it's unrelated to the email work.<br> +</p> +<p><br> +<img alt="" src="" style="width: 1025px; height: 721px;"><br> +</p> +<br> +<p><img alt="" src="" style="width: 1025px; height: 721px;"><br> +</p> +<p><br> +<img alt="" src="" style="width: 1025px; height: 721px;"><br> +</p> +<p> </p> +<h2>Beta/1.0 Email</h2> +<h3>Implementation Details</h3> +<h2>Special Considerations</h2> +<h3>QA / Test</h3> +<h3>API / Developer Platform</h3> +<h3>Security</h3> +<h3>Internationalization / Localization</h3> +<h3>Accessibility</h3> +<p>UI must be accessible (Section 508).</p> +<h3>Build / Install</h3> +</div> +<div id="codicille"> +<h2>Cuts</h2> +<p>Handle CONFIDENTIAL or PRIVATE events specially.</p> +<h2>Useful Links</h2> +<ul> + <li><a href="" doc</a></li> + <li><a href="" doc</a></li> + <li><a href="" doc</a></li> +</ul> +<h2>History</h2> +<table width="100%"> + <tbody> + <tr> + <th width="15%">Author</th> + <th width="15%">Edit date</th> + <th width="70%">Description</th> + </tr> + <tr> + <td><a href="" PROTECTED]">Sheila Mooney</a></td> + <td>Mar 21, 2006</td> + <td>First draft of search spec<br> + </td> + </tr> + </tbody> +</table> +</div> +</body> +</html> Property changes on: trunk/docs/specs/rel0_7/Email-0.7.html ___________________________________________________________________ Name: svn:mime-type + text/html Name: svn:eol-style + native
_______________________________________________ Commits mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/commits
