Changes

<div style="background-color: #FFF; margin-left:auto; margin-right: auto; width: 95%;">

<div style="background-color: #FFF; margin-left:auto; margin-right: auto; width: 95%;">

{{hig-subnav-intra|p_page=Introduction|c_section=Activities|c_page=Activity Basics|n_page=Activity Bundles}}

{{hig-subnav-intra|p_page=Introduction|c_section=Activities|c_page=Activity Basics|n_page=Activity Bundles}}{{TOCright}}

===Starting Activities===

===Starting Activities===

Activities appear in the Actions section of the frame; starting an activity amounts to creating an active instance of it, represented in the activity ring. They can be started with a single click. An activity may also be directly manipulated; dragging an activity into the ring will also create a new active instance of it.  

Activities appear in the Actions section of the frame; starting an activity amounts to creating an active instance of it, represented in the activity ring. They can be started with a single click. An activity may also be directly manipulated; dragging an activity into the ring will also create a new active instance of it.  

Visual cues differentiate between instances of an activity and the [[OLPC Human Interface Guidelines/The Sugar Interface/Icons#Activity Icons|activity icon]] in the frame. Specifically, any activity installed on the system and appearing in the Actions edge is drawn as a white outline stroke, with no fill. Upon instantiation the icon receives a fill; both [[OLPC Human Interface Guidelines/The Sugar Interface/Icons#Strokes & Fills|stroke and fill colors]]  match the XO colors of the child who created it.

Visual cues differentiate between instances of an activity and the [[Human Interface Guidelines/The Sugar Interface/Icons#Activity Icons|activity icon]] in the frame. Specifically, any activity installed on the system and appearing in the Actions edge is drawn as a white outline stroke, with no fill. Upon instantiation the icon receives a fill; both [[Human Interface Guidelines/The Sugar Interface/Icons#Strokes & Fills|stroke and fill colors]]  match the XO colors of the child who created it.

====Private Activities====

====Private Activities====

Newly created activity instances inherit the scope of the view in which they are created. This means that any activity started from the Home view begins as a private one by default. Children may later [[OLPC Human Interface Guidelines/Activities/Activity Basics#Sharing_Activities|share]] private activities, opening them up to friends, classmates, or anyone on the mesh through an [[OLPC Human Interface Guidelines/Activities/Activity Basics#Invitations|explicit invitation]].

Newly created activity instances inherit the scope of the view in which they are created. This means that any activity started from the Home view begins as a private one by default. Children may later [[Human Interface Guidelines/Activities/Activity Basics#Sharing_Activities|share]] private activities, opening them up to friends, classmates, group members, or anyone on the mesh through an [[Human Interface Guidelines/Activities/Activity Basics#Invitations|explicit invitation]].

====Shared Activities====

====Shared Activities====

Since newly created activities inherit the scope of the view, any activity started directly from the Friends view will be open for friends to participate. [[OLPC Human Interface Guidelines/Activities/Activity Basics#Implicit_Invitations|Implicit invitations]] are sent to all of the friends in the view, alerting them of the activity. Likewise, any activity started from the (unfiltered) Mesh view will be open to everyone on the mesh, although invitations are not sent.

Since newly created activities inherit the scope of the view, any activity started directly from the Friends Group view will be open for her friends to participate in. This applies to any group the child belongs to as well.  [[Human Interface Guidelines/Activities/Activity Basics#Implicit_Invitations|Implicit invitations]] are sent to all of the members of the currently selected Group, alerting them of the activity. Likewise, any activity started from the (unfiltered) Mesh view will be open to everyone on the mesh, although invitations are not sent.

The views provide scope for instantiating activities. For finer granularity, the search (located in the Frame) provides an incremental filtering system that enables arbitrary selection of scope. As a query is entered into the search field, the view&mdash;Friends or Mesh&mdash;dynamically updates to reveal the matching selection. Matches remain in color, while those filtered out appear with a white outline. The filter terms apply parameters such as the names of activities, the types of activities, the names of individuals, and the interests of individuals.  For instance, a child could search for anyone who likes games before starting a new game of Memory, or everyone in the same grade in a classroom setting, or a specific group of individuals by name. The results of the query become the scope for any new activity instance, and all XOs within that scope receive implicit invitations when an activity begins. These groupings may be saved as groups for future use.

The views provide scope for instantiating activities. For finer granularity, the search (located in the Frame) provides an incremental filtering system that enables arbitrary selection of scope. As a query is entered into the search field, the view&mdash;Friends or Mesh&mdash;dynamically updates to reveal the matching selection. Matches remain in color, while those filtered out appear with a white outline. The filter terms apply parameters such as the names of activities, the types of activities, the names of individuals, and the interests of individuals.  For instance, a child could search for anyone who likes games before starting a new game of Memory, or everyone in the same grade in a classroom setting, or a specific group of individuals by name. The results of the query become the scope for any new activity instance, and all XOs within that scope receive implicit invitations when an activity begins. These groupings may be saved as groups for future use.

===Sharing Activities===

===Sharing Activities===

Activities may begin as private, or private to a small group of individuals. There may be occasion to open up activities to a broader scope. For instance, a class may break into groups to work on a project within private group activities. At the end of the session, all groups may wish to open up their activities to the rest of the class for discussion and critique. Through selection in the activities contextual rollover, one may set the scope of people who may join an activity to one of Private, Friends, and Mesh, or a saved group.

Activities may begin as private, or restricted to a small group of individuals. There may be occasion to open up activities to a broader scope. For instance, a class may break into groups to work on a project within private group activities. At the end of the session, all groups may wish to open up their activities to the rest of the class for discussion and critique. Through selection in the activities contextual rollover, one may set the scope of children who may join an activity to one of Private, Mesh, or any specific Group to which she belongs, including her class, her friends, and potentially others.

A child may lock activities in a similar manner, tightening an activity's scope. Participants must leave on their own volition or at the request of others within the activity before locking it.

A child may lock activities in a similar manner, tightening an activity's scope. Participants must leave on their own volition or at the request of others within the activity before locking it.

Explicit invitations are used to invite specific individuals into already active activities.  The ability to send explicit invitations to others serves particular use when in a private activity, be it a private group or a solitary one.  In these cases, an explicit invitation can extend the group by including one or more specific individuals, without opening up the activity to a broader scope.

Explicit invitations are used to invite specific individuals into already active activities.  The ability to send explicit invitations to others serves particular use when in a private activity, be it a private group or a solitary one.  In these cases, an explicit invitation can extend the group by including one or more specific individuals, without opening up the activity to a broader scope.

A child may initiate an explicit invitation either from within the activity itself or by identifying an individual or group in either the Friends or Neighborhood views.

A child may initiate an explicit invitation either from within the activity itself or by identifying an individual or group in either the Groups or Neighborhood views.

====Implicit Invitations====

====Implicit Invitations====

Implicit invitations do not require specific action on the part of the child. These invitations go to the appropriate individuals whenever actions suggest it, such as when starting an activity from the Friends or Neighborhood views. All individuals within the activity's scope receive implicit invitations to join. When an activity is resumed, those who participated previously receive an invitation.

Implicit invitations do not require specific action on the part of the child. These invitations go to the appropriate individuals whenever actions suggest it, such as when starting an activity from the Groups or Neighborhood views. All individuals within the activity's scope receive implicit invitations to join. When an activity is resumed, those who participated previously receive an invitation.

====Receiving Invitations====

====Receiving Invitations====

Incoming invitations appear within the [[OLPC Human Interface Guidelines/The Laptop Experience/The Frame#Actions|Actions]] section of the Frame, adjacent to the installed activities; they are rendered in the color of the inviter. Rollover reveals both the name of the inviter as well as the name and type of the activity.  On extended rollover, the options to accept and decline appear. There is an optional message back to the inviter upon declining and invitation.

Incoming invitations appear within the [[Human Interface Guidelines/The Laptop Experience/The Frame#Actions|Actions]] section of the Frame, adjacent to the installed activities; they are rendered in the color of the inviter. Rollover reveals both the name of the inviter as well as the name and type of the activity.  On extended rollover, the options to accept and decline appear. There is an optional message back to the inviter upon declining an invitation.

===Notifications===

===Notifications===

Notifications behave similarly to Invitations; they also appear in the [[OLPC Human Interface Guidelines/The Laptop Experience/The Frame#Actions|Actions]] edge of the frame.  However, unlike invitations, which are sent from people on the mesh, Notifications come from activities or directly from the system. As new notifications come in, they form a queue, with the most recent in the lower left-hand corner for quick access.

Notifications behave similarly to Invitations; they also appear in the [[Human Interface Guidelines/The Laptop Experience/The Frame#Actions|Actions]] edge of the frame.  However, unlike invitations, which are sent from people on the mesh, Notifications come from activities or directly from the system. As new notifications come in, they form a queue, with the most recent in the lower left-hand corner for quick access.

====Sticky Notifications====

====Sticky Notifications====

{{hig-subnav-intra|p_page=Introduction|c_section=Activities|c_page=Activity Basics|n_page=Activity Bundles}}

{{hig-subnav-intra|p_page=Introduction|c_section=Activities|c_page=Activity Basics|n_page=Activity Bundles}}