Human Interface Guidelines/Core Ideas/lang-pt-br - Revision history

FGrose at 02:34, 27 August 2009

2009-08-27T02:34:27Z

← Older revision		Revision as of 22:34, 26 August 2009
Line 1:		Line 1:
	<noinclude><div style="background-color: #F5F5F5;">		<noinclude><div style="background-color: #F5F5F5;">
	{{Translation \| lang = pt \| source = ~~Design_Team/~~Human_Interface_Guidelines/Core Ideas \| version = ~~27062~~ \| source_display = ~~OLPC-~~HIG-Core Ideas}}		{{Translation \| lang = pt \| source = Human_Interface_Guidelines/Core Ideas \| version = 32759 \| source_display = HIG-Core Ideas}}
	{{Ongoing Translation}}		{{Ongoing Translation}}
	<!-- Iniciando tradução - Caroll -->		<!-- Iniciando tradução - Caroll -->
Line 19:		Line 19:
	\|}		\|}
	<!-- FIXME - traduzir journaling nesse paragrafo -->		<!-- FIXME - traduzir journaling nesse paragrafo -->
	Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[~~Design Team/~~Human Interface Guidelines/Activities\|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.		Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[Human Interface Guidelines/Activities\|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.

	{{anchor\|Presence is Always Present}}		{{anchor\|Presence is Always Present}}
Line 47:		Line 47:
	===Journaling===		===Journaling===

	The concept of the [[~~Design Team/~~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.		The concept of the [[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.		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.

FGrose: moved Design Team/Human Interface Guidelines/Core Ideas/lang-pt-br to Human Interface Guidelines/Core Ideas/lang-pt-br: restructure

2009-07-07T12:59:27Z

moved Design Team/Human Interface Guidelines/Core Ideas/lang-pt-br to Human Interface Guidelines/Core Ideas/lang-pt-br: restructure

← Older revision	Revision as of 08:59, 7 July 2009
(No difference)

Dfarning: fix broken links

2009-04-09T02:06:18Z

fix broken links

← Older revision		Revision as of 22:06, 8 April 2009
Line 16:		Line 16:
	!style="background:#D6784C"\|API Reference		!style="background:#D6784C"\|API Reference
	\|-		\|-
	\|[~~[Sugar Architecture~~/~~API#Sugar_Activity_APIs\|~~Sugar ~~Activity APIs]~~]		\|[http://api.sugarlabs.org/ Sugar]
	\|}		\|}
	<!-- FIXME - traduzir journaling nesse paragrafo -->		<!-- FIXME - traduzir journaling nesse paragrafo -->

Dfarning: fix broken links

2009-04-09T00:15:56Z

fix broken links

← Older revision		Revision as of 20:15, 8 April 2009
Line 1:		Line 1:
	<noinclude><div style="background-color: #F5F5F5;">		<noinclude><div style="background-color: #F5F5F5;">
	~~{{OLPC}}~~		{{Translation \| lang = pt \| source = Design_Team/Human_Interface_Guidelines/Core Ideas \| version = 27062 \| source_display = OLPC-HIG-Core Ideas}}
	{{Translation \| lang = pt \| source = ~~OLPC Human Interface Guidelines~~/Core Ideas \| version = 27062 \| source_display = OLPC-HIG-Core Ideas}}
	{{Ongoing Translation}}		{{Ongoing Translation}}
	<!-- Iniciando tradução - Caroll -->		<!-- Iniciando tradução - Caroll -->

Dfarning: fix camelcase links

2009-04-07T22:23:04Z

fix camelcase links

← Older revision		Revision as of 18:23, 7 April 2009
Line 20:		Line 20:
	\|}		\|}
	<!-- FIXME - traduzir journaling nesse paragrafo -->		<!-- FIXME - traduzir journaling nesse paragrafo -->
	Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[~~DesignTeam~~/Human Interface Guidelines/Activities\|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.		Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[Design Team/Human Interface Guidelines/Activities\|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.

	{{anchor\|Presence is Always Present}}		{{anchor\|Presence is Always Present}}
Line 48:		Line 48:
	===Journaling===		===Journaling===

	The concept of the [[~~DesignTeam~~/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.		The concept of the [[Design Team/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.		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.

Dfarning: DesignTeam/Human Interface Guidelines/Core Ideas/lang-pt-br moved to Design Team/Human Interface Guidelines/Core Ideas/lang-pt-br

2009-04-07T22:05:21Z

DesignTeam/Human Interface Guidelines/Core Ideas/lang-pt-br moved to Design Team/Human Interface Guidelines/Core Ideas/lang-pt-br

← Older revision	Revision as of 18:05, 7 April 2009
(No difference)

Dfarning-bot: Robot: Automated text replacement (-[OLPC Human +[DesignTeam/Human)

2009-02-05T13:12:33Z

Robot: Automated text replacement (-[OLPC Human +[DesignTeam/Human)

← Older revision		Revision as of 09:12, 5 February 2009
Line 20:		Line 20:
	\|}		\|}
	<!-- FIXME - traduzir journaling nesse paragrafo -->		<!-- FIXME - traduzir journaling nesse paragrafo -->
	Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[~~OLPC~~ Human Interface Guidelines/Activities\|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.		Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[DesignTeam/Human Interface Guidelines/Activities\|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.

	{{anchor\|Presence is Always Present}}		{{anchor\|Presence is Always Present}}
Line 48:		Line 48:
	===Journaling===		===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.		The concept of the [[DesignTeam/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.		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.

Dfarning-bot: OLPC Human Interface Guidelines/Core Ideas/lang-pt-br moved to DesignTeam/Human Interface Guidelines/Core Ideas/lang-pt-br: Robot: moved page

2009-02-05T02:02:00Z

OLPC Human Interface Guidelines/Core Ideas/lang-pt-br moved to DesignTeam/Human Interface Guidelines/Core Ideas/lang-pt-br: Robot: moved page

← Older revision	Revision as of 22:02, 4 February 2009
(No difference)

Dfarning: 11 revisions

2009-02-04T18:37:40Z

11 revisions

New page

<noinclude><div style="background-color: #F5F5F5;">
{{OLPC}}
{{Translation | lang = pt | source = OLPC Human Interface Guidelines/Core Ideas | version = 27062 | source_display = OLPC-HIG-Core Ideas}}
{{Ongoing Translation}}

</noinclude>
<div style="background-color: #FFF; margin-left:auto; margin-right: auto; border-left:1px solid #888; border-right:1px solid #888; width: 95%;">
{{hig-nav-lang | prev=Introduction | curr=Core Ideas | next=Design Fundamentals | lang=pt-br}}
<div style="margin: 8px;">
{{anchor|Core Ideas}}
==Idéias Principais==

{{anchor|Activities, Not Applications}}
===Atividades, Não Aplicações===

{|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_Activity_APIs|Sugar Activity APIs]]
|}

Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[OLPC Human Interface Guidelines/Activities|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.

{{anchor|Presence is Always Present}}
===Presença é Sempre Presente===

{|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]]
|}

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.

Para facilitar um ambiente de aprendizagem colaborativo, os laptops utilizam uma rede mesh que interconecta todos os laptops dentro da range. Explorando esta conectividade, cada atividade tem o potencial para ser uma atividade em rede. Nós aspiramos que todas as atividades tomem vantagem do mesh; alguma atividade que não seja baseada em mesh deve talvez ser repensada sob à luz da conectividade. Como um exemplo, considere o conjunto de atividades do navegador web com a distribuição do laptop. Normalmente uma procura isolada, talvez numa ocasião enviando a um amigo um link favorito. No laptop, entretanto, um recurso integrado de troca de links dentro da atividade de procura transforma um ato solitário de navegar na web em um grupo de colaboração. Onde possivelmente, todas as atividades devem abranger o mesh e focar fortemente na posição de facilitar tais processos colaborativos.

{{anchor|Tools of Expression}}
===Ferramentas de Expressão===

Partindo da premissa que nós desejamos fazer uso do que as pessoas já conhecem a fim de fazer conexões para novos conhecimentos, nossa aproximação está focada em pensar, expressar e comunicar com tecnologia. O laptop é uma "coisa para pensar com"; nós esperamos tornar a expressão criativa uma atividade primária das crianças, em qualquer forma que possa tomar. Assim, a maioria das atividades focará na criação de algum tipo de objeto, seja ele um desenho, uma música, uma história, um jogo ou um programa. Em outra mudança na linguagem usada para descrever a experiência do usuário, nós nos referimos a objetos melhor que à arquivos como material principal à expressão criativa.

Como a maioria do desenvolvedores de software concordaria, a melhor maneira de aprender como escrever um programa é escrever um, ou talvez ensinar outra pessoa a fazer; estudar a sintaxe da linguagem pode ser útil, mas isto não ensina como programar. Nós esperamos aplicar o princípio de "aprender fazendo" para todos os tipos de criação, por exemplo, nós enfatizamos compor músicas sobre músicas baixadas. Nós também encorajamos as crianças a dedicar-se ao processo de crítica colaborativa das suas expressões e iterar-se sobre esta expressão também.

A do sistema de arquivos tradicional fala mais diretamente às metáforas do mundo real: em vez de um arquivo de som, nós temos um som real; em vez de um arquivo de texto, uma história. Para suportar este conceito, os desenvolvedores da atividade podem definir tipos de objeto e ícones associados para representá-los.


{{anchor|Journaling}}
===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-lang | prev=Introduction | curr=Core Ideas | next=Design Fundamentals | lang=pt-br}}</div>
<noinclude></div></noinclude>

200.195.150.81 at 15:59, 15 May 2007

2007-05-15T15:59:23Z

New page

<noinclude><div style="background-color: #F5F5F5;">
{{OLPC}}
{{Translation | lang = pt | source = OLPC Human Interface Guidelines/Core Ideas | version = 27062 | source_display = OLPC-HIG-Core Ideas}}
{{Ongoing Translation}}

</noinclude>
<div style="background-color: #FFF; margin-left:auto; margin-right: auto; border-left:1px solid #888; border-right:1px solid #888; width: 95%;">
{{hig-nav-lang | prev=Introduction | curr=Core Ideas | next=Design Fundamentals | lang=pt-br}}
<div style="margin: 8px;">
<div id="Core Ideas"/>
==Idéias Principais==

<div id="Activities, Not Applications"/>
===Atividades, Não Aplicações===

{|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_Activity_APIs|Sugar Activity APIs]]
|}

Não há [http://en.wikipedia.org/wiki/Software_Application software aplicativo] no sentido tradicional no laptop. O laptop foca crianças em torno de "[[OLPC Human Interface Guidelines/Activities|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.

<div id="Presence is Always Present"/>
===Presença é Sempre Presente===

{|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]]
|}

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.

Para facilitar um ambiente de aprendizagem colaborativo, os laptops utilizam uma rede mesh que interconecta todos os laptops dentro da range. Explorando esta conectividade, cada atividade tem o potencial para ser uma atividade em rede. Nós aspiramos que todas as atividades tomem vantagem do mesh; alguma atividade que não seja baseada em mesh deve talvez ser repensada sob à luz da conectividade. Como um exemplo, considere o conjunto de atividades do navegador web com a distribuição do laptop. Normalmente uma procura isolada, talvez numa ocasião enviando a um amigo um link favorito. No laptop, entretanto, um recurso integrado de troca de links dentro da atividade de procura transforma um ato solitário de navegar na web em um grupo de colaboração. Onde possivelmente, todas as atividades devem abranger o mesh e focar fortemente na posição de facilitar tais processos colaborativos.

<div id="Tools of Expression"/>
===Ferramentas de Expressão===

Partindo da premissa que nós desejamos fazer uso do que as pessoas já conhecem a fim de fazer conexões para novos conhecimentos, nossa aproximação está focada em pensar, expressar e comunicar com tecnologia. O laptop é uma "coisa para pensar com"; nós esperamos tornar a expressão criativa uma atividade primária das crianças, em qualquer forma que possa tomar. Assim, a maioria das atividades focará na criação de algum tipo de objeto, seja ele um desenho, uma música, uma história, um jogo ou um programa. Em outra mudança na linguagem usada para descrever a experiência do usuário, nós nos referimos a objetos melhor que à arquivos como material principal à expressão criativa.

Como a maioria do desenvolvedores de software concordaria, a melhor maneira de aprender como escrever um programa é escrever um, ou talvez ensinar outra pessoa a fazer; estudar a sintaxe da linguagem pode ser útil, mas isto não ensina como programar. Nós esperamos aplicar o princípio de "aprender fazendo" para todos os tipos de criação, por exemplo, nós enfatizamos compor músicas sobre músicas baixadas. Nós também encorajamos as crianças a dedicar-se ao processo de crítica colaborativa das suas expressões e iterar-se sobre esta expressão também.

A do sistema de arquivos tradicional fala mais diretamente às metáforas do mundo real: em vez de um arquivo de som, nós temos um som real; em vez de um arquivo de texto, uma história. Para suportar este conceito, os desenvolvedores da atividade podem definir tipos de objeto e ícones associados para representá-los.


<div id="Journaling"/>
===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-lang | prev=Introduction | curr=Core Ideas | next=Design Fundamentals | lang=pt-br}}</div>
<noinclude></div></noinclude>