Page MenuHomePhabricator

Move from non-developed, deprecated Mapbox.js to Leaflet
Open, LowPublic

Description

Right now Kartographer embeds Mapbox.js, which is Mapbox's version of Leaflet. There's nothing which can't be done with base Leaflet.

We should switch to base Leaflet, which will help maintenance by having us use a more standard library that more people are familiar with. It would also make it easier to keep up to date and get bugfixes from Leaflet.

This has been discussed a fair amount informally and is considered desirable.

Details

Event Timeline

Do we know why originally the choice for mapbox.js was made?

I think the initial idea was to use client-side rendering, and mapbox offers a better path for that.

Pnorman added a project: Technical-Debt.

This is still a good idea and wouldn't result in any changes visible to the user.

Change 451788 had a related patch set uploaded (by TheDJ; owner: TheDJ):
[mediawiki/extensions/Kartographer@master] [WIP] Move from Mapbox.js to Leaflet

https://gerrit.wikimedia.org/r/451788

Mapbox.js is now considered legacy btw:
Mapbox.js is no longer in active development. To learn more about our newer mapping tools see Mapbox GL JS.

Aklapper renamed this task from Move from Mapbox.js to Leaflet to Move from non-developed, deprecated Mapbox.js to Leaflet.Feb 26 2020, 5:30 PM

I think I can actually wrap this up fairly easily soon. Finally had the time to develop a better understanding on the differences between mapbox.js and leaflet.js and know where and how to tackle them I think. want to see if i can also convert it to packageFiles RL structure.

Seems we don't have a good layer icon in oo-ui, which we sort of need for the conversion...

Volker_E subscribed.
This comment was removed by Volker_E.