Sugar Architecture/API: Difference between revisions
| Line 47: | Line 47: | ||
== Third Party Packages == |
== Third Party Packages == |
||
*[[Abiword]] - Document writer |
*[[Abiword]] - Document writer |
||
*[[ATK]] - GNOME Accessibility Toolkit |
*[[Software_components#Libraries_and_Plugins|ATK]] - GNOME Accessibility Toolkit |
||
*[[Software_components#Libraries_and_Plugins|Avahi]] - Network Discovery Service |
*[[Software_components#Libraries_and_Plugins|Avahi]] - Network Discovery Service |
||
*[[GTK for OLPC|GTK]] - GNOME Toolkit |
*[[GTK for OLPC|GTK]] - GNOME Toolkit |
||
| Line 56: | Line 56: | ||
*[[HippoCanvas]] - Cairo compatible Drawing tool |
*[[HippoCanvas]] - Cairo compatible Drawing tool |
||
*[[Matchbox]] - Graphical Windows Manager |
*[[Matchbox]] - Graphical Windows Manager |
||
*[[Pango]] - GTK package for text rendering |
*[[Software_components#Libraries_and_Plugins|Pango]] - GTK package for text rendering |
||
*[[X Window System]] - the tried-and-true ancient X11 display libraries |
*[[X Window System]] - the tried-and-true ancient X11 display libraries |
||
*[[Xul]] - XML User Interface Language (aka gecko and other identity challenged projects) |
*[[Xul]] - XML User Interface Language (aka gecko and other identity challenged projects) |
||
Revision as of 14:58, 13 March 2007
Sugar is written in Python with a variety of open source packages. Programming in the Sugar environment requires a basic understanding of both 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 Discovery Service
- GTK - GNOME Toolkit
- gstreamer - media player
- Cairo
- D-BUS - Message Bus service
- Evince - Document viewer
- HippoCanvas - Cairo compatible Drawing tool
- 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 (aka gecko and other identity challenged projects)
Sugar Packs
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-nm-applet
- sugar-presence-service
- sugar-setup-activity
- sugar-shell
Sugar Library Packages
Many Sugar Library packages reside in /usr/lib/python*/site-packages/sugar
Modules:
- TracebackUtils
- 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:
Subpackages:
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
- sugar.services.presence
Sugar Activity APIs
The previous API sections detail all sugar interfaces. Here is an abbreviated list of the APIs most relevant for activity programming:
- TBD