Hi, In principle on MeeGo Qt Mobility Location API uses GeoclueMaster for positioning -> As a consequence it supports whatever Geoclue Master works with and adding your own provider should be possible.
If you are going to use the Qt Location API a lot, I would recommend to use Qt Location for MeeGo from the QtMobility repository (http://qt.gitorious.org/qt-mobility/qt-mobility). Unfortunately there are no released binaries of it available yet but you would need to compile yourself. It is however significantly different from the temporary patch you are referring to, although the 'provider strategy' should be the same (i.e. geoclue master for positioning, gypsy for satellites). Note that for satellite metadata (which satellites are in view/use and their signal strengths etc.) QtLocation uses gypsy. Juha From: [email protected] [mailto:[email protected]] On Behalf Of ext HorryChiang Sent: Friday, January 07, 2011 5:45 PM To: [email protected] Subject: [MeeGo-dev] Does QT-Mobility Location API of MeeGo 1.1 released only support Gypsy provider? Dear master, Since we have our special GPS provider for Geoclue, we want to check if it can be controlled by Geoclue of Qt Mobility locaton API. I find information about default provider 'gypsy' used by Geoclue, it looks like Geoclue only supports Gypsy provider for current MeeGo Location API implementation. Please find line 351 from "07_add_location_api_meego_implementation_using_geoclue.patch" of "qt-mobility-1.0.2-7.1.src.rpm" (MeeGo 1.1 released) My question is: Does QT-Mobility Location API of MeeGo 1.1 released only support Gypsy provider? How should we do if we want to replace Gypsy with our provider? Many thanks for your reply.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
