The LayerSelector is quite messy at the moment. I am thinking about a smaller or bigger rework of the whole thing. This functionality is currently supported by the Layerselector:
One Layer can corresponds to one button that toggles visibility.
A layer group can correspond to category button. A click on the category button does normally collapse or expand all contained layers.
A category button can be separated into two buttons. Than the second button does activate/deactivate all buttons.
It is possible to combine multiple layers into one button.
A WMS Layer can be shown as different buttons that activate different layers in the server request.
A WMS Layer can have an info-toggle button that toggles the get feature info capabilities.
If a WMS Layer is shown as different buttons, it can have a category button.
Activation of a baselayer deactivates other baselayers (not neccessarily a feature of the layerselector)
A certain layer button can get a special class name given through the config (i.e. for coloring).
A click on a layer can open an info window.
There exists a mobile view.
Ideas:
Stronger separation of the actual view and the building. That means having classes category and button that provide all needed events for all uses cases. This would separate the view concerns better from the classes used behind.
simonseyock
commented
6 years ago
The LayerSelector is quite messy at the moment. I am thinking about a smaller or bigger rework of the whole thing. This functionality is currently supported by the Layerselector:
Ideas:
Stronger separation of the actual view and the building. That means having classes category and button that provide all needed events for all uses cases. This would separate the view concerns better from the classes used behind.