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.
Languages: |
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català |
Key pages on: FSO |
|
---|
s/Openmoko/freesmartphone.org/ :)
Openmoko is basing on the freesmartphone.org (FSO) middleware. FSO will be in the forthcoming Om 2009 distribution. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.
... to be defined ...
This initiative does not cover low level services such as
This initiative does not cover high level services such as
Please see the description at http://www.freesmartphone.org/index.php/Architecture
Attach the logs to the tickets, please.
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 D-Bus 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.
The milestone releases are combined Openmoko Framework and Zhone releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does not exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.
Note: The milestones and tasks moved over to our issue tracker.