View Single Post
otsaloma's Avatar
Posts: 141 | Thanked: 1,530 times | Joined on May 2011 @ Finland
#247
Originally Posted by rinigus View Post
I must say that situation with QtLocation on SFOS is frustrating. Its probably a naive question but I am going to ask it anyway: now, when we have Qt5.6, is it possible to compile missing QtLocation 5.6 and add it ourself via OpenRepos or other distribution mechanism? @otsaloma, you have been following for a while, do you know whether it is possible?
I don't actually know if it's possible, but looking the commit activity, there's a lot of fixes related to e.g. geoclue positioning, and just using upstream 5.6 might not work well on all devices and trying to port those patches to 5.6 might be difficult. Additionally, there are API changes between 5.2 and 5.6, which means upgrading would break many apps written for 5.2. The API changes are small and it's easy to adapt to them, but it might be difficult for app authors to support both versions.

Also note, that this problem of using using a custom tile source, e.g. OSM Scout Server, is only partially served by the OSM plugin in QtLocation 5.6. It allows you to set the host, e.g. "http://tile.openstreetmap.org/" in "http://tile.openstreetmap.org/{z}/{x}/{y}.png", but the requested URL will always end in "{z}/{x}/{y}.png". What we'd really need is a plugin that supports a template URL string, so that you can have X, Y and Z as URL parameters instead of path components or additional parameters like day/night or API keys etc. And also, a plugin parameter for tile size so that the requested tiles can be shown correctly. A custom QtLocation plugin would be easy to distribute separately, e.g. at OpenRepos, but probably difficult to use in Harbour apps.
 

The Following 5 Users Say Thank You to otsaloma For This Useful Post: