OLPC Human Interface Guidelines/Core Ideas/lang-pt-br

From OLPC
< OLPC Human Interface Guidelines‎ | Core Ideas
Revision as of 22:56, 9 May 2007 by 201.15.51.119 (talk) (translating for pt)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  This page is monitored by the OLPC team.
  Please copy/paste "{{Translationlist | xx | origlang=en | translated={{{translated}}}}}" (where xx is ISO 639 language code for your translation) to OLPC Human Interface Guidelines/Core Ideas/lang-pt-br/translations HowTo [ID# 37457]  +/-  
This is an on-going translation


Core Ideas

Atividades, Não Aplicações

API Reference
Sugar Activity APIs

Não há software aplicativo no sentido tradicional no laptop. O laptop foca crianças em torno de "atividades." Esta é mais que uma nova convenção nomeada; ela representa uma qualidade intrínseca da experiência de aprendizagem que nós esperamos que as crianças tenham quando usarem o laptop. Atividades são diferentes de aplicações em seu foco—colaboração e expressão—e sua implementação—journaling e iteração.

Presença é sempre Presente

API Reference
Sugar Library Package: sugar.presence

Todos tem o potencial para ser tanto aluno quanto professor. Nós escolhemos colocar a colaboração no centro da experiência do usuário a fim de realizar este potencial. A presença de outros membros da comunidade de aprendizagem encorajará as crianças a tomar a responsabilidade por outros' aprendendo assim como suas próprias. A troca de idéias entre semelhantes pode também fazer o processo de aprendizagem mais comprometido e estimula a habilidade de pensamento crítico. Nós esperamos encorajar estes tipos de interação social com os 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 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.