Add a basemap componant/module
Currently, a list of basemap is definable under the componant SHOP and then used to "pick one of this basemap for the SHOP front-end interface in step 2.
We see that basemap can be used in many different componants and modules (CATALOG for example too).
I suggest to move this basemap list outside of the SHOP componant and make a independant componant (or module) to manage this list.
Then other componants like SHOP or CATALOG can point to the basemap item to choose the desired one.
Any comments ?
#1 Updated by Magoni Bruno over 9 years ago
This is a good idea to have a fully independant basemap container which can be reused inside several EasySDI components.
As basemaps could be used by other EasySDI components, I would like to propose that basemaps definition will be part of the CORE component and not be a self component.
We must be aware when reengineering source code that basemaps definition are now used by the new MAP component.
#10 Updated by Magoni Bruno over 5 years ago
- Status changed from Affected to Resolved
- Assignee deleted (
Good news about this feature :-)
In easySDI V4, administrator can create maps (previously map contexts) with MAP component.
All these maps can be used in other component (i.e. permieter's definition in SHOP component), so there is no more basemap or map context needed to be defined in other component than MAP! Each map is reusable totally in each easySDI component!