Yes, that is my intention, too: being able to serialize/deserialize a map configuration. Is your project open source?
I have started to work in that direction: defining a schema (currently no XSD, but an eclipse ecore model), so I can define the map configuration in Java, then, generate JS code from it and evaluate it in the browser: https://github.com/erdalkaraca/geoff 2013/2/27 Phil Scadden <p.scad...@gns.cri.nz>: > I create maps pretty much in the style, where I load the "declarations" as a > json object, and then have the code translates this into the map and layer > properties. I have a webapp for creating the map and the behaviours you want > on the map and in interactions with the layer and it saves the config as > this json file. > > Notice: This email and any attachments are confidential. > If received in error please destroy and immediately notify us. > Do not copy or disclose the contents. > > _______________________________________________ > Users mailing list > us...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/openlayers-users _______________________________________________ Users mailing list us...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-users
