Difference between revisions of "Human Interface Guidelines/Core Ideas"

From Sugar Labs
Jump to navigation Jump to search
Line 17: Line 17:
 
|}
 
|}
  
−
There are no [http://en.wikipedia.org/wiki/Software_Application software applications] in the traditional sense on the laptop. The laptop focuses children around "[[OLPC Human Interface Guidelines/Activities|activities]]." This is more than a new naming convention; it represents an intrinsic quality of the learning experience we hope the children will have when using the laptop. Activities are distinct from applications in their foci—collaboration and expression—and their implementation—journaling and iteration.
+
There are no [http://en.wikipedia.org/wiki/Software_Application software applications] in the traditional sense on the laptop. The laptop focuses children around "[[OLPC Human Interface Guidelines/Activities|activities]]." This is more than a new naming convention; it represents an intrinsic quality of the learning experience we hope the children will have when using the laptop. Activities are distinct from applications in their foci
−
 
 
−
===Presence is Always Present===
 
−
{|border=1 cellpadding=1 cellspacing=0 style="float: right; width: 175px; border: 1px #666666 solid; border-collapse: collapse; background: #f9f9f9;"
 
−
!style="background:#D6784C"|API Reference
 
−
|-
 
−
|[[Sugar Architecture/API/sugar.presence|Sugar Library Package: sugar.presence]]
 
−
|}
 
−
 
 
−
Everyone has the potential for being both a learner and a teacher.  We have chosen to put collaboration at the core of the user experience in order to realize this potential. The presence of other members of the learning community will encourage children to take responsibility for others' learning as well as their own. The exchange of ideas amongst peers can both make the learning process more engaging and stimulate critical thinking skills. We hope to encourage these types of social interaction with the laptops.
 
−
 
 
−
In order to facilitate a collaborative learning environment, the laptops employ a mesh network that interconnects all laptops within range. By exploiting this connectivity, every activity has the potential to be a networked activity. We aspire that all activities take advantage of the mesh; any activity that is not mesh-aware should perhaps be rethought in light of connectivity.  As an example, consider the web-browsing activity bundled with the laptop distribution. Normally one browses in isolation, perhaps on occasion sending a friend a favorite link. On the laptop, however, a link-sharing feature integrated into the browser activity transforms the solitary act of web-surfing into a group collaboration. Where possible, all activities should embrace the mesh and place strong focus on facilitating such collaborative processes.
 
−
 
 
−
===Tools of Expression===
 
−
 
 
−
Starting from the premise that we want to make use of what people already know in order to make connections to new knowledge, our approach focuses on thinking, expressing, and communicating with technology. The laptop is a "thing to think with"; we hope to make the primary activity of the children one of creative expression, in whatever form that might take. Thus, most activities will focus on the creation of some type of object, be it a drawing, a song, a story, a game, or a program. In another shift in the language used to describe the user experience, we refer to objects rather than files as the primary stuff of creative expression.
 
−
 
 
−
As most software developers would agree, the best way to learn how to write a program is to write one, or perhaps teach someone else how to do so; studying the syntax of the language might be useful, but it doesn't teach one how to code. We hope to apply this principle of "learn through doing" to all types of creation, e.g., we emphasise composing music over downloading music. We also encourage the children to engage in the process of collaborative critique of their expressions and to iterate upon this expression as well.
 
−
 
 
−
The objectification of the traditional filesystem speaks more directly to real-world metaphors: instead of a sound file, we have an actual sound; instead of a text file, a story. In order to support this concept, activity developers may define object types and associated icons to represent them.
 
−
 
 
−
===Journaling===
 
−
 
 
−
The concept of the [[OLPC Human Interface Guidelines/The Laptop Experience#The Journal|Journal]], a written documentation of everyday events, is generally understood, albeit in various forms across cultures. A journal typically chronicles the activities one has done throughout the day. We have chosen to adopt a journal metaphor for the filesystem as our basic approach to file organization. While the underlying implementation of such a filesystem does not differ significantly from some of those in contemporary operating systems, it also holds less importance than the journal abstraction itself.
 
−
 
 
−
At its core, our journal concept embodies the idea that the filesystem records a history of the things a child has done, or, more specifically, the activities a child has participated in.  Its function as the store of the objects created while performing those activities is secondary, although also important. The Journal naturally lends itself to a chronological organization (although it can be tagged, searched, and sorted by a variety of means).  As a record of things a child has ''done''—not just the things a child has ''saved''—the Journal will read much like a portfolio or scrapbook history of the child's interactions with the machine and also with peers. The Journal combines entries explicitly created by the children with those which are implicitly created through participation in activities; developers must think carefully about how an activity integrates with the Journal more so than with a traditional filesystem that functions independently of an application. The activities, the objects, and the means of recording all tightly integrate to create a different kind of computer experience.
 
−
 
 
−
</div>{{hig-nav|prev=Introduction|curr=Core Ideas|next=Design Fundamentals}}</div>
 
−
<noinclude>
 
−
 
 
−
 
 
−
</div></noinclude>
 

Revision as of 20:39, 28 August 2007

Template:OLPC

english | español | 한국어 | português HowTo [ID# 15585]  +/-  



Core Ideas

Activities, Not Applications

API Reference
Sugar Activity APIs

There are no software applications in the traditional sense on the laptop. The laptop focuses children around "activities." This is more than a new naming convention; it represents an intrinsic quality of the learning experience we hope the children will have when using the laptop. Activities are distinct from applications in their foci

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Human_Interface_Guidelines/Core_Ideas&oldid=15585"