OpenmokoFramework

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m (Download and see also: Use correct link to FSOs Trac)
(changing size of headings in order to be consistent with the rest of the wiki)
Line 5: Line 5:
 
FSO is an abbreviation for FreeSmartphone.Org. With FSO, Openmoko is working on a stable system services software back-end. The framework will be used in forthcoming Openmoko distributions -- a demonstration one is available as FSO-image. For more information see http://www.freesmartphone.org and http://trac.freesmartphone.org .
 
FSO is an abbreviation for FreeSmartphone.Org. With FSO, Openmoko is working on a stable system services software back-end. The framework will be used in forthcoming Openmoko distributions -- a demonstration one is available as FSO-image. For more information see http://www.freesmartphone.org and http://trac.freesmartphone.org .
  
=Q/A=
+
==Q/A==
 
* ''Question'': Is this an Openmoko-only thing?
 
* ''Question'': Is this an Openmoko-only thing?
 
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, XanaduX, HTC/iPAQ, ...
 
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, XanaduX, HTC/iPAQ, ...
Line 25: Line 25:
 
* ''Answer'':  See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.
 
* ''Answer'':  See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.
  
= Timeline=
+
== Timeline==
 
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone6 milestone 6]''
 
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone6 milestone 6]''
 
* ''2009-01-30: [http://trac.freesmartphone.org/milestone/milestone5 milestone 5]''
 
* ''2009-01-30: [http://trac.freesmartphone.org/milestone/milestone5 milestone 5]''
Line 33: Line 33:
 
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved
 
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved
  
=Purposes=
+
==Purposes==
 
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
 
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
 
* Support competing UIs while collaborating on developing services
 
* Support competing UIs while collaborating on developing services
 
* Encourage framework users (e.g. application developers) to also contribute to the framework
 
* Encourage framework users (e.g. application developers) to also contribute to the framework
  
=Requirements=
+
==Requirements==
 
* Make it simple
 
* Make it simple
 
* Concentrate on core services
 
* Concentrate on core services
Line 45: Line 45:
 
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API
 
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API
  
=How to achieve that technically=
+
==How to achieve that technically==
 
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
 
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
 
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
 
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
Line 51: Line 51:
 
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars
 
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars
  
=Mandatory Reading=
+
==Mandatory Reading==
 
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
 
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
 
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
 
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
 
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]
 
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]
  
=What this is NOT about=
+
==What this is NOT about==
 
This initiative does not cover low level services such as
 
This initiative does not cover low level services such as
 
* Bootloader, Kernel, or System Init.
 
* Bootloader, Kernel, or System Init.
Line 64: Line 64:
 
* Application Launchers, Applications, or Fancy UIs.
 
* Application Launchers, Applications, or Fancy UIs.
  
=Architectural Overview=
+
==Architectural Overview==
 
[[Image:OpenmokoFramework08.png |823px|frontside]]
 
[[Image:OpenmokoFramework08.png |823px|frontside]]
  
=Software Components=
+
==Software Components==
  
 
We differentiate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.
 
We differentiate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.
  
===Low-Level Services===
+
====Low-Level Services====
  
====Device Control====
+
=====Device Control=====
 
The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as
 
The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as
 
* GSM, WiFi, Bluetooth, GPS, as well as
 
* GSM, WiFi, Bluetooth, GPS, as well as
Line 87: Line 87:
 
* [http://www.freesmartphone.org/index.php/Implementations/OpenDeviceDaemon odeviced]
 
* [http://www.freesmartphone.org/index.php/Implementations/OpenDeviceDaemon odeviced]
  
====Audio====
+
=====Audio=====
 
The low level audio service relies on a working ALSA device driver with the dmix software mixing plugin (*). On top of that, there is the GStreamer streaming media framework:
 
The low level audio service relies on a working ALSA device driver with the dmix software mixing plugin (*). On top of that, there is the GStreamer streaming media framework:
 
* [http://gstreamer.freedesktop.org/ gstreamer]
 
* [http://gstreamer.freedesktop.org/ gstreamer]
Line 94: Line 94:
  
 
*) Initially, we wanted to use PulseAudio on top of ALSA, howver currently it has serious performance problems on this hardware. [http://lists.openmoko.org/pipermail/devel/2008-July/000253.html]
 
*) Initially, we wanted to use PulseAudio on top of ALSA, howver currently it has serious performance problems on this hardware. [http://lists.openmoko.org/pipermail/devel/2008-July/000253.html]
====GSM====
+
=====GSM=====
 
The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon to export virtual serial lines over which -- again -- AT-protocol can be spoken:
 
The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon to export virtual serial lines over which -- again -- AT-protocol can be spoken:
 
* [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd]
 
* [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd]
  
====Bluetooth====
+
=====Bluetooth=====
 
The low level Bluetooth services rely on the official Linux Bluetooth subsystem:
 
The low level Bluetooth services rely on the official Linux Bluetooth subsystem:
 
* [http://www.bluez.org BlueZ].
 
* [http://www.bluez.org BlueZ].
  
====GPS====
+
=====GPS=====
 
The low level GPS services assume a GPS device that talks NMEA over a device node. We implemented an [[ogpsd]] daemon speaking an extended Gypsy API:
 
The low level GPS services assume a GPS device that talks NMEA over a device node. We implemented an [[ogpsd]] daemon speaking an extended Gypsy API:
 
* [http://gypsy.freedesktop.org Gypsy]
 
* [http://gypsy.freedesktop.org Gypsy]
  
====Network====
+
=====Network=====
 
The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:
 
The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:
 
* Intel Connection Manager
 
* Intel Connection Manager
 
* PPP
 
* PPP
  
===High Level===
+
====High Level====
  
====Usage====
+
=====Usage=====
 
The Usage subsystem is concerned with coordinating application I/O requirements. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think ''reference counting'' for I/O requirements.
 
The Usage subsystem is concerned with coordinating application I/O requirements. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think ''reference counting'' for I/O requirements.
  
Line 120: Line 120:
 
See discussion page about PolicyKit.
 
See discussion page about PolicyKit.
  
====Events====
+
=====Events=====
 
* Signalling events via I/O (ringing, blinking, vibrating)
 
* Signalling events via I/O (ringing, blinking, vibrating)
 
* Might use fd.o notification API
 
* Might use fd.o notification API
  
====PIM====
+
=====PIM=====
 
An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description [http://www.neo1973-germany.de/wiki/pyPimd here].
 
An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description [http://www.neo1973-germany.de/wiki/pyPimd here].
  
====Context====
+
=====Context=====
 
* Intelligent context API, integrating location as one -- among other -- sources
 
* Intelligent context API, integrating location as one -- among other -- sources
 
* Geoclue?
 
* Geoclue?
  
====[http://www.freesmartphone.org/index.php/Standards/PhoneAPI Phone]====
+
=====[http://www.freesmartphone.org/index.php/Standards/PhoneAPI Phone]=====
 
The phone subsystem can be used to create and manage voices communications. It makes abstraction of the protocol used.
 
The phone subsystem can be used to create and manage voices communications. It makes abstraction of the protocol used.
  
=== [http://www.freesmartphone.org/index.php/Implementations/OpenPreferencesDaemon Preferences] ===
+
==== [http://www.freesmartphone.org/index.php/Implementations/OpenPreferencesDaemon Preferences] ====
 
* Settings database
 
* Settings database
  
====Network====
+
=====Network=====
 
* High-level networking queries
 
* High-level networking queries
  
=Known API Consumers=
+
==Known API Consumers==
  
 
(TODO: add links...)
 
(TODO: add links...)
Line 149: Line 149:
 
* Paroli
 
* Paroli
  
=Tools=
+
==Tools==
 
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
 
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
 
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
 
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
 
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.
 
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.
  
=How to debug=
+
==How to debug==
 
# log in via ssh
 
# log in via ssh
 
# killall python
 
# killall python
Line 169: Line 169:
 
Attach the logs to the tickets, please.
 
Attach the logs to the tickets, please.
  
=The role of Python=
+
==The role of Python==
  
 
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++.
 
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++.
Line 175: Line 175:
 
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.
 
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.
  
=Team & Roadmap=
+
==Team & Roadmap==
  
==Team==
+
===Team===
  
 
* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
 
* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
Line 184: Line 184:
 
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.
 
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.
  
==Roadmap==
+
===Roadmap===
  
 
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.
 
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.
Line 190: Line 190:
 
'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''
 
'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''
  
== Download and see also ==
+
=== Download and see also ===
  
 
* [http://trac.freesmartphone.org/ Development tracker]
 
* [http://trac.freesmartphone.org/ Development tracker]

Revision as of 17:47, 27 December 2008

Key pages on:
FSO

(Other distributions)


FSO is one of the many distributions that currently work on the Openmoko phones. You can compare a distribution with an Operating System on normal computers. It gives the phone all the software needed for operating. For more information about the different flavors, see distributions.

FSO is an abbreviation for FreeSmartphone.Org. With FSO, Openmoko is working on a stable system services software back-end. The framework will be used in forthcoming Openmoko distributions -- a demonstration one is available as FSO-image. For more information see http://www.freesmartphone.org and http://trac.freesmartphone.org .

Contents

Q/A

Timeline

Purposes

  • Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
  • Support competing UIs while collaborating on developing services
  • Encourage framework users (e.g. application developers) to also contribute to the framework

Requirements

  • Make it simple
  • Concentrate on core services
  • Be programming language agnostic
  • Be UI toolkit agnostic
  • Try to reuse existing technologies as much as possible, but not at the cost of a bad API

How to achieve that technically

  • Choose D-Bus as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
  • Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
  • Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
  • By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

Mandatory Reading

What this is NOT about

This initiative does not cover low level services such as

  • Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as

  • X-Window-System, Window Manager, UI Toolkits,
  • Application Launchers, Applications, or Fancy UIs.

Architectural Overview

frontside

Software Components

We differentiate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.

Low-Level Services

Device Control

The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as

  • GSM, WiFi, Bluetooth, GPS, as well as
  • Backlight brightness and power,
  • Turning LEDs on and off, etc.

It also deals with

  • Charging, suspend/resume,
  • Accelerometers, and buttons.

Last but not least, it sends notifications about the user's activity so that listeners have a chance to

  • Change to powersaving modes, or
  • Lock the device.

We implement the following software for that:

Audio

The low level audio service relies on a working ALSA device driver with the dmix software mixing plugin (*). On top of that, there is the GStreamer streaming media framework:

Gstreamer is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.

  • ) Initially, we wanted to use PulseAudio on top of ALSA, howver currently it has serious performance problems on this hardware. [1]
GSM

The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon to export virtual serial lines over which -- again -- AT-protocol can be spoken:

Bluetooth

The low level Bluetooth services rely on the official Linux Bluetooth subsystem:

GPS

The low level GPS services assume a GPS device that talks NMEA over a device node. We implemented an ogpsd daemon speaking an extended Gypsy API:

Network

The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:

  • Intel Connection Manager
  • PPP

High Level

Usage

The Usage subsystem is concerned with coordinating application I/O requirements. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think reference counting for I/O requirements.

With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.

See discussion page about PolicyKit.

Events
  • Signalling events via I/O (ringing, blinking, vibrating)
  • Might use fd.o notification API
PIM

An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description here.

Context
  • Intelligent context API, integrating location as one -- among other -- sources
  • Geoclue?
Phone

The phone subsystem can be used to create and manage voices communications. It makes abstraction of the protocol used.

Preferences

  • Settings database
Network
  • High-level networking queries

Known API Consumers

(TODO: add links...)

Tools

  • mdbus -- a dbus introspection and interaction utility,
  • cli-framework -- a python dbus command line interface.
  • mickeyterm -- a MUXer-aware minimal terminal emulator.

How to debug

  1. log in via ssh
  2. killall python
  3. edit /etc/frameworkd.conf and add to the frameworkd section:
    1. log_level = DEBUG
    2. log_to = file
    3. log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
  4. Read our documented frameworkd.conf configuration file to learn about the other options.
  5. relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
  6. log in via ssh (yes, again)
  7. export DISPLAY=:0.0
  8. run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

The role of Python

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.

Team & Roadmap

Team

Roadmap

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.

Download and see also

Personal tools
Key pages on:
FSO

(Other distributions)


FSO is one of the many distributions that currently work on the Openmoko phones. You can compare a distribution with an Operating System on normal computers. It gives the phone all the software needed for operating. For more information about the different flavors, see distributions.

FSO is an abbreviation for FreeSmartphone.Org. With FSO, Openmoko is working on a stable system services software back-end. The framework will be used in forthcoming Openmoko distributions -- a demonstration one is available as FSO-image. For more information see http://www.freesmartphone.org and http://trac.freesmartphone.org .

Q/A

Timeline

Purposes

  • Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
  • Support competing UIs while collaborating on developing services
  • Encourage framework users (e.g. application developers) to also contribute to the framework

Requirements

  • Make it simple
  • Concentrate on core services
  • Be programming language agnostic
  • Be UI toolkit agnostic
  • Try to reuse existing technologies as much as possible, but not at the cost of a bad API

How to achieve that technically

  • Choose D-Bus as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
  • Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
  • Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
  • By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

Mandatory Reading

What this is NOT about

This initiative does not cover low level services such as

  • Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as

  • X-Window-System, Window Manager, UI Toolkits,
  • Application Launchers, Applications, or Fancy UIs.

Architectural Overview

frontside

Software Components

We differentiate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.

Low-Level Services

Device Control

The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as

  • GSM, WiFi, Bluetooth, GPS, as well as
  • Backlight brightness and power,
  • Turning LEDs on and off, etc.

It also deals with

  • Charging, suspend/resume,
  • Accelerometers, and buttons.

Last but not least, it sends notifications about the user's activity so that listeners have a chance to

  • Change to powersaving modes, or
  • Lock the device.

We implement the following software for that:

Audio

The low level audio service relies on a working ALSA device driver with the dmix software mixing plugin (*). On top of that, there is the GStreamer streaming media framework:

Gstreamer is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.

  • ) Initially, we wanted to use PulseAudio on top of ALSA, howver currently it has serious performance problems on this hardware. [1]

GSM

The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon to export virtual serial lines over which -- again -- AT-protocol can be spoken:

Bluetooth

The low level Bluetooth services rely on the official Linux Bluetooth subsystem:

GPS

The low level GPS services assume a GPS device that talks NMEA over a device node. We implemented an ogpsd daemon speaking an extended Gypsy API:

Network

The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:

  • Intel Connection Manager
  • PPP

High Level

Usage

The Usage subsystem is concerned with coordinating application I/O requirements. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think reference counting for I/O requirements.

With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.

See discussion page about PolicyKit.

Events

  • Signalling events via I/O (ringing, blinking, vibrating)
  • Might use fd.o notification API

PIM

An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description here.

Context

  • Intelligent context API, integrating location as one -- among other -- sources
  • Geoclue?

Phone

The phone subsystem can be used to create and manage voices communications. It makes abstraction of the protocol used.

Preferences

  • Settings database

Network

  • High-level networking queries

Known API Consumers

(TODO: add links...)

Tools

  • mdbus -- a dbus introspection and interaction utility,
  • cli-framework -- a python dbus command line interface.
  • mickeyterm -- a MUXer-aware minimal terminal emulator.

How to debug

  1. log in via ssh
  2. killall python
  3. edit /etc/frameworkd.conf and add to the frameworkd section:
    1. log_level = DEBUG
    2. log_to = file
    3. log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
  4. Read our documented frameworkd.conf configuration file to learn about the other options.
  5. relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
  6. log in via ssh (yes, again)
  7. export DISPLAY=:0.0
  8. run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

The role of Python

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.

Team & Roadmap

Team

Roadmap

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.

Download and see also