Sugar Architecture: Difference between revisions
Jump to navigation
Jump to search
m (→[[Sugar Architecture/API | API]]: add Activity API link) |
m (→[[Sugar Architecture/API | API]]: Rename Activity DBus API) |
||
| Line 11: | Line 11: | ||
* [[API | Sugar APIs]] |
* [[API | Sugar APIs]] |
||
* [[Presence Service DBus API]] |
* [[Presence Service DBus API]] |
||
* [[Activity |
* [[Activity DBus API]] |
||
* [[HippoCanvas]]: Cairo drawing and UI layout widget |
* [[HippoCanvas]]: Cairo drawing and UI layout widget |
||
Revision as of 10:03, 22 May 2007
The Sugar Interface acts as the primary user interface for most children using an OLPC laptop. It runs as a graphical shell on top of a trimmed down implementation of Redhat's Fedora implementation of a Linux operating system. Python has been selected as the primary development language for sugar.
Specifications
API
- Sugar APIs
- Presence Service DBus API
- Activity DBus API
- HippoCanvas: Cairo drawing and UI layout widget
Third party packages
- Avahi service discovery layer
- Cairo 2D graphics library (Python interface)
- Pango text layout library (Python interface)
- GTK+ user interface (Python interface)
- D-Bus interprocess communications system (Python interface)