Opened 14 years ago
Last modified 12 years ago
#121 new enhancement
Database config - other - overwrite resource options
| Reported by: | adube | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.8.0 |
| Component: | server | Version: | |
| Keywords: | Cc: |
Description
With the XMLWorkspaceConfig, you can overwrite options of objects inside a workspace. It would be interesting to do the same inside the new model.
There are two objects containing lists of objects :
- mapcontext (contain resources)
- application (contain widget)
IMHO, it appears useless to overwrite widget options inside an application. Since widget don't have resource-specific options in the new model, it's simpler to create an other widget of the same type, set the different options and simply use that other widget inside the application.
For the resources inside the mapcontext, that's an other story. It looks more useful to be able to redefine scales, extents, widget-related options (for example we could want a mapcontext to not add any zoom widgets at all). We could have a new mcconfig_mapcontextresourceoptions table for these changes.
Comments welcomed.
resource option OR mapcontext resource option ?
In a way, 'resource options' should be used specifically to link resources to widget and to define some default layer options that are 100% sure to be always default.
Other kind of 'resource options' that are used for OpenLayers.Layer object creations should be defined as 'mapcontext resource options'. For example, setting 'opacity' to 0.50 as a resource option means that the data itself is 50% transparent (which is wrong). Setting the 'opacity' as a mapcontext resource option means that the layer added to the map (mapcontext) should be 50% transparent in this map (which is ok).