Development Team/Resources

From Sugar Labs
< Development Team
Revision as of 14:25, 19 January 2009 by Sascha silbe (talk | contribs) (→‎Tutorials: fix links (pages are all on, not
Jump to navigation Jump to search

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

DevelopmentTeam/Sugar Architectual Diagram


PyGTK developers will find a collection of Tutorials available, from very simple Hello World projects to an in-depth description of the development of Block Party.

Pygame developers will likely want to start with:

Etoys/Smalltalk developers will want to start with Smalltalk Development on XO.

Other developers will want to read about Sugarizing non-Python applications.


  • API Reference -- pointers to the various libraries' reference documentation.

You can also run the pydoc script on an XO in order to have browseable pydoc documentation locally. To do this, open a Terminal activity and run:

 pydoc -p 8080

then open a Web Browser activity and go to the url:


to view the documentation. This approach works best with Python-coded libraries which have spent some time on their docstrings (and generally requires that you know English, as most docstrings are written in English).


  • The Developer's Category collects everything in the wiki that's been tagged as pertaining to developers (it's a bit hard to navigate)
  • Sugar Code Snippets a few canonical code fragments that may be of use when coding in PyGTK

Beginner's tools

Link to Andrew's course in the Overview chapter of the Extending Sugar section of the FLOSS manual for Sugar (

  1. The Byte of Python (
  2. How to Think Like a Computer Scientist: Learning with Python, 2nd edition (
  3. Python for Fun (
  4. Python Bibliotheca (
  5. Dive into Python (
  6. Hands-on Python Tutorial (
  7. Snake Wrangling for Kids (
  8. PyGame (scattered throughout the site) (

Please feel free to add other suggested resources to the ones already there and to add some feedback, e.g., good for beginners/experts, etc.


The Developer's FAQ is large enough to merit its own page in the Developer's manual.


As with most Open Source software projects, we have difficulties with documentation. We are very interested in finding people interested in documenting the system. If you are too shy about your coding skills to write code, helping us document the code-base would be an amazing and valuable contribution.

Helping organize the wiki (the web site you are currently reading) to better document the platform and development process would also be very helpful.

Wade's handy links list

Pulling the source to an existing activity from Git:

Creating a new activity:

For PyGTK activities:

For PyGame activities:

For video playback using gstreamer:

For supporting collaboration:

Submitting to OLPC:

Previous Next