Ask / Submit
100

Support for QtPositioning & QtLocation APIs [released]

asked 2014-01-07 10:33:34 +0300

Ecyrd gravatar image

updated 2014-01-07 10:35:56 +0300

AL13N gravatar image

I am fairly sure that someone already is working on this ('cos a mobile phone these days without any sort of location/positioning is kinda dumb), but I'll just add this here as a tracker:

It would be very cool and useful to have both QtPositioning and QtLocation APIs available as "approved" APIs to link against, in order to enable a number of location-based apps.

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by r0kk3rz
close date 2015-05-06 17:53:37.884557

Comments

If I understand correctly, the problem is that those API are not yet stable in Qt version used by Sailfish. This could cause compatibility breaks in future updates, so they are simply not allowed. This will be resolved by upgrading Qt in sailfish to newer version with stable API (hopefully soon).

koudi ( 2014-01-07 12:44:49 +0300 )edit

Yes, this is my understanding as well. I wanted to add this topic here so we can all put nice little social pressure on Jolla to accept that they are stable ;-)

After all, both have been around since QtMobility...

Ecyrd ( 2014-01-07 12:53:35 +0300 )edit
1

is there any other possibility to obtain the position without qt5-qtdeclarative-import-positioning?

mgbler ( 2014-01-07 13:53:34 +0300 )edit

2 Answers

Sort by » oldest newest most voted
20

answered 2014-01-07 15:17:58 +0300

thp gravatar image

updated 2014-01-07 15:24:17 +0300

We're working hard on adding support for QtPositioning. QtPositioning became stable in Qt 5.2, the Qt we ship is something between Qt 5.1 and Qt 5.2. QtLocation is not yet stable, so we can't support that at the moment until upstream Qt makes it stable. For getting the position, QtPositioning is enough (QtLocation is used for such things as maps, place search, routing and geocoding).

To get QtPositioning supported as an official API, we need to upgrade it to Qt 5.2 (as its API is only stable from then on, our current build differs a bit from Qt 5.2, as it's been taken from an earlier development version between Qt 5.1 and Qt 5.2), which we're working on at the moment, but it can take some time. If you want to see the difference of what the package we're currently shipping has and what the (API-stable) Qt 5.2 version of Qt Positioning looks like, you can do this yourself in the following way:

git clone --recursive git://github.com/mer-packages/qtlocation.git
cd qtlocation
cd upstream
git checkout v5.2.0
cd ..
diff -ru qtlocation upstream > changes_sailfish-to-qt52.patch

(a copy of that as of today is available temporarily at http://o.thp.io/tmp/2014-01-07_changes_sailfish-to-qt52.patch for your convenience)

You see, while most of these changes are internal, some QML APIs have changed, so we cannot just allow linking and using the current version of QtPositioning, as there might be conflicts.

As a temporary, not recommended workaround, you can use GeoClue via the D-Bus API directly (but check if there's a GeoClue service manager running on the current session bus, and use QtPositioning once 5.2 is out): http://www.freedesktop.org/software/geoclue/docs/

edit flag offensive delete publish link more

Comments

Great, thanks for this clarification!

Ecyrd ( 2014-01-07 17:19:56 +0300 )edit
1

Actually, the API docs linked are for GeoCode2 - Jolla uses an older version with a quite different API, docs can be found at https://developer.gnome.org/geoclue/0.12/.

patrikf ( 2014-01-27 10:29:54 +0300 )edit

I'd be really interested on progress on this, as my project would need at least QtPositioning on C++ side soon.

ToniR ( 2014-03-18 10:34:55 +0300 )edit

Progress update: Will come when Qt 5.2 is ready, which will probably happen with one of the upcoming updates. So we're getting closer.

thp ( 2014-04-17 17:10:07 +0300 )edit
17

answered 2015-03-21 12:53:33 +0300

thp gravatar image

updated 2015-05-06 09:27:00 +0300

Kontio gravatar image

Qt Location won't be supported at first (because it's not yet in the list of supported modules in Qt 5), but Qt Positioning (which is supported upstream since Qt 5.2) is queued for allowing in Harbour:

https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/pull/54

UPDATE - 06. May 2015
As announced in the mailing list, we start today in Harbour to accept applications which depend on Qt Positioning.

edit flag offensive delete publish link more

Comments

Wow, thanks a lot! :)

MartinK ( 2015-03-21 14:10:15 +0300 )edit
1

thanks a lot! what is about sensors? to also access the compass, which should be important for navigation related apps, too

balta ( 2015-03-21 15:45:38 +0300 )edit
1

Thanks! Do you know if Qt has some timeline for an official and stable release of QtLocation?

otsaloma ( 2015-03-21 16:14:58 +0300 )edit

@balta I think the QtSensors module can already be used by Jolla Store applications.

@Osmo Salomaa Looks like it will be a tech preview in Qt 5.5.

MartinK ( 2015-03-21 17:06:08 +0300 )edit
1

@MartinK I don't know if it is just missing the qml plugin or missing comletely, but the validator ist giving me: ERROR [qt5-qtdeclarative-import-sensors] Dependency not allowed

balta ( 2015-03-23 11:28:56 +0300 )edit

Question tools

Follow
14 followers

Stats

Asked: 2014-01-07 10:33:34 +0300

Seen: 2,896 times

Last updated: May 06 '15