Sugar Labs - User contributions [en]

Documentation Team/lang-es

2008-08-02T16:07:49Z

Alejo:

{{Translations
| [[DocumentationTeam|english]] | [[DocumentationTeam/lang-es|español]] }}

Nuestra Misión es proveer la comunidad de sugar con alta calidad de documentación, incluyendo manuales de usuario, referencias de programación y tutoriales

{{ Translated text|
Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.
| display = none}}

{{anchor|User Manuals}}
== Manuales de Usuario ==

Estaremos trabajando con [http://flossmanuals.net/about manuales FLOSS] para crear nuestra documentación o la del usuario. Una excelente guía de inicio está en [http://flossmanuals.net/OLPC_simple OLPC simple]. El trabajo en progreso se enlista en DocumentationTeam/KnowledgeBase .

{{ Translated text|
We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .
| display = none}}

Vea también
* [http://wiki.laptop.org/go/OLPC_Publications Publicaciones de OLPC] En el Wiki de OLPC.
* OLPC Austria [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Manual de Actividades]

Ideas del Programa
* Establecer un ambiente de desarrollo. con y sin jhbuild
* Tutorial "Escribe tu actividad". Debería incluir:
** Controles gráficos.
** Alamcen datos
** Colaboración

{{ Translated text|
See also
* [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.
* OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]

Topic Ideas
* Setup a development environment. With and without jhbuild.
* "Write your activity" tutorial. It should include:
** graphic controls,
** datastore,
** collaboration.| display = none}}

La [[DocumentationTeam/API_Documentation | guía API ]] explica cómo iniciarse en la documentación del API.

Referencias
* http://wiki.laptop.org/go/API_reference?
* Probablemente deberíamos documentar el almacén de datos dbus API. No estoy seguro de cual es la mejor forma de generar la documentación para ello. Es tan pequeño que una página del wiki podría ser la solución más simple por ahora.
* La documentación de colaboración existente está en [http://wiki.laptop.org/go/Category:Colaboración].
:* Mi impresión después de 3 minutos de ver la documentación disponible es que hay muy poco escrito con los autores de la actividad en mente, y que esta dispersa en varias páginas y se mezcla con la aplicación de documentos. ¿Es correcta esta impresión? Me gustaría tener un par de cosas: 1 documentación completa del API que involucren a autores de la actividad (con buenos enlaces a la documentación dbus ya que esto es usado de forma muy pesada) 2 Un completo tutorial como parte del "manual".Una de las páginas se ve como un buen comienzo en este sentido.¿Tiene sentido para usted? ¿podemos hacer que suceda? -- [[User:Marcopg|Marcopg]]
::* Si podemos! --[[User:Morgs|Morgs]] 13:50, 16 de Mayo de 2008 (UTC)
::* Hey, vine con una implementación de referencia "alterna" para la colaboración cuando escribí colores!, pienso que es mucho más fácil de entender y podría ser la base para un buen tutorial.La única cosa extraña es que quería que la clase de mi actividad recibiera señales DBus directamente entonces la volví subclase de ExportedGObject, pero se demora inicializando. Hacky, lo se. Sería muy bueno pero no es necesario!
[http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579]
[[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)
* API de bajo nivel(Actividades que no son python). Podríamos mover la documentación de bert a este wiki
:Esta es la pagina http://wiki.laptop.org/go/Low-level_Activity_API pero deberia ser complementada con
:* http://wiki.laptop.org/go/Sugar_Factory
:* http://www.catmoran.com/olpc/#sugxterm

{{ Translated text|
The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.

References
* http://wiki.laptop.org/go/API_reference?
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].

:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]
::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)
::* Hey, I came up with an alternate "reference" implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)
* Low level API (non-python activities). We should just move bert document on this wiki.
:this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with
:* http://wiki.laptop.org/go/Sugar_Factory
:* http://www.catmoran.com/olpc/#sugxterm
| display = none}}

{{anchor|Tutorials}}
== Tutoriales ==
* Probablemente seria bueno tener un tutorial de Pygame, es probablemente lo mejor que tenemos hasta el momento para hacer gráficos libres.
* Tutorial basado en la actividad Etoys?

{{ Translated text|
* Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.
* Etoys based activity tutorial?
| display = none}}

{{anchor|Glossary}}
== Glosario ==
[[DocumentationTeam/Glossary | Glosario]]

[[Category:DocumentationTeam]]

{{ Translated text|
[[DocumentationTeam/Glossary | Glossary]]
[[Category:DocumentationTeam]]
| display = none}}

Documentation Team/lang-es

2008-08-02T16:06:25Z

Alejo:

{{Translations
| [[DocumentationTeam|english]] | [[DocumentationTeam/lang-es|español]] }}

Nuestra Misión es proveer la comunidad de sugar con alta calidad de documentación, incluyendo manuales de usuario, referencias de programación y tutoriales

{{ Translated text|
Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.
| display = none}}

{{anchor|User Manuals}}
== Manuales de Usuario ==

Estaremos trabajando con [http://flossmanuals.net/about manuales FLOSS] para crear nuestra documentación o la del usuario. Una excelente guía de inicio está en [http://flossmanuals.net/OLPC_simple OLPC simple]. El trabajo en progreso se enlista en DocumentationTeam/KnowledgeBase .

{{ Translated text|
We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .
| display = none}}

Vea también
* [http://wiki.laptop.org/go/OLPC_Publications Publicaciones de OLPC] En el Wiki de OLPC.
* OLPC Austria [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Manual de Actividades]

Ideas del Programa
* Establecer un ambiente de desarrollo. con y sin
* Tutorial "Escribe tu actividad". Debería incluir:
** Controles gráficos.
** Alamcen datos
** Colaboración

{{ Translated text|
See also
* [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.
* OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]

Topic Ideas
* Setup a development environment. With and without jhbuild.
* "Write your activity" tutorial. It should include:
** graphic controls,
** datastore,
** collaboration.| display = none}}

La [[DocumentationTeam/API_Documentation | guía API ]] explica cómo iniciarse en la documentación del API.

Referencias
* http://wiki.laptop.org/go/API_reference?
* Probablemente deberíamos documentar el almacén de datos dbus API. No estoy seguro de cual es la mejor forma de generar la documentación para ello. Es tan pequeño que una página del wiki podría ser la solución más simple por ahora.
* La documentación de colaboración existente está en [http://wiki.laptop.org/go/Category:Colaboración].
:* Mi impresión después de 3 minutos de ver la documentación disponible es que hay muy poco escrito con los autores de la actividad en mente, y que esta dispersa en varias páginas y se mezcla con la aplicación de documentos. ¿Es correcta esta impresión? Me gustaría tener un par de cosas: 1 documentación completa del API que involucren a autores de la actividad (con buenos enlaces a la documentación dbus ya que esto es usado de forma muy pesada) 2 Un completo tutorial como parte del "manual".Una de las páginas se ve como un buen comienzo en este sentido.¿Tiene sentido para usted? ¿podemos hacer que suceda? -- [[User:Marcopg|Marcopg]]
::* Si podemos! --[[User:Morgs|Morgs]] 13:50, 16 de Mayo de 2008 (UTC)
::* Hey, vine con una implementación de referencia "alterna" para la colaboración cuando escribí colores!, pienso que es mucho más fácil de entender y podría ser la base para un buen tutorial.La única cosa extraña es que quería que la clase de mi actividad recibiera señales DBus directamente entonces la volví subclase de ExportedGObject, pero se demora inicializando. Hacky, lo se. Sería muy bueno pero no es necesario!
[http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579]
[[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)
* API de bajo nivel(Actividades que no son python). Podríamos mover la documentación de bert a este wiki
:Esta es la pagina http://wiki.laptop.org/go/Low-level_Activity_API pero deberia ser complementada con
:* http://wiki.laptop.org/go/Sugar_Factory
:* http://www.catmoran.com/olpc/#sugxterm

{{ Translated text|
The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.

References
* http://wiki.laptop.org/go/API_reference?
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].

:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]
::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)
::* Hey, I came up with an alternate "reference" implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)
* Low level API (non-python activities). We should just move bert document on this wiki.
:this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with
:* http://wiki.laptop.org/go/Sugar_Factory
:* http://www.catmoran.com/olpc/#sugxterm
| display = none}}

{{anchor|Tutorials}}
== Tutoriales ==
* Probablemente seria bueno tener un tutorial de Pygame, es probablemente lo mejor que tenemos hasta el momento para hacer gráficos libres.
* Tutorial basado en la actividad Etoys?

{{ Translated text|
* Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.
* Etoys based activity tutorial?
| display = none}}

{{anchor|Glossary}}
== Glosario ==
[[DocumentationTeam/Glossary | Glosario]]

[[Category:DocumentationTeam]]

{{ Translated text|
[[DocumentationTeam/Glossary | Glossary]]
[[Category:DocumentationTeam]]
| display = none}}

Documentation Team/lang-es

2008-08-02T04:00:10Z

Alejo:

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}</noinclude>

Nuestra Misión es proveer la comunidad de sugar con alta calidad de documentación, incluyendo manuales de usuario, referencias de programación y tutoriales

{{ Translated text|
Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.
| display = none}}

{{anchor|User Manuals}}
== Manuales de Usuario ==

Estaremos trabajando con [http://flossmanuals.net/about manuales FLOSS] para crear nuestra documentación o la del usuario. Su excelente guia de inicio está en [http://flossmanuals.net/OLPC_simple OLPC simple]. El trabajo en progreso se enlista en DocumentationTeam/KnowledgeBase .

{{ Translated text|
We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .
| display = none}}

Vea también
* [http://wiki.laptop.org/go/OLPC_Publications Publicaciones de OLPC] En el Wiki de OLPC.
* OLPC Austria [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Manual de Actividades]

Ideas del programa

* Establecer un ambiente de desarrollo. con y sin
* Tutorial "Escribe tu actividad". Debería incluir:
** Controles gráficos.
** Alamcen datos
** Colaboración

{{ Translated text|
See also
* [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.
* OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]

Topic Ideas
* Setup a development environment. With and without jhbuild.
* "Write your activity" tutorial. It should include:
** graphic controls,
** datastore,
** collaboration.| display = none}}

La [[DocumentationTeam/API_Documentation | guia API ]] explica cómo empezar la documentación de API.

Referencias
* http://wiki.laptop.org/go/API_reference?
* Probablemente deberíamos documentar el almacén de datos dbus API. No estoy seguro de cual es la mejor forma de generar la documentación para ello. Es tan pequeño que una página del wiki podría ser la solución más simple por ahora.
* La documentación de colaboración existente está en [http://wiki.laptop.org/go/Category:Colaboración].
:* Mi impresión después de 3 minutos de ver la documentación disponible es que hay poco escrito con los autores de la actividad en mente, y que esta dispersa en varias páginas y se mezcla con la aplicación de documentos. ¿Es correcta esta impresión? Me gustaría tener un par de cosas: 1 documentación completa del API que involucren a autores de la actividad (con buenos enlaces a la documentación dbus ya que esto es usado de forma muy pesada) 2 Un completo tutorial como parte del "manual".Una de las páginas se ve como un buen comienzo en este sentido.¿Tiene sentido para usted? ¿podemos hacer que suceda? -- [[User:Marcopg|Marcopg]]
::* Si podemos! --[[User:Morgs|Morgs]] 13:50, 16 de Mayo de 2008 (UTC)
::* Hey, vine con una implementacion de referencia "alterna" para la colaboración cuando escribí colores!, pienso que es mucho más fácil de entender y podria ser la base para un buen tutorial.La única cosa extraña es que quería que mi actividad de clase recibiera señales DBus directamente

{{ Translated text|
The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.

References
* http://wiki.laptop.org/go/API_reference?
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].

:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]
::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)
::* Hey, I came up with an alternate "reference" implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)
* Low level API (non-python activities). We should just move bert document on this wiki.
:this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with
:* http://wiki.laptop.org/go/Sugar_Factory
:* http://www.catmoran.com/olpc/#sugxterm
| display = none}}

{{anchor|Tutorials}}
== Tutoriales ==

* Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.
* Etoys based activity tutorial?

{{anchor|Glossary}}
== Glosario ==

[[DocumentationTeam/Glossary | Glossary]]

[[Category:DocumentationTeam]]

Documentation Team/lang-es

2008-08-02T01:05:14Z

Alejo:

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}</noinclude>

Nuestra Misión es proveer la comunidad de sugar con alta calidad de documentación, incluyendo manuales de usuario, referencias de programación y tutoriales

{{ Translated text|
Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.
| display = none}}

{{anchor|User Manuals}}
== Manuales de Usuario ==

Estaremos trabajando con [http://flossmanuals.net/about manuales FLOSS] para crear nuestra documentación o la del usuario. Su excelente guia de inicio está en [http://flossmanuals.net/OLPC_simple OLPC simple]. El trabajo en progreso se enlista en DocumentationTeam/KnowledgeBase .

{{ Translated text|
We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .
| display = none}}

Vea también
* [http://wiki.laptop.org/go/OLPC_Publications Publicaciones de OLPC] En el Wiki de OLPC.
* OLPC Austria [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Manual de Actividades]

Ideas del programa

* Establecer un ambiente de desarrollo. con y sin
* Tutorial "Escribe tu actividad". Debería incluir:
** Controles gráficos.
** Alamcen datos
** Colaboración

{{ Translated text|
See also
* [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.
* OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]

Topic Ideas
* Setup a development environment. With and without jhbuild.
* "Write your activity" tutorial. It should include:
** graphic controls,
** datastore,
** collaboration.| display = none}}

{{anchor|Programming References}}
== Referencias del programa ==
=== [http://api.sugarlabs.org API] ===

La guia API explica cómo empezar la documentación de API.

Referencias
* http://wiki.laptop.org/go/API_reference?
* Probablemente deberíamos documentar el almacén de datos dbus API
{{ Translated text|
The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.

References
* http://wiki.laptop.org/go/API_reference?
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].

:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]
::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)
::* Hey, I came up with an alternate "reference" implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)
* Low level API (non-python activities). We should just move bert document on this wiki.
:this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with
:* http://wiki.laptop.org/go/Sugar_Factory
:* http://www.catmoran.com/olpc/#sugxterm
| display = none}}

== Tutorials ==

* Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.
* Etoys based activity tutorial?

== Glossary ==

[[DocumentationTeam/Glossary | Glossary]]

[[Category:DocumentationTeam]]

Documentation Team/lang-es

2008-08-02T00:53:34Z

Alejo:

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|DocumentationTeam|home=Documentation}}</noinclude>

Nuestra Misión es proveer la comunidad de sugar con alta calidad de documentación, incluyendo manuales de usuario, referencias de programación y tutoriales

{{ Translated text|
Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.
| display = none}}

{{anchor|User Manuals}}
== Manuales de Usuario ==

Estaremos trabajando con [http://flossmanuals.net/about manuales FLOSS] para crear nuestra documentación o la del usuario. Su excelente guia de inicio está en [http://flossmanuals.net/OLPC_simple OLPC simple]. El trabajo en progreso se enlista en DocumentationTeam/KnowledgeBase .

{{ Translated text|
We will be working with [http://flossmanuals.net/about FLOSS manuals] to create our end user documentation. Their excellent getting started guide is at [http://flossmanuals.net/OLPC_simple OLPC simple]. Works in progress are listed in the DocumentationTeam/KnowledgeBase .
| display = none}}

Vea también
* [http://wiki.laptop.org/go/OLPC_Publications Publicaciones de OLPC] En el Wiki de OLPC.
* OLPC Austria [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Manual de Actividades]

Ideas del programa

* Establecer un ambiente de desarrollo. con y sin
* Tutorial "Escribe tu actividad". Debería incluir:
** Controles gráficos.
** Alamcenamiento de datos
** Colaboración

{{ Translated text|
See also
* [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.
* OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]

Topic Ideas
* Setup a development environment. With and without jhbuild.
* "Write your activity" tutorial. It should include:
** graphic controls,
** datastore,
** collaboration.| display = none}}

{{anchor|Programming References}}
== Referencias del programa ==
=== [http://api.sugarlabs.org API] ===

The [[DocumentationTeam/API_Documentation | API guide ]] explains how to get started documenting api.

References
* http://wiki.laptop.org/go/API_reference?
* Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collabration].

:* Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- [[User:Marcopg|Marcopg]]
::* Yes we can! --[[User:Morgs|Morgs]] 13:50, 16 May 2008 (UTC)
::* Hey, I came up with an alternate "reference" implementation for collaboration when I wrote Colors!, I think it's a lot easier to understand and could be the basis for a good tutorial. The only weird thing is, I wanted my activity class to receive DBus signals directly, so I subclassed ExportedGObject but initialized late - hacky, I know. It would be nice if this were not needed! [http://dev.laptop.org/git?p=activities/colors;a=blob;f=colors.py;h=c262f55e46519248418a07e3c4eed1ab4207fa09;hb=5822328cab1162b32452dfb915b33d98307b55d1#l579] [[User:Wade|Wade]] 18:49, 18 May 2008 (UTC)
* Low level API (non-python activities). We should just move bert document on this wiki.
:this is the page http://wiki.laptop.org/go/Low-level_Activity_API but it must be complemented with
:* http://wiki.laptop.org/go/Sugar_Factory
:* http://www.catmoran.com/olpc/#sugxterm

== Tutorials ==

* Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.
* Etoys based activity tutorial?

== Glossary ==

[[DocumentationTeam/Glossary | Glossary]]

[[Category:DocumentationTeam]]

Documentation Team/lang-es

2008-08-01T23:27:34Z

Alejo:

Documentation Team/lang-es

2008-08-01T23:00:19Z

Alejo: New page: <noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show...