Hello,
yes indeed, we saw that collective.geo.mapwidget provides the needed
mechanism to build a map
so of course we will use it into our package
regarding the name, collective.geo.configurablelayers will be perfect
something I do not get in mapwidget is how you provide custom js
because the macro mention this:
<script type="text/javascript"
tal:content="structure cgmap/js | nothing"><!--
additional javascript --></script>
but in MapWidget class, I only see:
js = "// default"
and nothing else about it
could we turn it into a property that would store the js into an
annottion into the context object ?
eric
On Thu, Oct 14, 2010 at 9:20 AM, Giorgio Borelli
<[email protected]> wrote:
> Hello,
>
> Il giorno 13/ott/2010, alle ore 16.50, Eric Bréhault ha scritto:
>> 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 ?
>
> Actually we do somethings like that in
> http://svn.plone.org/svn/collective/collective.geo.mapwidget
> Mapwidget package provide a set of adapter to create a map layer and
> configure it in a map.
>
> http://svn.plone.org/svn/collective/collective.geo.mapwidget/trunk/collective/geo/mapwidget/README.txt
>
> c.geo don't have a end user tool to configure these layer without write a bit
> of python code, I think your idea could be useful
>
>> - you agree we name this package "collective.geo.map" ?
>
> maybe 'map' could be a name too generic, I think could be better:
> - collective.geo.configurablelayers
> - g.geo.layerwizard
> - c.geo.configurablelayer
>
> or something similar
>
> I suggest you to use the source in the trunk on the collective repository.
> We have made many changes but there aren't released yet. I hope to release a
> new beta of c.geo soon
>
> You will find short description of the new structure of c.geo packages here,
> http://www.coactivate.org/projects/collectivegeo/lists/collectivegeo-discussion/archive/2010/04/1271787031609/forum_view
>
>
> _____________
> Giorgio
>
>
>
>
>
> _______________________________________________
> Community mailing list
> [email protected]
> http://lists.gispython.org/mailman/listinfo/community
>
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
