Documentation

From OLPC
Jump to navigation Jump to search

OLPC hardware and software is designed to be discoverable so that a user can figure things out by experimentation. We are preparing teachers by extensively lecturing and writing about how the devices might be leveraged. The OLPC laptops will come with e-books documenting how to use them, and technical details needed by application developers are available on the web including this wiki.

Examples: see the user interface guidelines and a draft developers handbook.

There are many audiences for the laptops and their software and content; some of them may need to create their own instructional material, or their own versions of existing material. This wiki is open for development of such material. If you have created your own documentation -- for instance, text, screenshots, video or animation for the hardware or specific software that is being turned into an activity -- note it here.

TODO

We need to improve speed/accuracy of 

() noting the need for pascals doc
() making sure it gets created
(*) integrating it with other such docs in a organizing framework
() having an organizing framework 
() keeping the docs up to date / tagged with freshness indicators

Needs

  • Comments in code -- clean up, write for children, translate, in synthesis make the code "readable" and localizable.
  • Notes about development -- how to create a 'hello world' activity or bundle. This is intented to be in Activity_Template and others.
  • Community introduction -- getting to know and collab with the social community of developers and supporting groups
  • Packaging/downloading guide -- how to package, where to publish, how to find and download.(stable and unstable documentation)
  • Testing guide -- how to write test plans, who tests, how to help test, how to read the results of automated / human tests.
  • Build/release guide -- how builds are made how often, where they end up; stable v unstable; how an activity gets into a buld, how to build a costomized build.
  • Fix and organize different types and pages of documentation that are spread in the wiki.

Specific examples

Educational materials

In-activity documentation

  • Etoys quick-guides (click the "?" icon in tool bar)

Wikitexts

Images/Pictures

  • (from christina xu... to find on Flickr)

Tutorials

Videos

Notes

Current work

See the thread http://lists.laptop.org/pipermail/devel/2007-October/thread.html#7008 , especially http://lists.laptop.org/pipermail/devel/2007-October/007008.html .

Demo videos

Demonstration videos take much more space than text documents, but may be more accessible to pre-literate users, and require less translation.

Record a laptop being used. Creating such videos might be an interesting project for kids, and something for cross-school sharing.

Record a desktop session. This can provide clearer and smaller video, be simpler than recording someone using the laptop, and be more characteristics-of-user neutral. It can be mixed with video of someone using a laptop. Since only the screen can be seen, it can't be used to show physical manipulation of the laptop (pressing buttons, etc). Istanbul, the Gnome desktop session recorder, can be used to record the window of an emulated xo, or of a real xo with remote display.

Record a laptop's own screen. Alt-1 takes still screenshots. Perhaps we could set things up so users could also take video, making their own desktop session videos.

Lego - children's documentation done well

Lego building blocks do children's docs well. Cross culture and cross reading-ability (or "no" reading ability).

http://www.lego.com/en-US/default.aspx
http://www.lego.com/eng/buildinginstructions/
Any in particular? MitchellNCharity 14:33, 16 October 2007 (EDT)

Some key points:

  • Use of pictures (line drawings also, to exclude unimportant details)
  • No reliance on prior knowledge of how things fit together or of systems thinking
  • Task-based picture instruction to accomplish tasks while teaching systems thinking

Laptop CAD model for creating illustrations

A CAD model of the laptop exists. But is not yet public. It could be used to generate illustrations. http://dev.laptop.org/ticket/2650


Handbook

A handbook for developers, teachers, contributors, and laptop-users. For other handbooks and higher-level discussion, see Documentation.


Background

OLPC is an education project for children, building tools for stimulating children's creativity, starting with a children's laptop, a child-friendly desktop interface, and communities of learning and creation dedicated to children's education around the world.

How can I get involved?

Who works on OLPC?

Designers, hardware manufacturers, firmware developers (Men Of FORTH), Linux kernel and systems developers, activity developers (esp python, javascript, actionscript, C), database and interface designers, localization fanatics, game developers, authors, translators, artists, musicians, media encoding experts...


Where does everyone hang out?

Developers primarily hang out on a few IRC channels : #sugar for activity and interface development, #olpc for general discussion and OS/kernel hacking, #olpc-content for content and library development and localization.

Community members have a few other channels : #olpc-es for spanish-language discussion, and low-traffic channels for specific pilots and countries (peru, brasil).

The OLPC wiki has a lot of means of knowing how and why to do things related to the xo.

Sugar

Emulating Sugar

jhbuild

VMWare and QEMU

Sugar Activities and Bundles

Bundle formats

Example Activities

Other example bundles


This page needs clean-up and editing for coherence, clarity, and completeness.

Please improve this article if you can.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Documentation&oldid=73544"