Products.ResourceRegistries (2.0.5)

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

Usage

The CSSRegistry and JSRegistry is configured through the ZMI. it can be found in the ZMI of your plonesite as portal_css and portal_javascript.

Add links to stylesheets that exist in your skins paths, by ids; like plone.css, ploneCustom.css etc.

Linked stylesheets take some parameters:

id

The id mentioned above. the Zope id of the stylesheet to be used.

expression

A CMF expression to be evaluated to check if the stylesheet should be included in output or not.

media

The media for which the stylesheet should apply, normally empty or all. other possible values are screen, print etc.

rel

Link relation. defaults to stylesheet, and should almost always stay that way. For designating alternative stylesheets.

rendering

How to link the stylesheet from the html page:

• import - the default. normal css import
• link - works better for old browsers an alternate stylesheets
• inline - render the stylesheet inline instead of linking it externally. Use sparingly. Costs bandwidth, but is very useful for style that vary for example on a per-folder-basis, like those famous header graphics bars.

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. Many thanks to Jodok and the others that made this happen :)