[Design] Updated stamping spec

[Sheila Mooney]

Grant, Bryan S, Mimi, Philippe and I met a couple of weeks ago to  
review the stamping work we are going to be doing in Alpha5 -  
specifically the visual affordances for supporting the edit/updating.  
Based on that meeting, there were a few clarifications we wanted to  
make which I have added to the spec.

http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ 
Stamping-0.7.html

Since the edits are scattered throughout the document, here is the  
summary Mimi gave me...

ADDRESSING FIELDS

The TO, CC, and BCC fields display either valid email addresses or  
invalid strings. Proposed workflow for checking email addresses when  
sending messages.
1. Send button activates as soon as we have entered any text into the  
TO, CC or BCC fields. (Currently, we can only detect this upon  
committing out of the field. In the future, we would like to be able  
to do without having to commit out of the field.)

2. User hits the Send button.

3. Chandlers checks for valid email addresses.

4a. If invalid email addresses are detected, then we throw up a  
dialog box that says:
You have addressed this message to invalid email addresses.
[Fix email addresses] [Send anyway]

4b. If there are no valid email addresses, we throw up a dialog that  
says:
Message cannot be sent. You have not entered any valid email addresses.
[Okay]


Bullet point rules for what appears in the Send via/Sent via/Edited  
by/Updated by....on....
Send via appears if:
+ Item has been stamped to be Addressed as a message
+ Item has not been Sent yet

Sent by...on... appears if:
+ Item has been Sent for the first time

Edited by appears if:
+ Item has been edited, regardless of whether it has been Sent/ 
Updated or not

Updated by...on... appears if:
+ Item has been


Which Addressing fields are editable
+ Send via:
+ Edited by:
+ FROM, TO, CC, BCC


Which Addressing fields aren't editable
+ Sent by...on...
+ Updated by...on...


What data types display in the Addressing fields
+ FROM displays a Contact Name
+ TO, CC, BCC displays email addresses or strings
+ Send via/Sent via/Updated by displays emails addresses
+ Edited by displays email address if it's a communication
+ Edited by displays Contact Name (aka me email address for now) if  
it's not a communication at all

IF/WHEN we move to a model where email accounts include both incoming  
and outgoing mail servers/accounts, the Send via/Sent via field  
should display user-defined account names rather than email addresses.


===
THE WHO COLUMN

How to determine Perspective: Is a message INBOUND, OUTBOUND or NEUTRAL?
+ If you're in the From field, it's an OUTBOUND communication and you  
see who the message is TO in the Who column
+ If you're in the TO, CC, BCC, its an INBOUND communication and you  
see who the message is FR or ED or UP in the Who column
+ If you're in the TO, CC or BCC field AND you've Updated an item,  
it's now an OUTBOUND communication and you see who the message is TO  
in the Who column
+ If you're in the TO, CC, or BCC field AND you've Sent an item, it's  
an OUTBOUND communication and you see who the message is TO in the  
Who column
+ If you're in none of these fields, the item is NEUTRAL and you see  
both who the message is FR and TO


The Who column sorts on the contact listed in the column, not on a  
particular attribute, e.g. FR or TO


===
COMMUNICATION STATUS

Priorities for which Communication Statuses to implement first.
1. Read, Unread, Needs reply
2. In versus Out
3. Error
4. Draft versus Not Draft
5. 1st time sent/received versus subsequent Updated
6. Queued


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