-
zope-z3c.jbot-0.7.2-1.lbn25.noarch
Overview
The z3c.jbot (or "Just a bunch of templates") package allows easy customization
of existing templates and images. It works on Zope 2 and Zope 3.
The Chameleon rendering engine is supported [1].
Use of this package adds a small (2-3 ms per request on Plone) to the total
application response time.
[1] To enable Chameleon on Zope 2, use the five.pt package (CMF-apps like
Plone should use cmf.pt which adds full support).
Usage
To override a particular file, first determine its canonical filename. It's
defined as the path relative to the package within which the file is located;
directory separators are replaced with dots.
Example:
Suppose you want to override: /plone/app/layout/viewlets/logo.pt
You would use the filename: plone.app.layout.viewlets.logo.pt
Simply drop the file in a directory and register that directory for use with jbot
using a ZCML-directive:
<include package="z3c.jbot" file="meta.zcml" />
<browser:jbot
directory="<path>"
layer="<layer>" />
Templates in views, viewlets and portlets
Any template that is defined as a class-attribute can be overriden using
jbot, e.g. those used in views, viewlets and portlets. The template overrides
may be registered for any request layer or only a specific layer.
CMF objects
Any skin-object (e.g. images, templates) on the file system (directory views)
can be overridden.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-z3c.objpath-1.1-1.lbn25.noarch
This package contains two things:
* the z3c.objpath.interfaces.IObjectPath interface.
* some helper functions to construct (relative) object paths, in z3c.objpath.path.
The idea is that a particular application can implement a utility that fulfills the
IObjectPath interface, so that it is possible to construct paths to objects in a uniform
way. The implementation may be done with zope.traversing, but in some cases you want
application-specific object paths. In this case, the functions in z3c.objpath.path might
be useful.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-z3c.pt-3.1.0-1.lbn25.noarch
This is a fast implementation of the ZPT template engine for Zope 3 which uses
Chameleon to compile templates to byte-code.
The package provides application support equivalent to zope.app.pagetemplate.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-z3c.recipe.compattest-1.0-1.lbn25.noarch
This buildout recipe generates a list of packages to test and a test runner that runs each
package’s tests (isolated from any other tests). This is useful to check that the changes
made while developing a package do not break any packages that are using this package.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-z3c.widgets-1.0c1-4.lbn25.noarch
Zope 3 widget base module hierarchy
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-z3c.widgets.flashupload-1.0c1-4.lbn25.noarch
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-z3c.zcmlhook-1.0b1-2.lbn25.noarch
z3c.zcmlhook
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zExceptions-2.13.0-2.lbn25.noarch
zExceptions contains common exceptions used in Zope2.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zLOG-3.0-1.lbn25.noarch
This package provides a general logging facility that, at this point, is just a small shim
over Python’s logging module. Therefore, unless you need to support a legacy package from
the Zope 2 world, you’re probably better off using Python’s logging module.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope-zc-2.0.0-3.lbn25.noarch
Zope Corp base module hierarchy
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
