Re: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo
-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 positioning APIs? If not, what is the relationship ? geoclue is the reference back end. Geoclue however is not a manadatory component. It's very likely that some commercial implementations of MeeGo will have their own custom back end, especially to tie into location services (maps etc) that service providers provide for a fee. Actually the devil is in the detail. From a Qt perspective Location covers four things: 1.) Positioning (get me the current coordinate 2.) Maps 3.) Navigation 4.) Landmarks/POIs Point 2-4 are based on plug-ins and can easily swapped out. With regards to positioning the Qt location actually integrates GeoClue into its own code base (and links against it). Swapping GoeClue out for positioning would therefore require a new backend inside the QtLocation library. Such positioning adaptations have to happen below/inside GeoClue (from a stack perspective). 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 a different maps provider etc). Otherwise a plug-in solution is too expensive for multiple reasons. The same applies to things like connman, ofono or other types of platform API's. Most Qt libraries with ties to those platform API's do not have a plug-in mechanism for their backends. -- Alex ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo
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 a different maps provider etc). Otherwise a plug-in solution is too expensive for multiple reasons. The same applies to things like connman, ofono or other types of platform API's. Most Qt libraries with ties to those platform API's do not have a plug-in mechanism for their backends. It's perfectly ok that some device vendors recompile certain libraries for better performance or, like in this case, linking to different libraries. However, they'll need to make their changes available to the community (QtMobility is LGPL). Also note that if it is likely that the same device image should/could be extended/changed during the same device's lifetime is actually incorrect. The guiding principle is not about one device's image, but the MeeGo release image (which spans all devices). Recompilations by vendors are the exception, not the rule, and they usually will rebuild only a couple of packages. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo
Yes, There is a draft implementation: http://qt.gitorious.org/~juhvu/qt-mobility/meego-location-qt-mobility Juha -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ext Sivan Greenberg Sent: Friday, October 29, 2010 11:11 AM To: meego-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 felt comfortable to discuss this here and not on meego-sdk) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo
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. It's very likely that some commercial implementations of MeeGo will have their own custom back end, especially to tie into location services (maps etc) that service providers provide for a fee. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
