You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage raptus.article.nesting-2.0b4-2.lbn25.noarch
Manage where you will list your bottom articles. Disable your article for random fader or other listings. The following features for raptus.article are provided by this package: Content ------- * Provides nesting support for articles
RPMPackage raptus.article.listings-2.0b9-1.lbn25.noarch
Provides basic listing components which display articles contained in the article. The following features for raptus.article are provided by this package: Components ---------- * Listing columns (List of the contained articles arranged in columns.) * Listing left (List of the contained articles with their image on the left side.) * Listing right (List of the contained articles with their image on the right side.)
RPMPackage raptus.article.links-2.0b6-1.lbn25.noarch
Provides support for adding links to articles. The following features for raptus.article are provided by this package: Content ------- * Link - add your links in a article. Components ---------- * Links (List of links contained in the article)
RPMPackage raptus.article.lightboxgallery-2.0b9-1.lbn25.noarch
Provides an inline lightbox component with a horizontal gallery showing the images contained in the article. The following features for raptus.article are provided by this package: Components ------------ * Lightbox with gallery (Lightbox of the images contained in the article including a horizontal gallery)
RPMPackage raptus.article.lightbox-2.0b6-1.lbn25.noarch
Provides an inline lightbox component showing the images contained in the article. The following features for raptus.article are provided by this package: Components ---------- * Lightbox (Lightbox of the images contained in the article) * Lightbox teaser (Lightbox of the images contained in the article displayed above the columns)
RPMPackage raptus.article.images-2.0b5-1.lbn25.noarch
raptus.article.images provides support for multiple images per article. The following features for raptus.article are provided by this package: Content ------- * Image - add your images in a article.
RPMPackage raptus.article.hidecolumns-2.0b5-2.lbn25.noarch
Articles get the option to hide the left or the right column or both. The following features for raptus.article are provided by this package: Fields ------ * Option to hide the portlet columns
RPMPackage raptus.article.gallery-2.0b11-1.lbn25.noarch
Provides basic gallery components. The following features for raptus.article are provided by this package: Components ---------- * Gallery left (Gallery of the images contained in the article on the left side) * Gallery right (Gallery of the images contained in the article on the right side) * Gallery columns (Gallery of the images contained in the article arranged in columns)
RPMPackage raptus.article.form-2.0b6-1.lbn25.noarch
Provides support for PloneFormGen The following features for raptus.article are provided by this package: Content ------- * Form Folder - PloneFormGen - add your forms in an article. Components ---------- * Forms (List of forms contained in the article)
RPMPackage raptus.article.flash-2.0b4-2.lbn25.noarch
Provides support for flash movies The following features for raptus.article are provided by this package: Content ------- * Flash - add your flash files in an article. Components ---------- * Flash (displays flash files contained in the article over the whole width) * Flash left (displays flash files contained in the article on the left side) * Flash right (displays flash files contained in the article on the right side) * Flash teaser (displays flash files contained in the article over the whole width and displayed above t
RPMPackage raptus.article.files-2.0b6-1.lbn25.noarch
Provides support for adding attachments to articles. The following features for raptus.article are provided by this package: Content ------- * File - add files in an article. Components ---------- * Attachments (List of files contained in the article)
RPMPackage raptus.article.fader-2.0b5-2.lbn25.noarch
Provides a component which continually fades in and out the contained articles. The following features for raptus.article are provided by this package: Components ---------- * Content fader (continually fades in and out the contained articles) * Content fader teaser (continually fades in and out the contained articles and is displayed above the columns)
RPMPackage raptus.article.contentflow-2.0b4-2.lbn25.noarch
The following features for raptus.article are provided by this package: Components ---------- * Content flow (showing the contained articles like in iTunes) * Content flow teaser (showing the contained articles like in iTunes and is displayed above the columns)
RPMPackage raptus.article.contentfader-2.0b6-2.lbn25.noarch
Provides a component which continually fades in and out the contained articles.
RPMPackage raptus.article.additionalwysiwyg-2.0b7-1.lbn25.noarch
Extends the article by a second WYSIWYG text field to make it possible to split your text into two parts and display it for example above and below another component. The following features for raptus.article are provided by this package: Fields ------ * Additional WYSIWYG text field for the articles. Components ---------- * Additional text (displays your text above an image or a video) * Additional text left (displays your text in a separate column on the left) * Additional text right (displays your text in a separate column on the right)
RPMPackage python-raptus-2.0b12-1.lbn25.noarch
 
RPMPackage python-memcached-1.54-6.lbn25.noarch
This software is a 100% Python interface to the memcached memory cache daemon. It is the client side software which allows storing values in one or more, possibly remote, memcached servers. Search google for memcached for more information.
RPMPackage plone.scale-2.1-2.lbn25.noarch
This package contains image scaling logic for use in Zope environments. It supports Zope 2, grok and other systems build on using the Zope ToolKit (ZTK). Several design goals were used when writing this package: image scaling to any width, height, width&height should be supported using both up-scaling and down-scaling. Scaling parameters should never be fixed in code. This allows designers to use any image scale they want without having to modify python code. the result of scaling will be an image along with its new size, not a HTML or XHTML tag. We already have excellent tools to generate tags in the form of Zope Pagetemplates, Genshi and other template languages that are much better suited for this purpose. In addition several implementation goals were defined: image scaling must happen on demand instead of up-front. This reduces initial save time and prevents unnecessary scalings from being generated. image scaling parameters should not be part of the generated URL. Since the number of parameters can change and new parameters may be added in the future this would create overly complex URLs and URL parsing. no HTML rewriting (such as done by repoze.bitblt) should be required. it should be possibly to develop an external storage system which stores scaled images externally and returns a URL which bypasses the application server. This should be configurable via just a filesystem path & base URL. minimum number of external dependencies, allowing this package to be used in many environments. testable without requiring zope.testing. Running setup.py test should be sufficient. URLs for scaled images should have an extension which reflects their MIME type. This is facilitates cache (and other front-end services) configuration.
RPMPackage plone.registry-1.1.2-1.lbn25.noarch
This package provides debconf-like (or about:config-like) settings registries for Zope applications. A ``registry``, with a dict-like API, is used to get and set values stored in ``records``. Each record contains the actual value, as well as a ``field`` that describes the record in more detail. At a minimum, the field contains information about the type of value allowed, as well as a short title describing the record's purpose. See the following doctests for more details: * ``registry.rst``, which demonstrates how registries and records work * ``events.rst``, which shows the events that are fired from the registry * ``field.rst``, which describes the behaviour of persistent fields
RPMPackage plone.recipe.zope2zeoserver-1.4-3.lbn25.noarch
This recipe creates and configures a Zope 2 ZEO server in parts. It also installs a control script, which is like zeoctl, in the bin/ directory. The name of the control script is the the name of the part in buildout. You can use it with a part like this:: [zeoserver] recipe = plone.recipe.zope2zeoserver zope2-location = /path/to/zope2/install zeo-address = 8100 Options ------- zope2-location The path where Zope 2 is installed. If you are also using the plone.recipe.zope2install recipe, and you have that configured as a part called 'zope2' prior to the zope2zeoserver part, you can use ${zope2:location} for this parameter. You must ensure the zope2zeoserver part is run *after* the zope2install one. zeopack The path to the zeopack.py backup script. A wrapper for this will be generated in bin/zeopack, which sets up the appropriate environment to run this. Defaults to "${zope2-location}/utilities/ZODBTools/zeopack.py". Set this option to an empty value if you do not want this script to be generated. repozo The path to the repozo.py backup script. A wrapper for this will be generated in bin/repozo, which sets up the appropriate environment for running this. Defaults to "${zope2-location}/utilities/ZODBTools/repozo.py". Set this to an empty value if you do not want this script to be generated. zeo-conf A relative or absolute path to a zeo.conf file. If this is not given, a zeo.conf will be generated based on the the options below. The following options all affect the generated zope.conf. zeo-address Give a port for the ZEO server (either specify the port number only (with 'localhost' as default) or you use the format ``host:port``). Defaults to 8100. effective-user The name of the effective user for the ZEO process. Defaults to not setting an effective user. invalidation-queue-size The invalidation-queue-size used for the ZEO server. Defaults to 100. zeo-log The filename of the ZEO log file. Defaults to var/log/${partname}.log zeo-log-format Format of logfile entries. Defaults to %(asctime)s %(message)s zeo-log-custom A custom section for the eventlog, to be able to use another event logger than `logfile`. `zeo-log` is still used to set the logfile value in the runner section. storage-number The number used to identify a storage. file-storage The filename where the ZODB data file will be stored. Defaults to var/filestorage/Data.fs. blob-storage The folder where the ZODB blob data files will be stored. socket-name The filename where ZEO will write its socket file. Defaults to var/zeo.zdsock. authentication-database The filename for a authentication database. Only accounts listed in this database will be allowed to access the ZEO server. The format of the database file is:: realm <realm> <username>:<hash> Where the hash is generated via:: import sha string = "%s:%s:%s" % (username, realm, password) sha.new(string).hexdigest() authentication-realm The authentication realm. Defaults to 'ZEO' pack-days Specify of days for the zeopack script to retain of history. Defaults to one day. pack-user If the ZEO server uses authentication, this is the username used by the zeopack script to connect to the ZEO server. pack-password If the ZEO server uses authentication, this is the password used by the zeopack script to connect to the ZEO server. zeo-conf-additional Give additional lines to zeo.conf. Make sure you indent any lines after the one with the parameter. monitor-address The address at which the monitor server should listen. The monitor server provides server statistics in a simple text format. relative-paths Set this to `true` to make the generated scripts use relative paths. You can also enable this in the `[buildout]` section.