User:Panta/translate

From Openmoko

< User:Panta(Difference between revisions)
Jump to: navigation, search
m (removed article from the "root" category.)
(homepage italiana al 17/8/08)
Line 1: Line 1:
{{Languages|OpenmokoFramework}}
+
{{Languages|Main Page}}
 +
__NOTOC__
 +
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo Freerunners]]
  
''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)''
+
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div>
  
=Risposte alle domande #1 e #2=
+
Openmoko™ is a project dedicated to delivering mobile phones with an open source software stack. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.
* ''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=
+
The Openmoko stack, which includes a full X server, allows users and developers to transform mobile hardware platforms into unique products. Our license gives developers and users freedom to cosmetically customize their device or radically remix it; change the wallpaper or rebuild the entire house! It grants them the freedom, for example, to transform a phone into a medical device or point of sale device or the freedom to simply install their own favourite software. Beyond freeing the software on our devices we have also released our CAD files under Creative Commons. And at Linux world 2008, we announced the release of the schematics for our products.
* '''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=
+
<div style="clear:both">&nbsp;</div>
* 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=
+
<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white">
* Scegliete [[Dbus]] come esempio di collaborazione. Sotto dbus, possiamo lavorare insieme. Sopra  dbus, possiamo distinguerci.
+
<tr style="background:#ff6600; text-align:center; font-weight:bold">
* Esponi le caratteristiche attraverso dbus API implementate in servizi agnostici nella UI e nel linguaggio (demoni).
+
<td width="50%">News and events</td>
* Ottimizza per i dispositivi OpenMoko, ma supporta scopi ed architetture multiple attracerso interfacce plugin e buoni meccanismi di astrazione hardware.
+
<td width="50%">New to Openmoko?</td>
* Non aver paura di reinventare la ruota per una carriola se tutte le ruote esistenti sono costruite per macchine sportive.
+
</tr>
 +
<tr valign="top" style="background:#333333">
 +
<td>
 +
* 15/8: Debian on the FreeRunner [http://n2.nabble.com/Debian-on-the-FreeRunner----now-official-td726410.html announced], [http://wiki.debian.org/DebianOnFreeRunner instructions].
 +
* 8/8: Openmoko team [http://lists.openmoko.org/pipermail/community/2008-August/025602.html releases] distribution formerly called ASU as [[Om 2008.8]] .
 +
* 4-5/8: Openmoko is at Linuxworld, San Francisco
 +
* 30/7: The FSO distribution releases [http://downloads.openmoko.org/framework/milestone2/ milestone 2]
 +
* 25/7: Community helps, [[GPS Problems]] fixed
 +
* 20/7: [[Debian]] added to the [[Distributions]] page
 +
* 27/6: GTA 02 shipping in the  [http://lists.openmoko.org/pipermail/community/2008-June/019943.html material world]
 +
</td>
 +
<td>
 +
===<font color=white>About Openmoko</font>===
 +
* [[Introduction]]
 +
* [[Why Openmoko]]
 +
* [[Neo FreeRunner|Neo FreeRunner phone]]
 +
* [[Supported Hardware]]
 +
* [[FAQ]]
  
=Letture Obbligatorie=
+
===<font color=white>Getting Openmoko</font>===
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ I Framework esistono per l'integrità concettuale]
+
* [[Getting Openmoko]]
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Dieci modi per rendere più umano il software open source]
+
* [http://www.openmoko.com Openmoko Inc.]
* [http://www.freesmartphone.org Il Wiki FreeSmartPhone.org]
+
  
=Cosa è ESCLUSO=
+
</td>
Questa iniziativa non copre servizi di basso livello come
+
</tr>
* Bootloader, Kernel, o System Init.
+
<tr style="background:#ff6600; text-align:center; font-weight:bold">
 +
<td width="50%">for Users</td>
 +
<td width="50%">for Developers</td>
 +
</tr>
 +
<tr valign="top" style="background:#333333">
 +
<td>
 +
===<font color=white>Getting started</font>===
 +
* [[Getting Started with your Neo FreeRunner | Neo FreeRunner getting started guide]]
 +
* [[Getting Started FAQ]]
  
Questa iniziativa non copre servizi di alto livello come
+
===<font color=white>Software</font>===
* X-Window-System, Window Manager, UI Toolkits,
+
* [[Distributions|Openmoko software distributions]]
* Application Launchers, Programmi, o UI Divertenti.
+
* [[Om 2007.2|2007.2 distribution]]
 +
* [[Om 2008.8|2008.8 distribution]]
 +
* [[OpenmokoFramework|FSO distribution]]
 +
* [[Qtopia_on_FreeRunner|Qtopia distribution]]
  
=Uno sguardo all'Architettura=
+
===<font color=white>Openmoko community</font>===
[[Image:OpenmokoFramework08.png |823px|left|frontside]]
+
* [[Discussion_Forums| Discussion Forums]]
 +
* [[CommunityRepository|Community repository]]
 +
* [[Development resources | Development resources]]
 +
</td>
 +
<td>
 +
===<font color=white>Applications development</font>===
 +
* [[Openmoko developer guide]]
 +
* [[Toolchain|The toolchain]]
 +
<!-- * <font color=white>VMware</font> -->
 +
* [[Python|Introduction to Python]]
 +
* [http://projects.openmoko.org/ Projects hosted in our GForge]
  
=Componenti Software=
+
===<font color=white>Integration and distributions</font>===
 +
* [[OpenEmbedded|The OpenEmbedded distribution building framework]]
 +
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]
 +
* [[Opkg|Opkg the package manager]]
  
Noi facciamo differenza tra servizi di alto e basso livello -- per comunicare orizzontalmente e verticalmente verrà utilizzato dbus.
+
===<font color=white>Emulation</font>===
 +
* [[Openmoko under QEMU]]
 +
</td>
 +
</tr>
 +
</table>
  
===Servizi di Basso Livello===
+
[[Category:Information| ]]
 
+
====Controllo del Dispositivo====
+
Il servizio di controllo del dispositivo di basso livello gestisce il controllo delle periferiche, il che consiste nel verificare l'accensione di sottosistemi singoli come
+
* GSM, WiFi, Bluetooth, GPS, coì come anche
+
* Accensione e luminosità dello schermo,
+
* accendere e spegnere LED, etc.
+
Inoltre, ha a che fare con
+
* caricare, sospendere,/riesumare,
+
* accelerometri, e pulsanti.
+
Per finire, invia notifiche sulle attività dell'utente in modo che i servizi in ascolto possano
+
* modificare lo stato del powersaving, o
+
* bloccare il dispositivo.
+
Per far ciò, abbiamo implementato il software seguente:
+
* [http://www.freesmartphone.org/mediawiki/index.php/Implementations/OpenDeviceDaemon odeviced]
+
 
+
====Audio====
+
The low level audio service relies on a working alsa device driver. On top of that, there are two components:
+
# [http://gstreamer.freedesktop.org/ gstreamer]
+
# [http://pulseaudio.org 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
+
* [http://www.freesmartphone.org/mediawiki/index.php/Implementations/gsm0710muxd gsm0710muxd]
+
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:
+
* [http://www.bluez.org BlueZ].
+
 
+
====GPS====
+
The low level GPS services assume a GPS device that talks NMEA over a device node. We rely on the following software:
+
* [http://gypsy.freedesktop.org Gypsy]
+
 
+
====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 [http://www.neo1973-germany.de/wiki/pyPimd|PyPimd]
+
 
+
====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==
+
 
+
* [[User:Mickey|Michael 'Mickey' Lauer]]
+
* Guillaume Chereau
+
* [[User:Shoragan|Jan 'Shoragan' Luebbe]]
+
* Holger 'Zecke' Freyther
+
 
+
==Roadmap==
+
 
+
Milestone 1:
+
 
+
Milestone 2:
+
 
+
Milestone 3:
+
 
+
 
+
[[Category:Openmoko ]]
+

Revision as of 22:40, 18 August 2008


Neo Freerunners
Openmoko™ - Open. Mobile. Free.

Openmoko™ is a project dedicated to delivering mobile phones with an open source software stack. Openmoko is currently selling the Neo FreeRunner phone to advanced users and will start selling it to the general public as soon as the software is more developed.

The Openmoko stack, which includes a full X server, allows users and developers to transform mobile hardware platforms into unique products. Our license gives developers and users freedom to cosmetically customize their device or radically remix it; change the wallpaper or rebuild the entire house! It grants them the freedom, for example, to transform a phone into a medical device or point of sale device or the freedom to simply install their own favourite software. Beyond freeing the software on our devices we have also released our CAD files under Creative Commons. And at Linux world 2008, we announced the release of the schematics for our products.

 
News and events New to Openmoko?

About Openmoko

Getting Openmoko

for Users for Developers

Getting started

Software

Openmoko community

Applications development

Integration and distributions

Emulation

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 differenza tra servizi di alto e basso livello -- per comunicare orizzontalmente e verticalmente verrà utilizzato dbus.

Servizi di Basso Livello

Controllo del Dispositivo

Il servizio di controllo del dispositivo di basso livello gestisce il controllo delle periferiche, il che consiste nel verificare l'accensione di sottosistemi singoli come

  • GSM, WiFi, Bluetooth, GPS, coì come anche
  • Accensione e luminosità dello schermo,
  • accendere e spegnere LED, etc.

Inoltre, ha a che fare con

  • caricare, sospendere,/riesumare,
  • accelerometri, e pulsanti.

Per finire, invia notifiche sulle attività dell'utente in modo che i servizi in ascolto possano

  • modificare lo stato del powersaving, o
  • bloccare il dispositivo.

Per far ciò, abbiamo implementato il software seguente:

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: