D-BUS: Difference between revisions
Jump to navigation
Jump to search
(Add descriptions of what the individual pieces are.) |
|||
| Line 3: | Line 3: | ||
== D-BUS Services on the OLPC-XO == |
== D-BUS Services on the OLPC-XO == |
||
* NetworkManager -- Standard Linux desktop component that provides a D-BUS API for controlling network connectivity |
|||
* NetworkManager |
|||
* [[Activity DBus API]] -- Describes the API an activity must implement on D-BUS in order to interact with the [[Sugar]] desktop |
|||
* [[Activity DBus API]] |
|||
** Activity Service (Python implementation of the Activity DBus API) |
** Activity Service (Python implementation of the Activity DBus API) |
||
** Activity Factory Service (Python implementation of the Activity-launching Factory DBus API) |
** Activity Factory Service (Python implementation of the Activity-launching Factory DBus API) |
||
* [[Presence Service DBus API]] |
* [[Presence Service DBus API]] -- friend discovery and collaboration primitives, including a description of the Telepathy API |
||
** Telepathy Connection Manager |
** Telepathy Connection Manager |
||
** Telepathy StreamEngine |
** Telepathy StreamEngine |
||
* Data Store Service (Journal) |
* Data Store Service (Journal) -- the core data-storage operation of the laptop |
||
* Clipboard Service |
* Clipboard Service -- manages cross-activity sharing of data and files |
||
* Hardware Manager Service |
* Hardware Manager Service -- provides access to the OLPC-specific hardware on the laptop |
||
* Activity Registry Service |
* Activity Registry Service -- registry of installed activity bundles on the laptop |
||
* Object Type Registry Service |
* Object Type Registry Service -- MIME-type registry service |
||
* Sugar Console Service |
* Sugar Console Service |
||
Revision as of 19:41, 31 August 2007
D-BUS is a message bus system, rather like Appletalk, that allows applications to send messages to one another. The applications all run on the same CPU. If you look at the Python source code for Sugar you can see how D-BUS is being used.
D-BUS Services on the OLPC-XO
- NetworkManager -- Standard Linux desktop component that provides a D-BUS API for controlling network connectivity
- Activity DBus API -- Describes the API an activity must implement on D-BUS in order to interact with the Sugar desktop
- Activity Service (Python implementation of the Activity DBus API)
- Activity Factory Service (Python implementation of the Activity-launching Factory DBus API)
- Presence Service DBus API -- friend discovery and collaboration primitives, including a description of the Telepathy API
- Telepathy Connection Manager
- Telepathy StreamEngine
- Data Store Service (Journal) -- the core data-storage operation of the laptop
- Clipboard Service -- manages cross-activity sharing of data and files
- Hardware Manager Service -- provides access to the OLPC-specific hardware on the laptop
- Activity Registry Service -- registry of installed activity bundles on the laptop
- Object Type Registry Service -- MIME-type registry service
- Sugar Console Service