User:Panta/translate

From Openmoko

< User:Panta
Revision as of 22:45, 13 May 2008 by Panta (Talk | contribs)

Jump to: navigation, search


Note: Questa è la (attuale) descrizione della nuova architettura framework in sviluppo. Si veda OpenmokoOldFramework per informazioni sull'architettura framework 2007.1 e 2007.2, nonché NeoSoftwareStack per lo stato attuale (che non ha ancora niente da fare con questo framework)

Contents

Risposte alle domande #1 e #2

  • Domanda: Tutto questo è già parte delle immagini attuali?
  • Risposta: No.
  • Domanda: Quando lo diverrà?
  • Risposta: Ci aspettiamo che una zhone-image (che include tutte le novità del framework) diventi una versione alpha intorno a Giugno '08, beta in Agosto '08 con un rilascio stabile al pubblico in Settembre '08.

Scopi

  • Dare alle persone l'infrastruttura sulla quale creare prodotti software solidi e divertenti basati sulla piattaforma OpenMoko
  • Dare supporto a UI competenti collaborando nello sviluppo dei servizi
  • Incoraggiare gli utenti framework (ad esempio, gli sviluppatori di programmi) a contribuire al framework stesso

Requisiti

  • Createlo semplice
  • Concentratevi sui core services
  • Siate agnostici nel linguaggio di programmazione
  • Siate agnostici nella scelta del toolkit UI
  • Cercate per quanto possibile di riutilizzare tecnologie esistenti, ma non al costo di ottenere una brutta API

Come soddisfarli tecnicamente

  • Scegliete Dbus come esempio di collaborazione. Sotto dbus, possiamo lavorare insieme. Sopra dbus, possiamo distinguerci.
  • Esponi le caratteristiche attraverso dbus API implementate in servizi agnostici nella UI e nel linguaggio (demoni).
  • Ottimizza per i dispositivi OpenMoko, ma supporta scopi ed architetture multiple attracerso interfacce plugin e buoni meccanismi di astrazione hardware.
  • Non aver paura di reinventare la ruota per una carriola se tutte le ruote esistenti sono costruite per macchine sportive.

Letture Obbligatorie

Cosa è ESCLUSO

Questa iniziativa non copre servizi di basso livello come

  • Bootloader, Kernel, o System Init.

Questa iniziativa non copre servizi di alto livello come

  • X-Window-System, Window Manager, UI Toolkits,
  • Application Launchers, Programmi, o UI Divertenti.

Uno sguardo all'Architettura

frontside

Componenti Software

Noi facciamo difefrenza tra servizi di alto e basso livello -- per comunicare orizzontalmente e verticalmente verrà utilizzato dbus.

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,
  • accellerometers, 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. On top of that, there are two components:

  1. gstreamer
  2. pulseaudio

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.

Pulseaudio is to be used for event sounds, where low-latency is necessary, e.g. touch click sounds and UI event acknowledge sounds. Pulseaudio is our general all-purpose mixer. Gstreamer will use the pulseaudio sink to feed audio through.

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 -- 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 rely on the following software:

Network

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

  • Network Manager or Intel Connection Manager (undecided yet)
  • ppp

High Level

Usage

The Usage subsystem is coordinating application I/O requirements preventing. 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

  • signaling 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 at [1]

Context

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

TBD Reference Geoclue

Telephony

  • Voice
  • Data

Preferences

  • settings database

Network

  • high level networking queries

Implementation

Completion Status

Low Level

  • device control: 50%
  • audio: 80%
  • GSM: 80%
  • Bluetooth: 80%
  • GPS: 80%
  • Network: 50%

High Level

  • Usage: 0%
  • Event: 0%
  • Preferences: 0%
  • Context: 0%
  • Telephony: 50%
  • Networking: 0%
  • PIM: 0%

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 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

Milestone 1:

Milestone 2:

Milestone 3:

Personal tools


Note: Questa è la (attuale) descrizione della nuova architettura framework in sviluppo. Si veda OpenmokoOldFramework per informazioni sull'architettura framework 2007.1 e 2007.2, nonché NeoSoftwareStack per lo stato attuale (che non ha ancora niente da fare con questo framework)

Risposte alle domande #1 e #2

  • Domanda: Tutto questo è già parte delle immagini attuali?
  • Risposta: No.
  • Domanda: Quando lo diverrà?
  • Risposta: Ci aspettiamo che una zhone-image (che include tutte le novità del framework) diventi una versione alpha intorno a Giugno '08, beta in Agosto '08 con un rilascio stabile al pubblico in Settembre '08.

Scopi

  • Dare alle persone l'infrastruttura sulla quale creare prodotti software solidi e divertenti basati sulla piattaforma OpenMoko
  • Dare supporto a UI competenti collaborando nello sviluppo dei servizi
  • Incoraggiare gli utenti framework (ad esempio, gli sviluppatori di programmi) a contribuire al framework stesso

Requisiti

  • Createlo semplice
  • Concentratevi sui core services
  • Siate agnostici nel linguaggio di programmazione
  • Siate agnostici nella scelta del toolkit UI
  • Cercate per quanto possibile di riutilizzare tecnologie esistenti, ma non al costo di ottenere una brutta API

Come soddisfarli tecnicamente

  • Scegliete Dbus come esempio di collaborazione. Sotto dbus, possiamo lavorare insieme. Sopra dbus, possiamo distinguerci.
  • Esponi le caratteristiche attraverso dbus API implementate in servizi agnostici nella UI e nel linguaggio (demoni).
  • Ottimizza per i dispositivi OpenMoko, ma supporta scopi ed architetture multiple attracerso interfacce plugin e buoni meccanismi di astrazione hardware.
  • Non aver paura di reinventare la ruota per una carriola se tutte le ruote esistenti sono costruite per macchine sportive.

Letture Obbligatorie

Cosa è ESCLUSO

Questa iniziativa non copre servizi di basso livello come

  • Bootloader, Kernel, o System Init.

Questa iniziativa non copre servizi di alto livello come

  • X-Window-System, Window Manager, UI Toolkits,
  • Application Launchers, Programmi, o UI Divertenti.

Uno sguardo all'Architettura

frontside

Componenti Software

Noi facciamo difefrenza tra servizi di alto e basso livello -- per comunicare orizzontalmente e verticalmente verrà utilizzato dbus.

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,
  • accellerometers, 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. On top of that, there are two components:

  1. gstreamer
  2. pulseaudio

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.

Pulseaudio is to be used for event sounds, where low-latency is necessary, e.g. touch click sounds and UI event acknowledge sounds. Pulseaudio is our general all-purpose mixer. Gstreamer will use the pulseaudio sink to feed audio through.

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 -- 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 rely on the following software:

Network

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

  • Network Manager or Intel Connection Manager (undecided yet)
  • ppp

High Level

Usage

The Usage subsystem is coordinating application I/O requirements preventing. 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

  • signaling 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 at [1]

Context

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

TBD Reference Geoclue

Telephony

  • Voice
  • Data

Preferences

  • settings database

Network

  • high level networking queries

Implementation

Completion Status

Low Level

  • device control: 50%
  • audio: 80%
  • GSM: 80%
  • Bluetooth: 80%
  • GPS: 80%
  • Network: 50%

High Level

  • Usage: 0%
  • Event: 0%
  • Preferences: 0%
  • Context: 0%
  • Telephony: 50%
  • Networking: 0%
  • PIM: 0%

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 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

Milestone 1:

Milestone 2:

Milestone 3: