Search results

collective.autopermission-1.0b2-1.lbn13.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.

collective.autopermission-1.0b2-1.lbn19.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.

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.

collective.autorestart-0.2.0-3.lbn13.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

collective.autorestart-0.2.0-3.lbn19.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

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

collective.azipfele-1.1.1-1.lbn19.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.

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.

collective.beaker-1.0b3dev_r239026-1.lbn13.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.

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.