OLPC Human Interface Guidelines/Activities/Introduction: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<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%;"> |
||
<noinclude>{{Translations}}</noinclude> |
|||
{{hig-subnav| |
{{hig-subnav-inter|p_link=The Laptop Experience/Global Search|p_label=The Laptop Experience|c_section=Activities|c_page=Introduction|n_link=Activities/Activity Basics|n_label=Activity Basics}} |
||
===A New Model=== |
===A New Model=== |
||
We make a distinction between the typical single-application, multi-document model of computing and the OLPC full-screen activity interface, where each object (document) runs within its own instance—multiple instances of a given activity may run in parallel. Activity instances within Sugar provide a way to handle files as objects; each instance may represent a different group of collaborating individuals, and creating a new instance of the Draw activity implicitly creates a new drawing. "Open" and "Save" actions are relegated to a journal interaction; In fact, we strengthen this by replacing the notion of "Saving" with the more general notion of "Keeping" things. To "open" a drawing you've kept, you simply [[#Resuming_Activities|resume]] it. |
We make a distinction between the typical single-application, multi-document model of computing and the OLPC full-screen activity interface, where each object (document) runs within its own instance—multiple instances of a given activity may run in parallel. Activity instances within Sugar provide a way to handle files as objects; each instance may represent a different group of collaborating individuals, and creating a new instance of the Draw activity implicitly creates a new drawing. "Open" and "Save" actions are relegated to a journal interaction; In fact, we strengthen this by replacing the notion of "Saving" with the more general notion of "Keeping" things. To "open" a drawing you've kept, you simply [[OLPC Human Interface Guidelines/Activities/Activity Basics#Resuming_Activities|resume]] it. |
||
{{hig-subnav| |
{{hig-subnav-inter|p_link=The Laptop Experience/Global Search|p_label=The Laptop Experience|c_section=Activities|c_page=Introduction|n_link=Activities/Activity Basics|n_label=Activity Basics}} |
||
</div> |
|||
Latest revision as of 18:44, 15 December 2008
A New Model
We make a distinction between the typical single-application, multi-document model of computing and the OLPC full-screen activity interface, where each object (document) runs within its own instance—multiple instances of a given activity may run in parallel. Activity instances within Sugar provide a way to handle files as objects; each instance may represent a different group of collaborating individuals, and creating a new instance of the Draw activity implicitly creates a new drawing. "Open" and "Save" actions are relegated to a journal interaction; In fact, we strengthen this by replacing the notion of "Saving" with the more general notion of "Keeping" things. To "open" a drawing you've kept, you simply resume it.