Search results

five.intid-1.1.2-1.lbn25.noarch

s package makes it possible to use zope.app.intid (and consequentually other packages that rely on it such as zope.app.keyreference) in a Zope2 environment.

five.localsitemanager-2.0.6-1.lbn25.noarch

five.localsitemanager attempts to provide a local site manager implementation that is as close to Zope 3's implementation as possible. Some reservations that do not conflict with Zope 3 have been made to ease the path with CMF.

five.pt-2.2.4-1.lbn19.noarch

This package brings the Chameleon template engine to the Zope 2 platform. Five is supported. It works using monkey-patching onto the existing API (specifically, the TALInterpreter and PageTemplate classes). In simple terms, what the patching does is to replace the TAL interpreter class and make sure that the so-called "cooking" routine uses the Chameleon parser and compiler instead of the zope.* reference implementation.

ftw.bridge.client-1.0.7-1.lbn19.noarch

The ftw.bridge tools are used for communication between several Plone instances. It is also possible to cummuncate with other web services. Requests between web services are proxied through the ftw.bridge.proxy. This makes it possible to move or reconfigure certain dependent webservices (clients) only by reconfiguring the proxy. The clients do not know where other target clients are located - they only communicate with the proxy directly, which forwards the requests to the target client. Features ftw.bridge.client integrates ftw.bridge support into Plone. It provides tools and utilities for communication and authentication. * Authentication: A PAS plugin authenticates requests and logs the user in on the target client without transmitting his password. Only requests from the configured ftw.bridge.proxy are authenticated. * Requests: The IBridgeRequest utility is used for making requesting other clients. It is also able to make remote catalog queries and transmitting the result brains to the sources by using fake brains. * Brain transport: By using a BrainRepresentation it is possible to get brains from a remote client. A BrainSerializer utility serializes and deserializes all brain metadata so that they can be used on the source client. * Watcher portlet: A recently-modified portlet can be used for generic listing a list of recently modified objects on the remote client but it is also possible to list other links. There is a browser view @@watch which creates a recently-modified portlet on the remote client dashboard. The watcher portlet loads its data asynchronously using javascript for not blocking while loading the dashboard. * Favorites: A browser view @@remote-add-favorite adds the context to the favorites on the remote client dashboard.

ftw.bridge.proxy-1.1.1-4.lbn19.noarch

ftw.bridge.proxy is a small pyramid based web application for proxying requests between multiple plone instances. It's purpose is to isolate the plone instances by routing through this proxy. This allows to easily move plone instances to other servers. Maintenance mode Each configured client (plone site) can be switched into maintenance mode on the bridge. When maintenance mode is enabled, the bridge answers every request to this client with a HTTP 503 (Service Unavailable). The maintenance mode can be enabled in the manage view of the bridge (/manage).

ftw.builder-1.8.1-1.lbn19.noarch

Create Plone objects in tests with the Builder Pattern. The builder pattern simplifies constructing objects. In tests we often need to create Plone objects, sometimes a single object, sometimes a whole graph of objects. Using the builder pattern allows us to do this in a DRY way, so that we do not repeat this over and over.

ftw.calendar-2.1.0-1.lbn19.noarch

Calendar view based on fullcalendar

ftw.calendarwidget-1.1.11-1.lbn19.noarch

ftw.calendarwidget provides an archetypes calendar widget using the jQuery UI datepicker.

ftw.colorbox-1.2.0-1.lbn19.noarch

ColorBox is a lightweight customizable lightbox plugin for jQuery. More information about ColorBox can be found here: http://jacklmoore.com/colorbox/ ftw.colorbox adds a new view called colorbox_view for folders and topics which integrates ColorBox in Plone.

ftw.contentpage-1.13.0-1.lbn19.noarch

ftw.contentpage provides some content types optimized for organisations, communities, associations, and more. It uses simplelayout to manage and display the content. Types: ContentPage: Folderish type for the site structure. Contains the blocks AddressBlock: AddressBlock contains address informations and it uses ftw.geo to render a map ListingBlock: A folderish block, which lists files and images by default. Two block views are provided: Tabular listing and a gallery view. The columns of the file listing are configurable per block. The default set of columns is configured through the the registry (plone.app.registry). The default sort order of the Listingblock file listing can be configured per block. EventPage / EventFolder: A simple and minimal event implementation based on a ContentPage. News / NewsFolder: A simple news implementation based on a ContentPage. Special views: There's a two-column and two-level overview named authorities_view, which displays a list of ContentPages with with the IAuthority interface. The IAuthority interface ist added and removed by ticking a checkbox called "Mark content for listings" on the ContentPage. This allows to decide if a ContentPage is displayed on the authorities_view manually. The checkbox is implemented with archetypes.schemaextender, which allows to extend other content types: Code example: <class class="dotted.name.to.my.class"> <implements interface="ftw.contentpage.interfaces.IAuthoritySupport" /> </class> The Checkbox is protected with the permission: ftw.contentpage: Toggle IAuthority marker interface. The EventFolder has a simple events listing, which shows the next 10 upcoming events (batching included). The NewsFolder has a simple news listing, which shows the 10 most recent news entries (batching included). ContentListing viewlet: The content listing viewlet is registered for all ContentPages. It shows categorized subcontent, within the ContentPage The categorization is done by a schemaextended field, so it's also possible to categorize your own or any other content. Code example: <class class="dotted.name.to.my.class"> <implements interface="ftw.contentpage.interfaces.ICategorizable" /> </class> ** Teaser Image ** All content pages, event pages and news are able to display a teaser image, which is stored on the content itself. It behaves like a regular block and shows also the description. The teaser image related fields have their own write permission, one per content type. Take a look at the rolemap.xml for details. ** Portlet ** It's possible to enable an archive portlet for News and EventPages. It only works if the current view is the news or event listing view. The portlet is not created by default. ftw.contentpage is using the additional slot provided by simplelayout (implements the IAdditionalListingEnabled interface of simplelayout) So the layout has the following structure: Simplelayout main slot for blocks The content listing viewlet The additional slot for blocks This way it's possible to display content below the content listing viewlet (by drag'n'drop) ftw.lawgiver support ftw.contentpage supports ftw.lawgiver