Hello, I m one of colleagues of Eric. I have read many features request for that egg in the thread. For sure it s simple to add openlayers in plone, cause it s just a set javascripts. For sure you want to do every things possible with OpenLayers, specialy for your projects.
But it s not the topic. The main idea is that the egg must be as customizable as possible to fit to developper needs, without doing the features your customer are waiting for. For example, you want a tool bar just before your openlayers, you just have to call a macro, and give it your toolbar's elements. You want to have a specific configuration for wms to be availables ? You just have to specify the wms tal variable before calling the macro. The default configuration is available throw a property sheet in the portal_properties, so if you just call a macro you get it. (google key, default wms, default_size, ...) The integration in portal_javascript is important. you can compress it, merge it if you want ... and just by put a marker in the page, you know OpenLayers is available. So we have started by doing this: - Add a profile to add OpenLayers in the portal_javascript and portal_skin - remove all call to img/xxx to be able to customize every icons used by OpenLayers - Writing some macros (displaying georss, editing macro, toolbars, ...) - Unittest the module The GOAL is to integrate OpenLayers faster in your plone project. Not to answer to any customer needs. For that we need to define every possible integration of openlayer features, to define many other macros. Finaly, adding your JS in each GIS plone product, is very hard to maintain and not a good way of doing in a component architecture. Cordialement, JeanMichel FRANCOIS Makina-Corpus Le Wednesday 23 April 2008 18:22:18 Eric Bréhault, vous avez écrit : > Hello, > > Some colleagues of mine are currently working on a product to manage > OpenLayers in Plone 3. > This product provides the OpenLayers library in its skin, and offers > different macros to manage the layers, the OL toolbar, etc. > > It does not provide any Plone content type, so basically it is just a > Plone/OL integration toolkit. > > I know there are other persons here who are developing OL Plone 3 > integration products (like EryrOpenlayers for instance, but there are > maybe others in preparation). > Personally, I need OL to display a WFS layer served by zgeo.wfs. > Another colleague of mine needs OL to create an AT geo widget. > > There are very different needs, and they implies different way to > interact with the OL library and web interface. > > So I am wondering if we could join our efforts to define and maintain > a generic OL toolkit that could be used by any Plone 3 content > type/products that may need to display OL. > > Regards, > > Eric BREHAULT > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
