View source for OpenmokoFramework
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to OpenmokoFramework.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to OpenmokoFramework.
Note: This is the (ongoing) description of the new framework architecture. See OpenmokoOldFramework for the framework architecture of 2007.1 and 2007.2
This initiative does not cover low level services such as
This initiative does not cover high level services such as
Note: V0.9 :-) Need to update it soon
We differenciate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.
This is about peripheral control, i.e. managing power for individual subsystems such as
It's also about access to
It will monitor the user's activity to
TBD
TBD
TBD
We base on the official Linux Bluetooth subsystem here, which is BlueZ.
TBD
We base on Gypsy here.
Wifi USB Options: Networkmanager or Intel Connection Manager
TBD Reference Geoclue
Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the Dbus APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.
Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, if necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.
Michael 'Mickey' Lauer Guillaume Chereau Jan 'Shoragan' Luebbe Holger 'Zecke' Freyther
Milestone 1:
Milestone 2:
Milestone 3: