plone

five.globalrequest-1.0-2.lbn13.noarch
Zope 2 integration for zope.globalrequest
Located in LBN / … / Plone and Zope / BastionLinux 13
five.globalrequest-1.0-3.lbn25.noarch
This package integrates zope.globalrequest with Zope 2. It is compatible with Zope 2.12 and later. In Zope 2.10, you can install ZPublisherEventsBackport to use it. The only thing you need to do to use this package is to load its configuration from your own ZCML file: <include package="five.globalrequest" /> You can now use zope.globalrequest as normal: from zope.globalrequest import getRequest request = getRequest() The request is set up when publication starts, when the IPubStart event is fired. It is cleared on one of the IPubEnd events: IPubSuccess or IPubFailure. If you have your own event handlers for either of these events, you should be aware that the event setup/clear could happen after/ before your own event handler is executed, since the order of execution for event handlers is not controllable.
Located in LBN / … / Plone and Zope / BastionLinux 19
five.globalrequest-1.0-3.lbn25.noarch
This package integrates zope.globalrequest with Zope 2. It is compatible with Zope 2.12 and later. In Zope 2.10, you can install ZPublisherEventsBackport to use it. The only thing you need to do to use this package is to load its configuration from your own ZCML file: <include package="five.globalrequest" /> You can now use zope.globalrequest as normal: from zope.globalrequest import getRequest request = getRequest() The request is set up when publication starts, when the IPubStart event is fired. It is cleared on one of the IPubEnd events: IPubSuccess or IPubFailure. If you have your own event handlers for either of these events, you should be aware that the event setup/clear could happen after/ before your own event handler is executed, since the order of execution for event handlers is not controllable.
Located in LBN / … / Plone and Zope / BastionLinux 25
five.grok-1.3.2-1.lbn13.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 13
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

« Previous 10 items Next 10 items » 1 ... 627 628 629 630 631 632 633 ... 4841

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.