You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage collective.blueprint.dancing-0.1-1.lbn25.noarch
collective.dancing blueprints for collective.transmogrifier pipelines
RPMPackage collective.blueprint.base-1.0-1.lbn25.noarch
collective.blueprint.base Provides transmogrifier blueprint base classes and several useful blueprints... contents:: Table of Contents.. *doctest*Blueprint Base Classes The collective.blueprint.base package provides base classes for clear and easy transmogrifier blueprints.Changing Keys For blueprints that add or change keys in items, it can be very useful to make the keys used by the ...
RPMPackage collective.behavior.localregistry-1.0b2-1.lbn25.noarch
Dexterity behavior to add a local plone.app.registry for content types, it adds a local component with a layered proxy registry.
RPMPackage collective.behavior.localdiazo-1.0b3-1.lbn25.noarch
Dexterity behavior to enable a local Diazo theme. This package aims to make easier the creation of microsites on big web sites.
RPMPackage collective.beaker-1.0b3-3.lbn25.noarch
This package provides a means to configure the Beaker session management and caching framework for use within a Zope 2 (and Plone) environment. Ordinarily, Beaker is configured using WSGI middleware. However, Zope 2 does not (yet) run WSGI by default (unless you use repoze.zope2). This package provides an alternative configuration syntax, based in zope.conf.
RPMPackage collective.azipfele-1.1.1-1.lbn25.noarch
This is a basic module aiming to create ZIP files asynchronous. Even if it has some basic built in data-extractors, it is not meant as a out-of-the-box package, but for integrators and addon-product authors. Creating ZIP files in a request-response cycle may take a lot of time. With this package a zip job info is queued into a AMQP-Server (such as RabbitMQ). The ZIP file is created in a worker instance. After the file was created an event is fired. With it i.e. an e-mail notification can be send out. The state of the creation (pending, processing, finished) and the timestamps (queued, started, finished) are shared between worker and instance. The worker instance gets a jobinfo (dict) with global key settings (dict) and a list of fileinfos (list of dicts). Each fileinfo has at least a valid UUID of an content item. For each fileinfo in the list one file will be created. It adapts the content with the given UUID with collective.azipfele.interfaces import IZipContentExtractor using ZCA. If fileinfo contains an extractor (string) it uses a named adapter. The IZipContentExtractor takes on call the fileinfo and gloabl settings. it is expected to return a tuple of filename and the data to be stored in the zip with the filename. The returned filename can be a relative path as well.
RPMPackage collective.autorestart-0.2.0-3.lbn25.noarch
Automatically reload changed Python files - putting agility back to Plone development. collective.autorestart monitors Python .py files for changes and triggers a reload when you edit the files. This way you don't need to restart Plone server between your code edit runs. collective.autorestart uses plone.reload package to perform the actual code replacement. File system is monitored using inotify interface which is only available for Linux. The future versions will support other operating systems as long as somebody contributes the file system monitoring code or gives the author a new computer running operating system X. Features * Recursively detect changes in ZCML and Python files which are known to Zope * Automatically trigger reload when files are changed (saved) * Audio playback depending on whether the restart succeed or failed - you can go back to your files and you don't need to watch the terminal
RPMPackage collective.autopermission-1.0b2-1.lbn25.noarch
This package registers an event handler that initialises permissions on the fly. To use it, simply include its ZCML: <include package="collective.autopermission" /> Then, you can use the <permission /> ZCML statement to define a new type of permission, without also needing to make the permission "spring into existence" via ClassSecurityInfo or similar.
RPMPackage collective.amberjack.portlet-1.1-2.lbn25.noarch
collective.amberjack.portlet This package provides portlet for collective.amberjack package. Set up environment This package allows you to create portlets that contain tours. You can select the tours that can be display and choosen by an user on these portlet. So this package allows you to create sets of tours on Plone site.
RPMPackage collective.amberjack.plonetour-1.1-2.lbn25.noarch
Introduction This package allows you to create tours on your site, based on collective.amberjack.core. This package contains the first released tours: * Add and publish a Folder * Add and publish a Page * Add and publish a News Item * Add and publish an Event * Format a page using the visual editor * Create internal links * Create external links * Upload an image * Insert image on a page * Upload and link to a File * Using the Contents tab * Using the Display menu Others will be released soon. Add and publish a Folder This tutorial shows you how to create a new folder and then publish it. At the end of tour you can see a public folder in your Home. Add and publish a Page In this tutorial you learn how create a new page and then publish it. At the end of tour you'll create a new page and publish it on your Plone-powered website. This tutorial uses the folder that you created in a previous tour ("Add and publish a Folder"). Add and publish a News Item In this tutorial you learn how create a new news item and then publish it. At the end of tour you can see a public news item in your Home. This tutorial uses the folder that you created in one of previous tutorials ("Add and publish a Folder"). Add and publish an Event In this tutorial you learn how create a new event and then publish it. At the end of tour you can see a public event in your Home. This tutorial uses the folder that you created in one of previous tutorials ("Add and publish a Folder"). Format a page using the visual editor In this tutorial you will revisit a page that you created and learn how to format content on the page. This tutorial uses the folder and the page that you created in previous tutorials ("Add and publish a Folder" and "Add and publish a Page"). You will learn how to to apply bold, italics, text alignment, and paragraph styles to the page. Create internal links In this tour you learn how insert hyperlinks into a page. You will revisit a page that you created in the previous tutorial "Add and publish a Page". You learn how browse the content of your site and how create a hyperlink to any page, news item, event, image, file or other content type within your Plone site. Create external links In this tutorial you learn how to create link to other webpages, documents or resources online. This tutorial uses the Page that you created in previous tutorials "Add and publish a Page". You learn how find the external link icon and how make a preview, that lets you confirm that you have the correct webpage. Upload an image This tour shows how add a new image to folder that you created in one of previous tutorials ("Add and publish a Folder"). You will browse the content of your site and find the image file you want to place in Plone. Insert image on a page In this tutorial you learn how insert image into a page. You should have at least one image already from a previous tutorial "Upload an image". You will browse to the location of an image you would like to insert and choose Left alignment and a Size or change the 'alt' text for the image. Upload and link to a File In this tutorial you learn how upload to your site binary file such as a PDF, DOC, XLS, PPT, RTF or other file type and how create a link to the file to allow a site visitor to download the file. Using the Contents tab In this tutorial you learn how take a look at the Contents tab, that lets you browse the filesystem of your website and perform administrative tasks. The items you have been creating for previous tutorials will listed in the Contents view. You learn how change the order of contents within a folder, how make copies of a content item and how cut-and-paste. Using the Display menu In this tutorial you learn how change the way that the folders contained items will appear on the screen, using the Display drop-down menu. You will see the Summary view, Tabular View and Select default page.
RPMPackage collective.amberjack.core-1.1-2.lbn25.noarch
How to create new tour First of all you need to define the tour. Starting version 1.1 we are using configuration based style. A tour is a .cfg file. It has an amberjack main section which has two options: title and steps - this is where you define tour steps: [amberjack] steps = my_step1 my_step2 title = My first amberjack tour there are also available two blueprints: 1. Step a step section is defined by collective.amberjack.blueprints.step and has several options: * title * text * url - step url definition * xpath - xpath selector * xcontent - xcontent selector * microsteps - microsteps sections * validators - tales expression validation it looks like that: [my_step1] blueprint = collective.amberjack.blueprints.step title = This is my first Step text = You should now know how to create a step section url = /mystep validators = python: context.isFolderish() xpath = '' xcontent = '' microsteps = microstep_1 microstep_2 2. Microstep a microstep section is defined by collective.amberjack.blueprints.microsteps and it has several options: * idstep * text * description * selector it looks like that: [microstep_1] blueprint = collective.amberjack.blueprints.microstep idstep = menu_state text = This is my dummy microstep description = Now you should now how to define microsteps selector = #insert Tour registration Finally you have to register it. The only acceptable format is an archive (zip or tar) which contains one or multiple .cfg files (tours) Using zcml: <configure xmlns:collective.amberjack="http://namespaces.plone.org/collective.amberjack.core"> <collective.amberjack:tour tourlocation="mytourpackage.zip" /> </configure>
RPMPackage repoze.zope2-1.0.3-5.lbn25.noarch
repoze.zope2 is a decomposition of the Zope 2 appserver publication machinery (ZPublisher) into a WSGI application component. It relies on separately-distributed middleware pieces to perform some of the features previously handled by ZPublisher and other parts of Zope 2.
RPMPackage repoze.xmliter-0.6-1.lbn25.noarch
Wrapper for ``lxml`` trees which serializes to string upon iteration.
RPMPackage repoze.who-2.3-1.lbn25.noarch
``repoze.who`` is an identification and authentication framework for arbitrary WSGI applications. It acts as WSGI middleware. ``repoze.who`` is inspired by Zope 2's Pluggable Authentication Service (PAS) (but ``repoze.who`` is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application. It attemtps to reuse implementations from ``paste.auth`` for some of its functionality.
RPMPackage repoze.vhm-0.14-1.lbn25.noarch
This package provides middleware and utilities for doing virtual hosting within a WSGI/Repoze environment. It is particularly useful within a 'repoze.zope2' environment, where it may be used as an alternative to the classic "VirtualHostMonster":http://www.zope.org/Members/4am/SiteAccess2/info method of doing virtual hosting.
RPMPackage repoze.tm2-2.1-2.lbn25.noarch
Middleware which uses the ZODB transaction manager to wrap a call to its pipeline children inside a transaction.
RPMPackage repoze.sphinx.autointerface-0.8-2.lbn25.noarch
This package defines an extension for the Sphinx documentation system. The extension allows generation of API documentation by introspection of zope.interface instances in code.
RPMPackage repoze.retry-1.4-2.lbn25.noarch
WSGI Middleware which intercepts a ZODB conflict error and retries the WSGI request a configurable number of times.
RPMPackage repoze.obob-0.4-5.lbn25.noarch
Zope-like publisher as WSGI application
RPMPackage repoze.lru-0.6-4.lbn25.noarch
repoze.lru is a LRU (least recently used) cache implementation. Keys and values that are not used frequently will be evicted from the cache faster than keys and values that are used frequently. It works under Python 2.5, Python 2.6, Python 2.7, and Python 3.2.
 
Distributions
To see exactly what is included in BastionLinux™, visit our online RPMDistro Builder.
Buy Now
Bastion CD
Subscribe Now
and get BastionLinux™ ...
Sponsored Links