| Nested Work Contexts/Workspaces |
|
|
|
| Written by Simon Nitz | |
| Wednesday, 07 February 2007 | |
|
Ability to nest one work context/workspace within another work context/workspace in a similar fashion to MapInfo Encounter. When creating Work Contexts in Exponare there is a lot of duplication and effort involved during configuration of the work contexts – many of the same settings are used over and over again for different work contexts that have predominantly the same content, but may differ by only a few layers. For example a work context containing aerial photography is predominantly the same as a work context without. Within MapInfo Encounter the nested workspace feature provided a much smarter way of changing the context of the map: The initial workspace loaded up the base layers (parcels, roads, labels etc) and then nested workspaces containing only relevant layers (e.g. aerials, or dogs, or sewer utilities, etc) were able to be loaded/unloaded into the base workspace. Multiple levels of nesting provided excellent flexibility e.g. base workspace + sewer workspace + aerial workspace The other big advantage comes when the administrator needs to change any configuration values that apply to the base work context (e.g. a url change in a hyperlink embedded in a SQL databind). The value only needs to be changed once. Currently in Exponare values need to be changed across all work contexts that have that base configuration value. This can add up to a significant amount of time for the Administrator. This should mean that the Exponare configuration.xml file would also be smaller in size. Comments (1)
![]() Write comment
|
| < Prev | Next > |
|---|
























