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
{{ message }}
This repository has been archived by the owner on May 6, 2021. It is now read-only.
Plugins are used in order to implement specific selection methods.
In MapStore a Plugin must provide a complete functionality, available in the Viewer when his configuration is enabled. This isn't the case of the current XXXSelectionMethod plugins.
These cases, which include specific operations, require the use of widgets. Widgets can be used by a certain plugin in order to provide full functionality (the mapstore's Tool).
Then the plugin configuration could contain the widgets's configuration to use.
This behavior make the widgets more reusable for all mapstore tools, a widgets isn't a plugin.
The text was updated successfully, but these errors were encountered:
* Export button fixes.
* Review retrocompatibility for show CSV
* Allow file export for complex filters
* New option `exportDoubleCheck`: Flag to make check before export
* Fixes IE 8 bug on feature grid plugin (on export action)
* Fix feature grid layout for IE
* Select `CSV` as default export for the export window.
* Refactor spatial selectors methods
* Refactor code of the spatial selector methods as widgets instead plugins to fixgeosolutions-it#339 issue.
* Optionally add a geometry operation combo for the spatial filter
alediator
added a commit
to alediator/mapstore
that referenced
this issue
Mar 14, 2014
About the pull request below:
#333
Plugins are used in order to implement specific selection methods.
In MapStore a Plugin must provide a complete functionality, available in the Viewer when his configuration is enabled. This isn't the case of the current XXXSelectionMethod plugins.
These cases, which include specific operations, require the use of widgets. Widgets can be used by a certain plugin in order to provide full functionality (the mapstore's Tool).
Then the plugin configuration could contain the widgets's configuration to use.
This behavior make the widgets more reusable for all mapstore tools, a widgets isn't a plugin.
The text was updated successfully, but these errors were encountered: