Changes

=====Actions=====

=====Actions=====

The bottom edge of the frame functions primarily as an [[#Starting_Activities|activity launcher]], but it also accumulates both incoming [[#Invitations|invitations]] and [[#Notifications|notifications]].  As a starting point for instantiating activities, this part of the frame is fairly straightforward.  Whenever an activity receives a click, a colored instance of that activity appears within the activity ring in the child's own colors, and invitations are automatically sent as appropriate.  On the other hand, anytime she receives an invitation it appears as a colored activity icon (in the color of the inviting XO, of course), clearly distinct from the uncolored outlines of the activities which reside on her own machine.  Since an invitation to join an activity has no functional differences from starting one of her own, the invitations appropriately indicate this by their similar form.  The rollover state for these invitations allows her to accept or decline the invitation, optionally providing a reason for declining.

The bottom edge of the frame functions primarily as an [[OLPC Human Interface Guidelines/Activities/Activity Basics#Starting_Activities|activity launcher]], but it also accumulates both incoming [[OLPC Human Interface Guidelines/Activities/Activity Basics#Invitations|invitations]] and [[OLPC Human Interface Guidelines/Activities/Activity Basics#Notifications|notifications]].  As a starting point for instantiating activities, this part of the frame is fairly straightforward.  Whenever an activity receives a click, a colored instance of that activity appears within the activity ring in the child's own colors, and invitations are automatically sent as appropriate.  On the other hand, anytime she receives an invitation it appears as a colored activity icon (in the color of the inviting XO, of course), clearly distinct from the uncolored outlines of the activities which reside on her own machine.  Since an invitation to join an activity has no functional differences from starting one of her own, the invitations appropriately indicate this by their similar form.  The rollover state for these invitations allows her to accept or decline the invitation, optionally providing a reason for declining.

Notifications, the third aspect of the Actions edge of the frame, function slightly differently.  While they don't represent an activity that she can join, they do come as messages from activities or from the system, conveying important information about the state of the activity or system status such as battery strength or wireless signal.  Though slightly different from activities and invitations, these notifications still require some action on her part, and are an appropriate addition to the frame which provides a convenient way to access them from within any view. Just as in the other edges of the frame, invitations and notifications organize by time, the most recent always in the lower left-hand corner, so that she may handle them in a timely manner.

Notifications, the third aspect of the Actions edge of the frame, function slightly differently.  While they don't represent an activity that she can join, they do come as messages from activities or from the system, conveying important information about the state of the activity or system status such as battery strength or wireless signal.  Though slightly different from activities and invitations, these notifications still require some action on her part, and are an appropriate addition to the frame which provides a convenient way to access them from within any view. Just as in the other edges of the frame, invitations and notifications organize by time, the most recent always in the lower left-hand corner, so that she may handle them in a timely manner.