The document provides an overview of the Chinook software architecture. It describes the major components which include GNU/Linux, X, GLib, D-Bus, GTK+, Pango, Cairo, ATK, Hildon Desktop, Matchbox, Hildon Toolkit, GnomeVFS, GConf, GStreamer, BlueZ, E-D-S, Telepathy, LibConIC. It also discusses the logical and development views of the architecture, differences from other mobile operating systems, and challenges and achievements of the architecture.
9. Architecture overview - processes Important system software processes dsme C Device State Management Entity, a watchdog bme C Battery Management Entity mce C Mode Control (e.g. offline, device lock, leds) dbus-daemon C system&session, IPC for a desktop session, launches singleton applications, lifecycle tracking maemo-launcher C speeds up application startup
10. Architecture overview - processes User interface server processes hildon-desktop hildon-input-method sapwood-server - theme engine matchbox-window-manager clipboard-manager
14. Differences to other mobile operating systems builds on existing open source desktop components all basic frameworks¨ source code available applications do not need signing SDK open source development environment free software ITOS contains also closed parts
15. Architecture overview - challenges Architecture heritage from GTK+ and GNOME Multiple APIs for the application developer Upstream APIs naturally change maemo specific APIs Documentation/API quality varies a lot Native application development language is C Not many available standards in mobile Linux ´ it is a hacker¨s world both in good and bad!
16. Architecture overview - achievements avoided ^not invented here ̄ largely same software components as in a normal GNU/Linux desktop maemo is an open embedded mobile platform embrace existing policies (e.g. Debian packaging) support existing de facto standards porting existing desktop software made easy