You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it uses TypeScript, which is much more easy to integrate with Kotlin
Generally it looks like MapLibre is less popular (it's much newer, having been recently split from MapBox, after a license change), but it supports more modern features.
Implementing MapLibre bindings is made much more difficult because Dukat fails to generate anythingKotlin/dukat#477. By comparison, Dukat did generate most of the Leaflet bindings, which provided a good basis. However... those aren't perfect because Leaflet is not TypeScript native (unlike MapLibre), so the TypeScript the Leaflet bindings were generated from might not be accurate (but they seem to work okay). So it's a mixed bag. Anyway, defining new bindings is a lot of work, regardless of Dukat support.
There is some interest in creating Kotlin bindings for MapBox/MapLibre Kotlin/dukat#477. Additional it looks like there's some movement to migrate the MapLibre's Java code to Kotlin maplibre/maplibre-native#420 - so maybe MapLibre devs could help with the bindings? Or even include them themselves? I might make an issue.
I'm not likely to pick this up any time soon - Leaflet is good enough. But if there's a lot of support, or someone wants to collaborate, I could give it a go.
The text was updated successfully, but these errors were encountered:
I'm using the module in one of my apps, but it's very simple usage (just to show a location of the entity). Maven central stats show about 1K downloads a month, even though it's not included by default in any template or example app.
This is a very speculative issue,
https://maplibre.org/
I like the look of MapLibre for a couple of reasons:
Generally it looks like MapLibre is less popular (it's much newer, having been recently split from MapBox, after a license change), but it supports more modern features.
Implementing MapLibre bindings is made much more difficult because Dukat fails to generate anything Kotlin/dukat#477. By comparison, Dukat did generate most of the Leaflet bindings, which provided a good basis. However... those aren't perfect because Leaflet is not TypeScript native (unlike MapLibre), so the TypeScript the Leaflet bindings were generated from might not be accurate (but they seem to work okay). So it's a mixed bag. Anyway, defining new bindings is a lot of work, regardless of Dukat support.
There is some interest in creating Kotlin bindings for MapBox/MapLibre Kotlin/dukat#477. Additional it looks like there's some movement to migrate the MapLibre's Java code to Kotlin maplibre/maplibre-native#420 - so maybe MapLibre devs could help with the bindings? Or even include them themselves? I might make an issue.
I'm not likely to pick this up any time soon - Leaflet is good enough. But if there's a lot of support, or someone wants to collaborate, I could give it a go.
The text was updated successfully, but these errors were encountered: