273
edits
Changes
Jump to navigation
Jump to search
Line 89:
Line 89: − + − +
Activity Team/Resources (view source)
Revision as of 14:34, 19 February 2009
, 14:34, 19 February 2009→References
* http://www.pygtk.org/docs/pygobject/index.html PyGObject API reference. Contains a few important things missing from the PyGTK API such as timers and idle callbacks.
* http://www.pygtk.org/docs/pygobject/index.html PyGObject API reference. Contains a few important things missing from the PyGTK API such as timers and idle callbacks.
* http://api.sugarlabs.org/ The official Sugar API documentation (quite sparse but includes all the source code).
* http://api.sugarlabs.org/ The official Sugar API documentation (quite sparse but includes all the source code).
* http://sugarlabs.org/go/DevelopmentTeam/Almanac Detailed Sugar API overview. Quite in depth and offers answers to common questions.
* [[DevelopmentTeam/Almanac]] Detailed Sugar API overview. Quite in depth and offers answers to common questions.
* http://pygstdocs.berlios.de/ Python GStreamer bindings.
* http://pygstdocs.berlios.de/ Python GStreamer bindings.
* http://sugarlabs.org/go/DesignTeam/Human_Interface_Guidelines The design behind the Sugar interface. Very important to read and understand before planning your activity's user interface.
* [[DesignTeam/Human_Interface_Guidelines]] The design behind the Sugar interface. Very important to read and understand before planning your activity's user interface.
* http://cairographics.org/documentation/pycairo/ Cairo Python API reference. Very sparse, use the tutorial instead.
* http://cairographics.org/documentation/pycairo/ Cairo Python API reference. Very sparse, use the tutorial instead.
* http://wiki.laptop.org/go/Low-level_Activity_API Information on how activities interact with Sugar.
* http://wiki.laptop.org/go/Low-level_Activity_API Information on how activities interact with Sugar.