[mapguide-trac] #606: Maestro: Consider adding a "Repointer" function

[MapGuide Open Source]

#606: Maestro: Consider adding a "Repointer" function
-------------------------+--------------------------------------------------
 Reporter:  jbirch       |         Owner:  ksgeograf
     Type:  enhancement  |        Status:  new      
 Priority:  low          |     Milestone:           
Component:  Maestro      |       Version:           
 Severity:  trivial      |    Resolution:           
 Keywords:               |   External_id:           
-------------------------+--------------------------------------------------
Old description:

> It would be useful to be able to click on a Layer and say "Point all maps
> that reference this layer to this other layer instead", and the same for
> MapDefinitions (and WebLayouts/ApplicationDefinitions).
>
> Similar option would be cool for data connections as well, but much more
> complex because of potential for mis-matched schemas.  To implement this
> you would also need to have a validity checker for layer definitions,
> allowing the user to list layers with invalid definitions, and visually
> see which properties are invalid when the layer is open.  MapGuide Studio
> (at least up to 2008?) just resets the layer definition when there are
> different schemas regardless of whether it would invalidate the layer
> definition, but this is not a desirable behaviour.

New description:

 It would be useful to be able to click on a Layer and say "Point all maps
 that reference this layer to this other layer instead", and the same for
 !MapDefinitions (and !WebLayouts/ApplicationDefinitions).  This would
 allow for simple testing of new layer definitions before swapping into
 live maps.

 Similar option would be cool for data connections as well, but much more
 complex because of potential for mis-matched schemas.  To implement this
 you would also need to have a validity checker for layer definitions,
 allowing the user to list layers with invalid definitions, and visually
 see which properties are invalid when the layer is open.  !MapGuide Studio
 (at least up to 2008?) just resets the layer definition when there are
 different schemas regardless of whether it would invalidate the layer
 definition, but this is not a desirable behaviour.

-- 
Ticket URL: <https://trac.osgeo.org/mapguide/ticket/606#comment:1>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals