-
five.grok-1.3.2-2.lbn25.noarch
five.grok is a development layer for Zope 2, based on Grok framework concepts.
The development techniques are similar to the ones used with Grok framework.
It is based on grokcore namespace packages that were factored out of Grok framework.
Implemented features
Coming from Grok, the following components are available to Zope 2 developers:
* Zope 3 Component (Adapter, Global utilities, Subscribers),
* Permissions,
* Views and Viewlets,
* Skins and resources directories,
* Page Templates (using the Zope 2 Page Templates),
* Formlib forms,
* Local sites and local utilities,
* Annotations.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
five.grok-1.3.2-2.lbn25.noarch
five.grok is a development layer for Zope 2, based on Grok framework concepts.
The development techniques are similar to the ones used with Grok framework.
It is based on grokcore namespace packages that were factored out of Grok framework.
Implemented features
Coming from Grok, the following components are available to Zope 2 developers:
* Zope 3 Component (Adapter, Global utilities, Subscribers),
* Permissions,
* Views and Viewlets,
* Skins and resources directories,
* Page Templates (using the Zope 2 Page Templates),
* Formlib forms,
* Local sites and local utilities,
* Annotations.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
five.intid-1.0.3-2.lbn13.noarch
s package makes it possible to use zope.app.intid (and consequentually
other packages that rely on it such as zope.app.keyreference) in a
Zope2 environment.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
five.intid-1.1.2-1.lbn25.noarch
s package makes it possible to use zope.app.intid (and consequentually
other packages that rely on it such as zope.app.keyreference) in a
Zope2 environment.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
five.intid-1.1.2-1.lbn25.noarch
s package makes it possible to use zope.app.intid (and consequentually
other packages that rely on it such as zope.app.keyreference) in a
Zope2 environment.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
five.localsitemanager-2.0.5-2.lbn13.noarch
five.localsitemanager attempts to provide a local site manager implementation
that is as close to Zope 3's implementation as possible. Some reservations
that do not conflict with Zope 3 have been made to ease the path with CMF.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
five.localsitemanager-2.0.6-1.lbn25.noarch
five.localsitemanager attempts to provide a local site manager implementation
that is as close to Zope 3's implementation as possible. Some reservations
that do not conflict with Zope 3 have been made to ease the path with CMF.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
five.localsitemanager-2.0.6-1.lbn25.noarch
five.localsitemanager attempts to provide a local site manager implementation
that is as close to Zope 3's implementation as possible. Some reservations
that do not conflict with Zope 3 have been made to ease the path with CMF.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
five.pt-2.2.1-2.lbn13.noarch
This package brings the Chameleon template engine to the Zope 2 platform. Five is
supported.
It works using monkey-patching onto the existing API (specifically, the TALInterpreter
and PageTemplate classes). In simple terms, what the patching does is to replace the
TAL interpreter class and make sure that the so-called "cooking" routine uses the
Chameleon parser and compiler instead of the zope.* reference implementation.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
five.pt-2.2.4-1.lbn19.noarch
This package brings the Chameleon template engine to the Zope 2 platform. Five is
supported.
It works using monkey-patching onto the existing API (specifically, the TALInterpreter
and PageTemplate classes). In simple terms, what the patching does is to replace the
TAL interpreter class and make sure that the so-called "cooking" routine uses the
Chameleon parser and compiler instead of the zope.* reference implementation.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
