allow selection to be rendered as separate layer

[madair]

render selections in a separate layer using the GETDYNAMICOVERLAY mapagent call.

[madair]

(In [1501]) re #120: optionally render selections in a separate layer and allow setting the color and format for selections

• configured through AppDef

[madair]

this also allows setting the color for selections.

Note that currently, the baselayer is still rendered with GETMAPIMAGE which includes the selections as well. The current OL implementation of MapGuide layer type uses the GETMAPIMAGE mapagent call for baselayers.

I think ideally in the long run a much better approach would be for Selection.php to return selected feature geometries which would get rendered in a vector layer in the browser using OL vector drawing code. This wold allow client-side feature manipulation (e.g. highlight effects on hover).

[madair]

(In [1574]) re #120: updated OpenLayers at v2.7 and custom build config file; includes a patch for the OL MapGuide layer to optionally render layers using GETDYNAMICOVERLAY calls.

[pagameba]

(In [1575]) re #120, make selectionasoverlay the default case and turn it off if explicitly requested in the app def.

[madair]

(In [1583]) re #120: patched version of OL which uses asynchronous calls for GETVISIBLEMAPEXTENT and supports the useOverlay flag

[madair]

(In [1625]) re #120: update of OL Mapguide layer to use the new GETDYNAMICOVERLAY API call from MapGuide

[madair]

(In [1626]) re #120: remove siteVersion check until it can be tested more

[madair]

(In [1627]) re #120: set useOverlay to default to true; prevent redrawing the map after a selection

[madair]

(In [1658]) re #120: for backwards compatibility, set useOverlay to false for MG installs prior to v2.1.x; move the PHP siteVersion element to LoadMap because opening a template from studio by-passes the CreateSesssion.php call

[madair]

closing, this was implemented months ago. New issues with MapGuide selections can be entered as new tickets