Thanks for all the info so far.
Is there any more information about the conflicting parts in the T&C? Is
it a about using Google inside lgpl code? Or something about the
techniques used? Whats the difference to e.g. the "here" maps who also
need an registered api key, basically in the same way
Hi,
>Has anyone tried to write a provider
>plugin for google maps or has anyone had any success in using the native
>Android MapView/MapFragment as well as iOS MapKit alongside QML in their
>App?
I know of at least two patches pushed to Gerrit for working Google
implementation. Both had to be re
On 13 juil. 2016, at 11:22, Adrian Jäkel wrote:
> Hi,
>
> since Monday, July 11, 2016, the direct tile access to MapQuest legacy maps
> has been stopped. See [1].
>
> Is it correct that there are now no out of the box usable map provider
> plugins?
>
> MapQuest now offers a "free" plan for
uartz should support it tho).
Regards,
Marco Piccolino
http://slackin.qtmob.org
>
> -- Messaggio inoltrato --
> From: "Adrian Jäkel"
> To: interest@qt-project.org
> Cc:
> Date: Wed, 13 Jul 2016 11:22:49 +0200
> Subject: [Interest] QML Map Provider
Hi,
since Monday, July 11, 2016, the direct tile access to MapQuest legacy
maps has been stopped. See [1].
Is it correct that there are now no out of the box usable map provider
plugins?
MapQuest now offers a "free" plan for which you need to register. Has
anyone tried to adapt the osm plu
