Changes

{{Translations  

{{Translations  

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

   | [[Documentation Team|english]] | [[Documentation Team/lang-es|español]] }}

<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>

<noinclude>{{TeamHeader|Documentation Team|home=Documentation}}</noinclude>

== Mission ==

== Sugar FLOSS manual ==

FLOSS Manuals held a BookSprint during the last week of August 2008 in Austin, TX; together, we wrote separate but combinable (remixable) manuals for Sugar, individual Sugar Activities and the hardware it may run on, such as the XO.

Our mission is to provide the Sugar community with high quality documentation, including user manuals, programming references, and tutorials.

The manuals for a number of Sugar Activities are now published (including manuals for [http://en.flossmanuals.net/write_activity '''Write'''], [http://en.flossmanuals.net/terminal '''Terminal'''], [http://en.flossmanuals.net/chat '''Chat'''], [http://en.flossmanuals.net/browse '''Browse'''], [http://en.flossmanuals.net/record '''Record'''], and [http://en.flossmanuals.net/turtleart '''Turtle Art''']).

People "remixed" these manuals to form the [[Activities/Help|Help activity]] for the XO laptop; a version of this is on the web at http://laptop.org/manual/

Please help us improve these manuals by going to http://en.flossmanuals.net/write where the editable versions reside. Note that we are including tutorials and notes to parents and teachers as part of the documentation effort. Helping expanding these sections would be greatly appreciated.

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 .

FLOSS Manuals is planning a BookSprint for the last week of August in Austin, TX, to put together separate but combinable (remixable) manuals for Sugar and the hardware it may run on, such as the XO. Here are rough working outlines:

Those who participated include: Adam Hyde, Anne Gentle, David Farning, Mikus Grinbergs, Brian Jordan, Adam Holt, Janet Swisher, Morgan Collett, Yama Ploskonka, David Cramer, Emily Kaplan, Faisal Anwar, Christoph Derndorfer, Sandy Culver, Aaron Konstam, and the Sugar community.  

Sugar Manual

We are translating the Sugar FLOSS manual into

'''See also'''

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

See also

* [http://wiki.laptop.org/go/OLPC_Publications OLPC Publications] in the OLPC Wiki.

* [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]  

* OLPC Austria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]

Topic Ideas

==Topic Ideas==

* Setup a development environment.  With and without jhbuild.

* Setup a development environment.  With and without jhbuild.

* "Write your activity" tutorial.  It should include:

* "Write your activity" tutorial.  It should include:

=== [http://api.sugarlabs.org API] ===

=== [http://api.sugarlabs.org API] ===

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

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

References  

References  

* http://wiki.laptop.org/go/API_reference?

* 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.

* 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].

* Existing collaboration documentation is at [http://wiki.laptop.org/go/Category:Collaboration Collaboration].

:* 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]]

:* 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]]

::* 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)

::* 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.

* 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  

:this is the page http://wiki.laptop.org/go/Low-level_Activity_API (see [[Development Team/Low-level Activity API]]) but it must be complemented with  

:* http://wiki.laptop.org/go/Sugar_Factory

:* http://wiki.laptop.org/go/Sugar_Factory

:* http://www.catmoran.com/olpc/#sugxterm

:* http://www.catmoran.com/olpc/#sugxterm

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

* 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?

* Etoys based activity tutorial - we now have an Etoys Activity manual set up on FLOSS Manuals. Feel free to contribute here: [http://en.flossmanuals.net/bin/view/Etoys/WebHome|Etoys]

 

 

 

 

 

 

== Glossary ==

== Glossary ==

[[DocumentationTeam/Glossary | Glossary]]

[[Documentation Team/Glossary | Glossary]]

 

 

 

[[Category:DocumentationTeam]]

[[Category:Documentation Team]]

[[Category:Team]]