You are here: Home

Modified items

All recently modified items, latest first.
Debug toolbar for Plone
This package integrates five.customerize_ into Plone, which enables site administrators to customize templates used for five/zope3-style views, viewlets and portlets through the web via the ZMI in a way similar to overriding filesystem-based skin elements via the portal skin "customize" procedure.
RPMPackage provides Plone-specific conditions and actions, as well as a user interface for plone.contentrules.
RPMPackage text/h323
============ contains the logic that powers Plone's content menu (the green one with the drop-down menus).
RPMPackage plone-4.3.17-1.lbn25.noarch
Plone is ideal as an intranet and extranet server, as a document publishing system, a portal server and as a groupware tool for collaboration between separately located entities. A versatile software product like Plone can be used in a myriad of ways. Look through the sites that use Plone section to see a variety of ways people have implemented Plone and Zope solutions.
RPMPackage grokcore.viewlet-1.11-2.lbn25.noarch
This package provides support to write and register Zope Viewlets directly in Python (without ZCML). It’s designed to be used with grokcore.view which let you write and register Zope Views.
RPMPackage grokcore.view-2.11-1.lbn25.noarch
This package provides support for writing browser pages for Zope and registering them directly in Python (without ZCML).
This package provides support to write local site and utilities for Zope directly in Python (without ZCML).
This package provides basic elements for defining Zope permissions and security checkers without ZCML.
RPMPackage grokcore.formlib-1.11-1.lbn25.noarch
This package provides support for writing forms using the Zope Formlib library and registering them directly in Python (without ZCML).
RPMPackage grokcore.content-1.3.1-1.lbn25.noarch
This package provides base classes of basic content types.
RPMPackage grokcore.component-2.7-1.lbn25.noarch
This package provides base classes of basic component types for the Zope Component Architecture, as well as means for configuring and registering them directly in Python (without ZCML).
RPMPackage grokcore.annotation-1.5.1-1.lbn25.noarch
This package provides a support to simplify the use of annotations in Zope.
RPMPackage ftw.table-1.18.1-1.lbn25.noarch
The ftw.table package provides a table generator utility, which generates a html table out of a list of almost anything. The Javascript, which will be registered, contains an extensible jQuery plugin. Using the optional extJS addon enables features such as grouping, sorting, filtering drag'n'drop ordering, checkboxes, etc.
RPMPackage ftw.tabbedview-3.8.3-1.lbn25.noarch
Introduction ============ This package provides a generic view with multiple tabs for plone. It provides a generic base tab for listing contents in a table, based on `ftw.table`_. Features ======== - Generic tabbed view - Tabs are registered through FTI actions - Base view for listing tabs - Listing tabs are filterable - Perform configurable actions on listed items - `ftw.table`_'s `Ext JS`_ support works also in listing tables - Fallback tables - Drag'n drop multiple file upload functionality (using quickupload plugin)
RPMPackage ftw.slider-2.4.1-1.lbn25.noarch
This product let you create a simple slideshow, using slick. In each slider-pane you can define: An image HTML text A link If ftw.contentpage is installed there will be registered a new view for the ListingBlock displaying images in a carousel. See last screenshot.
RPMPackage ftw.publisher.sender-2.2.0-1.lbn25.noarch
Introduction The ftw.publisher packages provide tools for publishing plone contents from one instance to another. By providing a simple mechanism to invoke the publishing, it's possible to set up the publisher in a variety of ways, such as workflow bound, manually invoked or automated publication. The ftw.publisher package library also provides a variety of surveillance and analysis tools for making maintenance confortable. Staging The ftw.publisher is meant to be used in a environment where there are two seperate plone-sites which do not share their database. The editors work on a editorial site and the contents are published to a public site when they are ready. Setting up such an environment with ftw.publisher let you have a powerful staging solution with completly isolated instances. Network security Using an environment with two isolated installations makes it possible to protect the editorial site with firewalls or to put it even in a private company network. This way the editorial site is completly protected from the internet, which is in some use cases mandatory for protecting other - unpublished - contents (for example when publishing the internet contents from the intranet). Component support * Archetypes objects * Standard Archetypes field types * Topics: criterias are published automatically when topic is published * Backreferences - references are added automatically as soon both objects are published * Additional interfaces added on /manage_interfaces or by other products * Contextual portlets * Properties With the publisher adapter structure it is as easy as creating another adapter to support other components. For instance annotations are not supported by design, because you may not want to publish all annotations but only certain ones. Therefore it is easyer to implement custom adapters for those annotations which need to be published.
RPMPackage ftw.publisher.receiver-2.0.2-1.lbn25.noarch
The ftw.publisher packages provide tools for publishing plone contents from one instance to another. This package should be installed on the receiver instance. It provides tools for unserializing publishing requests and creating, updating or deleting objects.
RPMPackage ftw.publisher.core-2.3.3-1.lbn25.noarch
The ftw.publisher packages provide tools for publishing plone contents from one instance to another. This package provides shared tools and utils used by ftw.publisher.sender and ftw.publisher.receiver.
RPMPackage ftw.profilehook-1.2.1-1.lbn25.noarch
ftw.profilehook provides a hook for executing custom code after a generic setup profile is installed. Motivation We often use import steps for executing code after import a generic setup profile. Registering a lot of setup handlers is bad because it extends the import duration of every profile and the amount of import steps are limited in generic setup, causing bad effects when exceeded. Import steps are meant to import things from any profile, not for executing code after importing a specific profile. Because of these reasons ftw.profilehook exists and provides an easy method to solve this issue.
To see exactly what is included in BastionLinux™, visit our online RPMDistro Builder.
Buy Now
Bastion CD
Subscribe Now
and get BastionLinux™ ...
Sponsored Links