Search results for dexterity

collective.geo.leaflet-0.2.3-1.lbn25.noarch

This package use the collective.geo.* suite with leaflet. How to add baseLayer ==================== What is a leaflet baseLayer : http://leafletjs.com/examples/layers-control.html In Plone, if you want to add a baseLayer, you have to add a subscriber on collective.geo.geographer.interfaces.IGeoreferenced (for exemple, in `configure.zcml`):: <subscriber for="collective.geo.geographer.interfaces.IGeoreferenced" provides="collective.geo.leaflet.interfaces.IMapLayer" factory=".maplayers.OpenStreetMap /> After, create your factory in python (`maplayers.py`):: from collective.geo.leaflet.maplayers import MapLayer from Products.Five.browser.pagetemplatefile import ViewPageTemplateFile class OpenStreetMap(MapLayer): name = u"osm" title = _(u"Open Street Map") index = ViewPageTemplateFile('browser/layers/osm.pt') And add your javascript into a template file `osm.pt`:: <script type="text/javascript"> var osmAttrib = '&copy; <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'; var osmUrl = 'http://{s}.tile.osm.org/{z}/{x}/{y}.png'; var %(name)s = L.tileLayer(osmUrl, { attribution: osmAttrib, }); </script>

collective.local.addgroup-1.2.2-1.lbn19.noarch

Allows to create a group and assign roles directly from the sharing tab for Plone 4. Tested on Plone 4.1. Content types have just to implement IAddNewGroup to have the functionnality. Also provides a dexterity behaviour. If you want to enable it for Folder, you only have to add to your buildout.cfg:: [instance] zcml = ... collective.local.addgroup If you don't want the functionality for Folder, but on your own content type, add to the configure.zcml of your policy module:: <include package="collective.local.addgroup" file="minimal.zcml" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.addgroup.interfaces.IAddNewGroup" /> </class> If you just want this for a dexterity content type, you just have to activate the behaviour. The user need to LOCALLY have the "Add Groups" permission to add a new group and "Manage users" to add and remove users from the listed groups. Add group to local list ----------------------- The site manager can add groups from sharing table to locally managed groups list. So then the user with local permissions can manage the group himself. We don't give this feature to local managers to avoid privilege escalation.

collective.local.addgroup-1.2.2-1.lbn25.noarch

Allows to create a group and assign roles directly from the sharing tab for Plone 4. Tested on Plone 4.1. Content types have just to implement IAddNewGroup to have the functionnality. Also provides a dexterity behaviour. If you want to enable it for Folder, you only have to add to your buildout.cfg:: [instance] zcml = ... collective.local.addgroup If you don't want the functionality for Folder, but on your own content type, add to the configure.zcml of your policy module:: <include package="collective.local.addgroup" file="minimal.zcml" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.addgroup.interfaces.IAddNewGroup" /> </class> If you just want this for a dexterity content type, you just have to activate the behaviour. The user need to LOCALLY have the "Add Groups" permission to add a new group and "Manage users" to add and remove users from the listed groups. Add group to local list ----------------------- The site manager can add groups from sharing table to locally managed groups list. So then the user with local permissions can manage the group himself. We don't give this feature to local managers to avoid privilege escalation.

collective.local.sendto-1.6.1-1.lbn19.noarch

Provides a "Mailing" tab on selected content types. It provides a 'send email' form where you can select recipients from the list of members having a local role on the content. Content types have just to implement ISendToAvailable, or, if they are dexterity type, to enable the behavior "Send mail tab". In your policy product : - Add 'collective.local.sendto' to the 'install_requires' parameter of setup.py - Add to the configure.zcml:: <include package="collective.local.sendto" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.sendto.interfaces.ISendToAvailable" /> </class> Roles whose you can select users as recipients are set by a site property : sendToRecipientRoles.

collective.local.sendto-1.6.1-1.lbn25.noarch

Provides a "Mailing" tab on selected content types. It provides a 'send email' form where you can select recipients from the list of members having a local role on the content. Content types have just to implement ISendToAvailable, or, if they are dexterity type, to enable the behavior "Send mail tab". In your policy product : - Add 'collective.local.sendto' to the 'install_requires' parameter of setup.py - Add to the configure.zcml:: <include package="collective.local.sendto" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.sendto.interfaces.ISendToAvailable" /> </class> Roles whose you can select users as recipients are set by a site property : sendToRecipientRoles.

collective.local.userlisting-1.3-1.lbn19.noarch

Provides a "Members" tab on selected content types. The view a the list of members having a role on the content, sorted by role. Content types have just to implement IUserListingAvailable. Add to the configure.zcml on your policy product:: <include package="collective.local.userlisting" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.userlisting.interfaces.IUserListingAvailable" /> </class> You can also check the interface in "Interfaces" tab of content in ZMI. In dexterity, you can select the behaviour.

collective.local.userlisting-1.3-1.lbn25.noarch

Provides a "Members" tab on selected content types. The view a the list of members having a role on the content, sorted by role. Content types have just to implement IUserListingAvailable. Add to the configure.zcml on your policy product:: <include package="collective.local.userlisting" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.userlisting.interfaces.IUserListingAvailable" /> </class> You can also check the interface in "Interfaces" tab of content in ZMI. In dexterity, you can select the behaviour.

collective.local.workspace-1.0rc2-1.lbn19.noarch

This content type bundles all collective.local.* packages. It adds a workspace dexterity content type where the new WorkspaceManager user role can manage a groupware : - inviting new users (to the workspace only) - from collective.local.adduser - creating groups - from collective.local.adduser - from collective.local.addgroup Workspace container have a "Members" tab to show all group members - from collective.local.userlisting -, and an "Emailing" tab to send emails to workspace members - from collective.local.sendto. A layer IWorkspaceLayer is set on request when you are in a workspace. A `get_workspace` method in api module gives you the workspace root of any content. String interpolators give you the title and the url of the workspace in an email rule action.

collective.local.workspace-1.0rc2-1.lbn25.noarch

This content type bundles all collective.local.* packages. It adds a workspace dexterity content type where the new WorkspaceManager user role can manage a groupware : - inviting new users (to the workspace only) - from collective.local.adduser - creating groups - from collective.local.adduser - from collective.local.addgroup Workspace container have a "Members" tab to show all group members - from collective.local.userlisting -, and an "Emailing" tab to send emails to workspace members - from collective.local.sendto. A layer IWorkspaceLayer is set on request when you are in a workspace. A `get_workspace` method in api module gives you the workspace root of any content. String interpolators give you the title and the url of the workspace in an email rule action.

collective.transcode.star-0.21-1.lbn19.noarch

collective.transcode.* or transcode.star for short, is a suite of modules that provide transcoding services to Plone sites. Both the naming scheme and the basic design priciples were inspired by collective.blog.star. Namely: Be modular. Not everyone wants everything your software has to offer. Be flexible. Don't assume that people want to use your software in one way. Be simplistic. If there is a simple way of doing it, do it that way. Be Ploneish. Plone already has 90% of what we need built in. Use it. It works out of the box with standard Plone Files, providing transcoding services to web friendly formats (mp4, ogv) when uploading video content. Additionally, a jpeg thumbnail is being extracted from the 5th second of the videos and a flowplayer viewlet pointing to the produced mp4 file will be displayed inside the IAboveContentBody viewlet manager when transcoding is complete. Transcode.star can be easily configured through the Plone Control Panel to work with any custom AT content type, as long as there is a File field in the schema. In the Transcode Settings panel you can enter a new line in the supported portal types, following the format customPortalType:fileFieldName where customPortalType the name of your portal_type and fileFieldName the name of the file field that you need transcoding for. Support for Dexterity content types is planned for the coming versions. For the transcoding to work you need to start the transcodedaemon instance provided in the buildout. If your transcoding needs are high, you can configure several transcode daemons in a load balanced setup. Transcode.star will select the daemon with the minimum transcoding queue length. All communication between transcode.star and transcode.daemon is encrypted using symmetric encryption by the pycrypto module so that the transcode server(s) transcode videos sent by the Plone site only, preventing abuse by third parties. Also extra care has been taken to transcode videos in private state (typical senario for a Plone site, when users upload a file) by using the same secure channel.