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
When this library was originally written, it was done in vanilla JS for the greatest amount of compatibility -- for instance, it could be used on demos that wasn't based on Leaflet. (See, for example, the demos on the Vector Tiles product page, only one of which is based on Leaflet.)
However, a Leaflet plugin could lead to some other benefits -- for instance, placing it within a Leaflet overlay container makes it easier to prevent situations where multiple UI components overlap each other because they are not aware of each other.
This would be a pretty considerable rewrite or augmentation of this library and may likely prevent it from working outside of a Leaflet context. This means there's a lot of work, and we lose something in the trade. I'm putting this issue here so that we have a point of reference to go off on should we start considering this in the future, not to suggest that we need to do this right away.
The text was updated successfully, but these errors were encountered:
When this library was originally written, it was done in vanilla JS for the greatest amount of compatibility -- for instance, it could be used on demos that wasn't based on Leaflet. (See, for example, the demos on the Vector Tiles product page, only one of which is based on Leaflet.)
However, a Leaflet plugin could lead to some other benefits -- for instance, placing it within a Leaflet overlay container makes it easier to prevent situations where multiple UI components overlap each other because they are not aware of each other.
This would be a pretty considerable rewrite or augmentation of this library and may likely prevent it from working outside of a Leaflet context. This means there's a lot of work, and we lose something in the trade. I'm putting this issue here so that we have a point of reference to go off on should we start considering this in the future, not to suggest that we need to do this right away.
The text was updated successfully, but these errors were encountered: