OLPC Human Interface Guidelines/Activities/Introduction: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
Line 4: Line 4:


===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. "Open" and "Save" actions are relegated to a journal interaction; creating a new instance of the Draw activity implicitly creates a new drawing. To "open" an older drawing, 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 [[#Resuming_Activities|resume]] it.





Revision as of 19:53, 29 November 2006

[[OLPC Human Interface Guidelines/{{{p_link}}}|{{{p_label}}}]] [[OLPC Human Interface Guidelines/{{{c_link}}}|{{{c_label}}}]] [[ talk:OLPC Human Interface Guidelines/{{{c_link}}}|(discussion)]] [[OLPC Human Interface Guidelines/{{{n_link}}}|{{{n_label}}}]]


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.


[[OLPC Human Interface Guidelines/{{{p_link}}}|{{{p_label}}}]] [[OLPC Human Interface Guidelines/{{{c_link}}}|{{{c_label}}}]] [[ talk:OLPC Human Interface Guidelines/{{{c_link}}}|(discussion)]] [[OLPC Human Interface Guidelines/{{{n_link}}}|{{{n_label}}}]]