diversity team meeting (1st July)

Guillaume Chereau charlie at openmoko.org
Tue Jul 1 13:43:35 CEST 2008


On Tue, 2008-07-01 at 18:11 +0800, Marek Lindner wrote:
> Hi,
> 
> today we discussed several things:
> 
> - Charlie took part in this meeting to represent the Framework team. We tried 
> to give him a general overview about what is going to happen.
> - He will start working on the "phone" API which will be a high level daemon 
> to integrate GSM and VoIP services. First he will focus to create an API and 
> to integrate GSM based on the framework API. Once Brandon is providing us 
> with some IAX stuff they can work together on it.
> - Brandon makes good progress and got more support from Digium. I hope we can 
> integrate his packages into our package builder this week.
> - OLV finished the connman / diversity daemon integration. In the coming days 
> he will focus on the AP database backend and tries to finish the map 
> packages.
> - Jeremy began looking into the splinter python migration and will keep some 
> code in C. Erin worked on the radar and on the "layer integration". Both 
> continue working on that.
> - Marek suggested to use the "app-launcher daemon" to improve memory usage and 
> startup time of python apps. Needs more discussions.
> 
> Open issues:
> - Do we offer to set a "user / screen name" for VoIP users (on incoming call 
> one would see the screen name instead of the number) ?
> - Charlie things that an automatic registration & account creation is a 
> restriction.
> - Add a config option to use your own IAX account ?
> - Do we offer to keep the number if the phone was lost or a new one was 
> bought ?
> 
> Needed:
> - Diversity needs a design to start thinking / working on the dialer / 
> contacts / desktop !
> 
> 
> Marek

OK, so what I am planning to do then is a new freesmartphone service,
that would implement a DBus interface with the following method :

* Initiate(string) -> dbus-object

the dbus-object returned by the method will itself implements a DBus
interface with the following methods :

* GetStatus()
* Release()
* ...

as well as a signal :
* CallStatus, to signal the change in status of a given call.

So it is very close to the GSM.Call interface of the framework, except
that it is a little bit higher level (one object per connection), and
the Initiate method will try to figure out which service to use (eheh,
for the moment the choice is easy, we only have GSM calls :) )

By the way : Mickey, why not using this object oriented approach with
one object per call in the GSM service instead of having to pass the id
of the call for each methods ? If this is possible then we can have an
elegant structure where the GSM Initiate method directly returns an
object implementing the "VoiceCall" interface.
I am just thinking aloud here, because I am not familiar enough with
ophoned to guess how difficult it would be to implement.

Cheer,
-Charlie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxtogo.org/pipermail/smartphones-standards/attachments/20080701/0069b0bc/attachment.pgp>


More information about the smartphones-standards mailing list