Steve, I thought of another way of possibly approaching this. What about assembling the OpenLayers interface upon init from the server. Then a reload would at least work to update things.
I'm trying to get out of all this OpenLayers specific coding that is required for things like a good Legend and layer control, which seems overly painful for some reason. bobb >>> Stephen Woodbridge <[email protected]> wrote: > > > Is there a way to use MapServer (my choice of poison) templates top > populate the Layerswitcher in some fashion? > > > Where we're al now on things: > /http://pwultra5.ci.stpaul.mn.us/cp_tiles/OpenLayers/OL.AVL.10-rlb.html/ > Bob, You are thinking about the problem the wrong way. If you were developing a server side application, then you would configure the layer switch this way. But with a Web 2.0 application like OpenLayers, you would issue and Ajax request to get some information and then have the response handler to that request update the web application. So you probably need to build a custom layer switch that you can inject data from your ajax request that will then cause it to update itself based on that information. If you choose to use a mapserver template as your ajax service that is fine, have it return json or xml and so your javascript handler can parse it and do whatever you need. -Steve _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
_______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
