SepalMap takes too much time to init

[12rambau]

I checked on my computer a normal ipyleaflet map takes 5s to start, a SepalMap consume a good 50s i.e. 10x more time.

I think it's related to the differnet widget we init with the map iteslf (drawing control, fullscreencontrol, etc...) this take lots of resources and even more if the end developer is not using them. I think we should work on 2 things:

• reduce the computation burden of the layersControl
• init virgin SepalMap and let the developers add what they need

[12rambau]

@dfguerrerom di you start your map with buitl-in widgets or do you use virgin map and add them manually ?

[dfguerrerom]

What types of controls do you refer to? if are the basic ones such as ZoomControl, LayersControl or ScaleControl, yes I don't want to add them manually, I think the initialization of our SepalMap is functional and minimal.

[12rambau]

I was effectively thinking abut them, if you look at ipyleaflet, it starts completely virgin from any controls. The only default ones are copyrights and zoom levels.

[dfguerrerom]

I see more use cases where you at least have those defaults + LayerControl, I don't have too many examples in my mind where you only need the zoom levels and copyrights.