On Fri, Jun 18, 2010 at 2:09 AM,  <[email protected]> wrote:

Hi Alex

[...]

> At the end of the day your suggestion would be some sort of API that manages 
> key-value pairs plus some UI for it. Personally I have doubts about its 
> usefulness - especially in a middleware layer API and more importantly how 
> many apps would there be which would use such a feature. The effort vs gain 
> ratio for UI elements would be particularly bad especially
[...]

My supposed use cases (apologize if based on wrong assumptions, but I
cannot gather the needed and/or correct informations):

* someone has to write system dialogs, configuration apps etc., for
the upcoming qt handhelds meego interface
* the same may be for meego-harmattan (do not know if it will use
connman or icd)
* the same for the new (?) upcoming qt based gui for netbook meego interface
* I guess kde may drive connman in the future and not only
networkmanager (again I maybe wrong here)
* thirdy part mms apps may need to go lowlevel to create new apn
* the same for vpn/wifi sharing, etc. apps
* some distro (many openembedded based) uses connman and need
frontends, actually I see only a gnome interface git repository but
may prefer qt (at this point hoping that lorn code will be evolved and
maintained)
* some of those uses ofono, qt, qt-mobility (neophysis, an hobbiest
distro working on openmoko freerunner and partially on the n900, in my
spare time I collaborate with them, they already use qt-mobility
actually only to import vcards with versit but is planned to write
plugins for openmoko device management, for a custom contacts backend
etc. the next natural idea is to use connman for wifi/gprs, and voice
call qt api if they will arrive later ;)

In all cases we have to write/maintain middleware level code that may
be shared and better organized in the bearer module.

But you are right, these use cases are few, may be incorrect or better
solved at system customization level, so I'll not insist ;)

Thanks and Regards

    Niko
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to