Search results

Products.Quills-remoteblogging-1.8.1-1.lbn19.noarch

Use your Blog with any Weblog Editor that supports the `MetaWeblog API`_. This feature requires the ``Products.MetaWeblogPASPlugin`` product to be installed into your Plone site. .. _MetaWeblog API: http://www.metaweblogapi.com/

Products.Quills-remoteblogging-1.8.1-1.lbn25.noarch

Use your Blog with any Weblog Editor that supports the `MetaWeblog API`_. This feature requires the ``Products.MetaWeblogPASPlugin`` product to be installed into your Plone site. .. _MetaWeblog API: http://www.metaweblogapi.com/

Products.QuotaFolder-0.1.1-2.lbn13.noarch

QuotaFolder is a folder-ish object that restricts the total number of objects, their total size and their individual maximum size. QuotaFolder takes subfolders (recursively) into account, so it should not be possible to escape the quota restrictions. The basic goal of QuotaFolder is not to put an absolute limit on ZODB usage - it is impossible to determine this. For example, each object may have several revisions in the ZODB, and some of the internal state of the object is stored in the ZODB that's not returned by get_size(). The goal is to limit the use of objects in general, to prevent people from offering large files or using up resources with enormous amounts of objects.

Products.QuotaFolder-0.1.1-2.lbn19.noarch

QuotaFolder is a folder-ish object that restricts the total number of objects, their total size and their individual maximum size. QuotaFolder takes subfolders (recursively) into account, so it should not be possible to escape the quota restrictions. The basic goal of QuotaFolder is not to put an absolute limit on ZODB usage - it is impossible to determine this. For example, each object may have several revisions in the ZODB, and some of the internal state of the object is stored in the ZODB that's not returned by get_size(). The goal is to limit the use of objects in general, to prevent people from offering large files or using up resources with enormous amounts of objects.

Products.QuotaFolder-0.1.1-2.lbn25.noarch

QuotaFolder is a folder-ish object that restricts the total number of objects, their total size and their individual maximum size. QuotaFolder takes subfolders (recursively) into account, so it should not be possible to escape the quota restrictions. The basic goal of QuotaFolder is not to put an absolute limit on ZODB usage - it is impossible to determine this. For example, each object may have several revisions in the ZODB, and some of the internal state of the object is stored in the ZODB that's not returned by get_size(). The goal is to limit the use of objects in general, to prevent people from offering large files or using up resources with enormous amounts of objects.

Products.rendezvous-1.4-6.lbn13.noarch

Products.rendezvous is a timeboard to select a rendez-vous when most people are available. You create a RendezVous content type where you select some days. For each date, you create 0 to several slots (for instance: 1pm, 2pm, morning, evening) and you publish your object. Then you send the url to all people you want to see at this rendezvous. Each member of the portal can participate to this rendezvous. The user checks the days and slots which for he or she is available.

Products.rendezvous-1.4.2-1.lbn25.noarch

Products.rendezvous is a timeboard to select a rendez-vous when most people are available. You create a RendezVous content type where you select some days. For each date, you create 0 to several slots (for instance: 1pm, 2pm, morning, evening) and you publish your object. Then you send the url to all people you want to see at this rendezvous. Each member of the portal can participate to this rendezvous. The user checks the days and slots which for he or she is available.

Products.rendezvous-1.4.2-1.lbn25.noarch

Products.rendezvous is a timeboard to select a rendez-vous when most people are available. You create a RendezVous content type where you select some days. For each date, you create 0 to several slots (for instance: 1pm, 2pm, morning, evening) and you publish your object. Then you send the url to all people you want to see at this rendezvous. Each member of the portal can participate to this rendezvous. The user checks the days and slots which for he or she is available.

Products.ResourceRegistries-2.2.10-1.lbn13.noarch

A registry for linked Stylesheet files and Javascripts. This registry is mainly aimed at solving the following usecases: - Enable product authors to register stylesheets with their product installers without having to resort to override either header.pt or ploneCustom.css creating potential conflicts with other products. - Enable more componentialization of the stylesheets provided with Plone (and other products) without having to increase the number of http requests for a Plone page. - Enable condition checking on stylesheets. Great for variable look-and-feel for groups/roles/folders/departments/content-types/etc - Enable inline dynamic stylesheets. For those style rules that should vary for each request. Mainly used for things like header-bar- backgroundimages, department colors etc. - Enable developers to activate/deactivate their styles in a simpler way - Enable compression to safe bandwidth and download time If several stylesheets listed directly after each other in the registry have the same parameters and expression, they will be concatenated into a larger, composite, stylesheet on rendering. - This can be useful for splitting stylesheets into smaller components for overrideing, while preserving cacheability and minimising the number of http-requests to Plone. This tool was started at the excellent SnowSprint 2005 - Organised by Telesis in the Austrian Alps. Thanks, Jodok! :)

Products.ResourceRegistries-2.2.13-1.lbn25.noarch

A registry for linked Stylesheet files and Javascripts. This registry is mainly aimed at solving the following usecases: - Enable product authors to register stylesheets with their product installers without having to resort to override either header.pt or ploneCustom.css creating potential conflicts with other products. - Enable more componentialization of the stylesheets provided with Plone (and other products) without having to increase the number of http requests for a Plone page. - Enable condition checking on stylesheets. Great for variable look-and-feel for groups/roles/folders/departments/content-types/etc - Enable inline dynamic stylesheets. For those style rules that should vary for each request. Mainly used for things like header-bar- backgroundimages, department colors etc. - Enable developers to activate/deactivate their styles in a simpler way - Enable compression to safe bandwidth and download time If several stylesheets listed directly after each other in the registry have the same parameters and expression, they will be concatenated into a larger, composite, stylesheet on rendering. - This can be useful for splitting stylesheets into smaller components for overrideing, while preserving cacheability and minimising the number of http-requests to Plone. This tool was started at the excellent SnowSprint 2005 - Organised by Telesis in the Austrian Alps. Thanks, Jodok! :)