Search results

collective.geo.wms-0.2-1.lbn19.noarch

collective.geo.wms is a product which enables you to embed WMS, TMS and WMTS layers in your website. It is designed to make adding WMS, TMS or WMTS layers as easy as possible. Why WMS/TMS/WMTS You will find thousands of public Map Servers with interesting and valuable information which you can display on your website. Many of these services provide WMS,TMS or WMTS only. Usage First you have to add a WMS Server to your site. The initial add form only allows you to enter the url and type of a webservice. The title, description and keywords are taken from the service if it produces a valid response to the getCapabilities query. When the server could be successfully added you can change the title, descripton and keywords. You are not allowed to change the server url or protocol. A list of layers that are available on this server will be requested directly from the server. The list of layers will be cached for 100 minutes so if layers are added on the server you may have to wait up to 2 hours for them to refresh. After you added the servers you can add layers to your website. Layers are displayed as a Map. In the add form you choose the service for your maps. You cannot change the server later by editing the layer. After you added the layer you have to choose the layers of the service you want to display in your map. Some WMS Servers do not support overlaying layers on the serverside if this is the case for the server you are connecting to you have to check 'Single Layers' for them to display. When you click on a feature on the map a request is sent to the server to get information about this feature (or features) which are displayed in a pop up. This behaviour can be disabled by unchecking 'Feature Info'

collective.geo.zugmap-1.0.2-1.lbn19.noarch

collective.geo.zugmap provides a maplayer for zugmap

collective.geolocationbehavior-1.5-1.lbn19.noarch

A behavior which makes it possible to mark and item with a geographic location.

collective.geotransform-1.0a2-1.lbn19.noarch

GEO stands for "Gracefully E-mail Obfuscation". This package implements the solution exposed in this post of List Apart web site authored by Roel Van Gils: http://www.alistapart.com/articles/gracefulemailobfuscation/ collective.geotransform uses plone.transformchain to transform the response output from Zope before it reaches your browser. It searches for all "mailto:" occurences inside the response and transform them into encoded harmless links. This codification is done via a simple base64 encoding, but enough to fool a spam robot. This is the form of the encoded mail link: ::<a rel="nofollow" href="contact/dmljdG9yLmZlcm5hbmRlejJAdXBjbmV0LmVz">mymail</a> On the browser side, the encoded links are decoded to their original form by using a Javascript that restore them to normal "mailto:" links. The text of the link is replaced by the full E-mail specified in the original mailto attribute. Authenticated responses are NOT affected by this transform. Only anonymous responses are modified.

collective.googleanalytics-1.6.1-2.lbn25.noarch

collective.googleanalytics is a product that integrates Plone with Google Analytics. It includes both tracking and reporting functionality. The product enables easy tracking of the standard Google statistics as well as external links, e-mail address clicks and file downloads. It also defines Analytics reports that are used to query Google and display the results using Google Visualizations. Reports are Zope objects that can be imported and exported using GenericSetup XML and modified on a site-by-site basis. The product currently provides a portlet that can display results of reports as well as a control panel for authorizing your site and configuring settings.

collective.groupdashboard-1.0b2-1.lbn19.noarch

This package adds the ability to manage dashboard portlets on a per-group basis. Once installed, a site manager will be able go to the "Group Portlets" tab when editing a group and then click the "Edit group dashboard portlets" link. From here, group dashboard portlets can be assigned as normal. Any member in that group will then see the relevant portlets on their dashboard. Note that group portlets will appear below the user's own portlets. To make it easier to lock down the dashboard, the view and edit permissions have been separated. You can take away the "Portlets: Manage own portlets" permission to let users view the dashboard without the ability to edit it.

collective.groupspace.content-1.0.2-1.lbn19.noarch

Implements a folderish content type that implements the ILocalGroupSpacePASRoles interface, This interface allows managemment of dynamic roles for users and groups in a context, and is implemented in collective.groupspace.roles.

collective.groupspace.mail-1.0.1-1.lbn19.noarch

Implements a mail tab for any content type implementing the ILocalGroupSpacePASRoles interface, This interface allows managemment of dynamic roles for users and groups in a context, and is implemented in collective.groupspace.roles. An example content type providing a mail tab is contained in collective.groupspace.content. The tab looks like the standard Plone "Send this page to someone" interface, but instead of manually filling in an email address, you can choose the recipients of the message from a list of participants that have a role in the context of your content type.

collective.groupspace.roles-1.0.3-1.lbn19.noarch

Implements a roles tab for any content type implementing the ILocalGroupSpacePASRoles interface. An example content type is contained in collective.groupspace.content. The tab looks exactly like the Plone sharing tab, but local roles for users and groups are stored in two attributes on the content type. The local roles can then be assigned in the context of a GroupSpace, and are dynamically added to the roles of a visiting user with borg.localrole.

collective.groupspace.workflow-1.0.4-1.lbn19.noarch

mplements a placeful workflow policy needed for the GroupSpace content type of collective.groupspace.content that makes sure that, unless otherwise defined, all content types use the default workflow as defined by the placeful workflow policy.