Implement workspaces to allow multiple maps and layouts

[yvesm]

As currently implemented, workspaces do not allow one to use more than one <map> and template (<layout>). It should be possible to add more than one <map> object in the configuration file and workspaces should be able to use one of them. An example use case would be to allow users access different maps altogether (e.g. projections, layers, etc.) or to have a different view of a same map (e.g. maxextent).

In some cases, users have requested the possibility to have a very light template with a minimum set of JS libraries and Ext components. Workspaces should provide for using different <layout> objects.

[adube]

Replaces workspace.patch. Is basically the same but with minor changes, such as code cleaning. The old patch was also missing a file which is now included in this one.

[adube]

I tested workspace2.patch. I confirm that the changes made accomplish quite well what it was intended to do : map and/or layout selection in workspace. Theses new tags in the workspace tag are optionals so there's no backward compatibility. I tested other samples that are using the XMLWorkspaceConfig driver and they still work well. I'd say it's ready for commit (by using workspace2.patch).

Good work
+1

[yvesm]

Thanx for your review Alexandre. If you ever find a tool that readily generates the before/after side by side comparisons of all the diffed files in a patch, please let me know. A Meld plug-in anyone ;-). Looking at patches that list several files is a PITA.

Of course, this has nothing to do with you ;-) Thanx again.

[yvesm]

done : r745