Hello, collective.geo.openlayers allows to integrate OL into Plone, but it does not allow to create maps easily (the only option is to create a .pt in the skin and insert some javascript code).
On our current project, we need to provide a way to configure OpenLayers maps into a Plone site without changing templates in the skin. Here is what we propose: - create an adapter (+a form) to store a Javascript code into an annotation, so users can configure their layers, add extra controls, etc. - create a browserview to display the resulting map - all of that would be plugged on any existing Plone object just by implementing a mark interface - we could imagine to provide a default Javascript code, to make sure the user can get a working map (with correct zooming and centring, etc.) before he/she starts customizing it, this default code could be stored into an annotation on the Plone site object, and managed through a configlet. I would like to know if: - you think it is a good idea ? - you agree we name this package "collective.geo.map" ? Note: in our usage scenario, the user is supposed to change the JS manually into the Plone interface, it is a good thing as it allows to do any customization the user might want, but it implies he/she knows about the OL API, so maybe a second step for this package could be to provide a wizard mode, so the user could specify his/her layers parameters into a form, and it would produce the JS dynamically of course, the Advanced mode would still allow to change the javascript manually Eric _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
