I really don't like how the map objects and the wms objects relate to each other.

The global JavaScript variable "wms" is an array of WMS objects. The variable "map" is an array of map objects. Each map object has an additional "wms" array and these entries point to the WMS within global variable "wms".

This means that you have at least one WMS in two or more map objects, so manipulating it in a single map also alters it in the other. I assume removing the global WMS object and storing the data in each map object would be more consistent.

Please enlighten me if you have an explanation why the current solution is superior.

Christoph

--
_______________________________________

W h e r e G r o u p GmbH & Co. KG

Siemensstraße 8
53121 Bonn
Germany

Christoph Baudson
Anwendungsentwickler

Fon: +49 (0)228 / 90 90 38 - 15
Fax: +49 (0)228 / 90 90 38 - 11
[EMAIL PROTECTED]
www.wheregroup.com
Amtsgericht Bonn, HRA 6788
_______________________________________

Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Arnulf Christl, Olaf Knopp, Peter Stamm
_______________________________________


_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev

Reply via email to