BTW, how is the "official" Mapbox GL plugin API compared to "our" custom MapboxGL element API ? Is it 1:1 match feature wise ?
I would kinda fear the API is dumbed down to account for all the other plugins but (the QtLocation API, especially in the QtQuick 1.0 times was not very good). Or is it possibly the other way around (eq. we are missing some features they have ?).
That's definitely the only sensible way. It looks like they are working on QtLocation 5.9: https://git.merproject.org/mer-core/...n/tree/mer-5.9 https://git.merproject.org/mer-core/...n/tree/mer1911 But who knows in which for it will actually be available, which plugins will work and if it will finally be whitelisted for Jolla Store apps.
BTW, thinking about it, would it be possible that the MapBoxGL plugin could be built with your updated GCC toolchain and still work with QtLocation 5.9 once available ? That way there would still be a custom dependency that needs to be installed, but the custom element would not have to be maintained anymore & it would simplify desktop porting compatibility.
Definitely thanks for the heads-up! While I think I'll just start with our current known-working solution, it's definitely good to explore other options (technically, the modRana codebase could be now able to support both if really really needed ). I don't know I understand this ? You mean in modRana, the custom MapBoxGL plugin on Poor/Whogo/Pure maps code ?