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
... picture ...
... discussion of subsystem purposes ...
...
This involves three components:
We base on the official Linux Bluetooth subsystem here, which is BlueZ.
Options: Networkmanager or Intel Connection Manager
We base on Gypsy here.
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 reimplementing some of the services with daemons written in Vala. Reimplementing things in Pyrex/RPython could be easier and many of the benefits of python would remain.
... talk about the team and the roadmap ...