fpw / avitab

X-Plane plugin that displays a tablet to aid VR usage
GNU Affero General Public License v3.0
299 stars 58 forks source link

Configurable online slippy maps 3 #167

Closed cyberang3l closed 10 months ago

cyberang3l commented 10 months ago

Enable the remaining features for the online maps

After this diff the support for used-defined online maps is mostly "feature-complete". Some things that are left to be done, but probably not so urgent:

fpw commented 10 months ago

Going forward, I suggest OnlineSlippySource as new class name since that reflects the name of its config class.

cyberang3l commented 10 months ago

Rename the OpenTopoSource filenames and class to something more generic like SlippyMapSource or OnlineMapSource? <- This is done in #170

If a map from the custom online maps is enabled, store it's name in a variable and add it to the description beside the "Online" button.... <- this is done in #172

Now about this: Get rid of the Stamen and OpenTopo buttons and move these maps under the "Online" button. Then move the "Online" button to the top of the list., I was wondering how to implement this correctly.

Ideally, we want to have OpenTopoMaps as a fixed, hard-coded configuration so that in case a user messes up their mapconfig.json, can still, at least access OpenTopoMaps.

So I was rethinking about this... and maybe we should leave the OpenTopoMaps button in place, and only move Stamen maps in the mapconfig.json and remove the "Stamen" button? What do you think @fpw ?

By the way, the Stamen maps don't even work for me. So if we want to make this change, is it something you can do as I cannot even test it myself? If you agree on this, then I think I'm already done with the implementation of this feature.

fpw commented 10 months ago

maybe we should leave the OpenTopoMaps button in place, and only move Stamen maps in the mapconfig.json and remove the "Stamen" button? What do you think @fpw ?

I think having all online sources in the JSON is fine. If OpenTopo gets messed up, it must be because the user changed the JSON file - which means they know how to edit or potentially restore it. This will leave more place in the menu for the various Navigraph map buttons.

Stamen doesn't work.

It seems they no longer host a free tile server, so it can be removed completely. On the other hand, I think OpenStreetMap's policy now allows tools like AviTab, so that can be enabled by default instead.

cyberang3l commented 10 months ago

OK, then I'll proceed like we initially planned.

Remove both OpenTopo and Stamen buttons. Move the "Online" button at the top of the menu, and enable OpenTopoMap by default. I'll remove completely the Stamen topo source.

You'll get the last PR soon then :)