Sugar Architecture: Difference between revisions
Jump to navigation
Jump to search
m (→[[Sugar Architecture/API | API]]: Rename Activity_DBus_API to Low-level Activity API) |
(→[[Sugar Architecture/API | API]]: Remove API link which goes to Low Level APIs anyway) |
||
| Line 10: | Line 10: | ||
== [[Sugar Architecture/API | API]] == |
== [[Sugar Architecture/API | API]] == |
||
* [[API | Sugar APIs]] |
|||
| ⚫ | |||
* [[Low-level Activity API]] |
* [[Low-level Activity API]] |
||
| ⚫ | |||
* [[HippoCanvas]]: Cairo drawing and UI layout widget |
* [[HippoCanvas]]: Cairo drawing and UI layout widget |
||
Revision as of 12:49, 17 January 2008
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
- Low-level Activity API
- Presence Service 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)