Sugar Architecture/API: Difference between revisions
| Line 61: | Line 61: | ||
== Sugar Packs == |
== Sugar Packs == |
||
This details the contents and structure of OLPC Build |
This details the contents and structure of OLPC Build 303. |
||
=== [[Sugar Architecture/API/Sugar Python Scripts|Sugar Python Scripts]] === |
=== [[Sugar Architecture/API/Sugar Python Scripts|Sugar Python Scripts]] === |
||
| Line 74: | Line 74: | ||
* sugar-emulator |
* sugar-emulator |
||
* sugar-emulator-shutdown |
* sugar-emulator-shutdown |
||
* sugar-nm-applet - removed [[303]] |
|||
* sugar-install-bundle - added [[303]] |
* sugar-install-bundle - added [[303]] |
||
* sugar-presence-service |
* sugar-presence-service |
||
| Line 108: | Line 107: | ||
Modules: |
Modules: |
||
* [[Sugar Architecture/API/sugar.shell.shellservice | sugar.shell.shellservice]] - added [[303]] |
* [[Sugar Architecture/API/sugar.shell.shellservice | sugar.shell.shellservice]] - added [[303]] |
||
* [[Sugar Architecture/API/sugar.shell.hardwaremanager | sugar.shell.HardwareManager]] - removed [[303]] |
|||
Subpackages: |
Subpackages: |
||
Revision as of 13:50, 14 March 2007
Sugar is written in Python and uses a variety of open source packages. Programming in the Sugar environment requires a basic understanding of the Sugar user interface, supporting third-party packages, and built-in Sugar packages.
Traditional software packages are built against application programming interfaces. Sugar runs Activities instead of applications, but from a developer's point of view, it's the same thing.
Third Party Packages
- Abiword - Document writer
- ATK - GNOME Accessibility Toolkit
- Avahi - network service discovery system
- GTK - GNOME Toolkit
- gstreamer - multimedia framework
- Cairo - 2-D graphics library
- D-BUS - message bus service
- Evince - document viewer
- HippoCanvas - generic user interface widget
- Matchbox - graphical windows manager
- Pango - GTK package for text rendering
- X Window System - the tried-and-true ancient X11 display libraries
- Xul - XML User Interface Language
Sugar Packs
This details the contents and structure of OLPC Build 303.
Sugar Python Scripts
Several Python Scripts reside in /usr/bin
Scripts:
- sugar-activity
- sugar-activity-factory
- sugar-clipboard
- sugar-console
- sugar-data-store
- sugar-emulator
- sugar-emulator-shutdown
- sugar-install-bundle - added 303
- sugar-presence-service
- sugar-presence-service2 - added 303
- sugar-setup-activity
- sugar-shell
Sugar Library Packages
Many Sugar library packages reside in /usr/lib/python*/site-packages/sugar
Modules:
- TracebackUtils
- date - added 303
- emulator
- env
- logger
- profile
- simulator
- util
Subpackages:
Package sugar.shell
Most of the Human Interface is implemented in the sugar.shell packages located in /usr/share/sugar/shell
Modules:
- sugar.shell.shellservice - added 303
Subpackages:
- sugar.shell.console
- sugar.shell.hardware - added 303
- sugar.shell.intro - added 303
- sugar.shell.model
- sugar.shell.view
Package sugar.services
Various services are provided in /usr/share/sugar/services
Modules: none
Subpackages:
- sugar.services.clipboard
- sugar.services.console
- sugar.services.datastore
- sugar.services.nm - removed 303
- sugar.services.presence
- sugar.services.presence2 303
Sugar Activity APIs
The previous API sections detail all Sugar interfaces. Here is an abbreviated list of the APIs most relevant for activity programming:
gtk gobject hippo logging os pango pygtk
sugar.activity.activity sugar.graphics sugar.date