OpenmokoFramework

From Openmoko

Revision as of 21:23, 28 April 2008 by Lally (Talk | contribs)

Jump to: navigation, search

Note: This is the (ongoing) description of the new framework architecture. See OpenmokoOldFramework for the framework architecture of 2007.1 and 2007.2

Contents

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

  • Chose Dbus 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.
  • Be not afraid of reinventing the wheel for a wheel-barrow if all the existing wheels are made for sports cars.

Mandatory Readings

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.

Overview

... picture ...

Components

... discussion of subsystem purposes ...

Low Level

Device

...

GSM

This involves three components:

  • GSM 07.10 (Multiplexing Daemon)
  • GSM 07.07 (Telephony)
  • GSM 07.05 (SMS)

Bluetooth

We base on the official Linux Bluetooth subsystem here, which is BlueZ.

Network

Options: Networkmanager or Intel Connection Manager

GPS

We base on Gypsy here.

High Level

PIM

  • intelligent storage database

Events

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

Usage

  • coordinating application I/O requirements (think reference counting for I/O requirements)
  • might use fd.o policy API

Preferences

  • settings database

Context

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

Tasks

What's there

  • bluez
  • gypsy
  • geoclue
  • py-odeviced
  • pygsmd
  • gsmd0710muxd
  • networkmanager or intel connection manager

What's missing

  • py-ophoned
  • pimd (GSoC 2008 project)
  • eventd
  • usaged
  • preferencesd
  • contextd

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 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 RPython would be much easier than Vala and much of the benefits of python remain.

Team & Roadmap

... talk about the team and the roadmap ...

Personal tools

Note: This is the (ongoing) description of the new framework architecture. See OpenmokoOldFramework for the framework architecture of 2007.1 and 2007.2

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

  • Chose Dbus 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.
  • Be not afraid of reinventing the wheel for a wheel-barrow if all the existing wheels are made for sports cars.

Mandatory Readings

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.

Overview

... picture ...

Components

... discussion of subsystem purposes ...

Low Level

Device

...

GSM

This involves three components:

  • GSM 07.10 (Multiplexing Daemon)
  • GSM 07.07 (Telephony)
  • GSM 07.05 (SMS)

Bluetooth

We base on the official Linux Bluetooth subsystem here, which is BlueZ.

Network

Options: Networkmanager or Intel Connection Manager

GPS

We base on Gypsy here.

High Level

PIM

  • intelligent storage database

Events

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

Usage

  • coordinating application I/O requirements (think reference counting for I/O requirements)
  • might use fd.o policy API

Preferences

  • settings database

Context

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

Tasks

What's there

  • bluez
  • gypsy
  • geoclue
  • py-odeviced
  • pygsmd
  • gsmd0710muxd
  • networkmanager or intel connection manager

What's missing

  • py-ophoned
  • pimd (GSoC 2008 project)
  • eventd
  • usaged
  • preferencesd
  • contextd

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 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 RPython would be much easier than Vala and much of the benefits of python remain.

Team & Roadmap

... talk about the team and the roadmap ...