Specifications/Object Transfers

From OLPC
< Specifications
Revision as of 18:51, 24 March 2008 by Eben (talk | contribs) (New page: ==Visual Spec== ==Interaction Spec== ===Example=== 1. Child A initiates an object transfer by one of the following means: clicking on the send-to button in the Journal toolbar; selecti...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Visual Spec

Interaction Spec

Example

1. Child A initiates an object transfer by one of the following means: clicking on the send-to button in the Journal toolbar; selecting the send-to option in the palette for a given object; dragging/dropping an object onto the XO icon of a buddy.
2. Child A receives a notification.  The notification indicates the person who the transfer has been offered to, the object to be transferred (call it O) including type and title, and the option to cancel the transfer.
2. Child B receives a notification.  The notification indicates the person who initiated the transfer (child A), the object to be transferred (object O) including type and title, and the options to accept or decline the transfer.
3. When child B accepts the transfer, a progress segment gets added to the notifications of both A and B.  This segment indicates visually the percentage transferred, and offers an approximate time remaining.  Additionally, both A and B receive a progress entry in their Journal which indicates the same information that the notification held.
4. When the transfer finishes, both A and B receive another notification to indicate this.  The corresponding Journal entry becomes a standard entry.  A's reads "Sent O to B".  B's reads "Received O from A".
5. Should the transfer cancel or fail, A notification should indicate this.  The corresponding Journal entry becomes a standard entry. A's reads "The transfer of O to B (was cancelled | failed)".  B's reads "The transfer of O from A (was cancelled | failed)".