-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
On Behalf Of ext Arjan van de Ven
On 10/28/2010 6:10 PM, Sivan Greenberg wrote:
Re reading about MeeGo's architecture, is Geoclue the engine or the
backend for Qt's Mobility location and
On Sunday, 31 de October de 2010 20:51:21 alex.blas...@nokia.com wrote:
Not every Qt API consists of plug-ins as their backend. In general, that's
only done if it is likely that the same device image should/could be
extended/changed during the same device's lifetime (e.g. add more codecs,
use
Re reading about MeeGo's architecture, is Geoclue the engine or the
backend for Qt's Mobility location and positioning APIs?
If not, what is the relationship ?
Thanks
-Sivan
(Since these subjects appear to be part of the core stack, I felt
comfortable to discuss this here and not on
-dev
Subject: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo
Re reading about MeeGo's architecture, is Geoclue the engine or the
backend for Qt's Mobility location and positioning APIs?
If not, what is the relationship ?
Thanks
-Sivan
(Since these subjects appear to be part of the core stack, I
On 10/28/2010 6:10 PM, Sivan Greenberg wrote:
Re reading about MeeGo's architecture, is Geoclue the engine or the
backend for Qt's Mobility location and positioning APIs?
If not, what is the relationship ?
geoclue is the reference back end. Geoclue however is not a manadatory
component.
