Modified items

All recently modified items, latest first.

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.

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.

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.

five.globalrequest-1.0-2.lbn13.noarch: Zope 2 integration for zope.globalrequest

five.customerize-1.1-1.lbn13.noarch: TTW customization of template-based Zope 3 views

dm.reuse-1.1-3.lbn13.noarch: Support for object reuse with slight modifications

dm.profile-1.0-2.lbn13.noarch: Easier readable profile statistics -- especially for caller and callee analysis

dm.incrementalsearch-2.0-2.lbn13.x86_64: dm.incrementalsearch is an efficient low level search execution engine. Its primary purpose is to incrementally perform searches involving and, or and not queries over ZODB.BTrees. Incrementally means here that hits are determined one at a time: the first hit, then the second hit, then the third hit, etc. Therefore, the first few hits can be determined extremely fast. But even if all hits need to be determined, the incremental execution of subqueries can lead to speedups of several orders for some query types (especially those dominated by specific and queries). Queries involving large or subqueries are difficult to optimize in the standard way. But often they can be replaced by incremental filtering. With this technique, a subquery is removed from the original search, the modified search executed and the result filtered by the removed subquery. incrementalsearch supports incremental filtering and thereby can again gain serveral orders of speedup for otherwise difficult to treat query types. The primary concept is that of an ISearch (incremental search). This is conceptionally a sorted list, computed incrementally (or lazily). The elements of this list are the ISearch's hits. The ISearch's keytype determines the type of the list elements. Currently supported are OBJECT (comparable Python objects), INT (Python 32 bit integers) and LONG (Python 64 bit integers).

dataflake.ldapconnection-1.5-1.lbn13.noarch: This package provides an abstraction layer on top of python-ldap. It offers a connection object with simplified methods for inserting, modifying, searching and deleting records in the LDAP directory tree. Failover/redundancy can be achieved by supplying connection data for more than one LDAP server.

dataflake.cache-1.4-1.lbn13.noarch: This package provides a set of simple cache implementations for use in Python code. Its roots are in the internally-used SimpleCache module from Products.LDAPUserFolder.

collective.z3cform.datetimewidget-1.2.6-1.lbn13.noarch: z3c.form date and datetime widgets

collective.z3cform.datagridfield-demo-0.5-2.lbn13.noarch: This package provides the demo views for collective.z3cform.datagridfield. Examples of configurations are in the demo folder. Once you install this package, the demo views will be visible on your site. * http://localhost:8080/Plone/@@demo-collective.z3cform.datagrid

collective.z3cform.datagridfield-0.11-2.lbn13.noarch: Version of DataGridField for use with Dexterity / z3c.form

collective.z3cform.colorpicker-1.1-1.lbn13.noarch: collective.z3cform.colorpicker provides two different jQuery based widgets: Farbtastic, a simple color picker. jPicker, a jQuery Color Picker Plugin supporting transparency.

collective.xmltestreport-1.3.1-1.lbn13.noarch: This package provides an extension to the test runner to the one that ships with zope.testrunner, as well as a buildout recipe based on zc.recipe.testrunner to install a test script for this test runner. The test runner is identical to the one in zope.testrunner, but it is capable of writing test reports in the XML format output by JUnit/Ant. This allows the test results to be analysed by tools such as the Jenkins continuous integration server. The recipe accepts the same options as zc.recipe.testrunner, so look at its documentation for details. When buildout is run, you should have a script in bin/test and a directory parts/test. To run the tests, use the bin/test script. If you pass the --xml option, test reports will be written to parts/test/testreports directory: $ bin/test --xml -s my.package Use bin/test --help for a full list of options. If you are using Jenkins, you can now configure the build to publish JUnit test reports for <buildoutdir>/parts/test/testreports/*.xml.

collective.usernamelogger-1.2-2.lbn13.noarch: Log user names when using cookie authentication in Zope/Plone.

collective.uploadify-1.1-1.lbn13.noarch: Multifileupload for Plone using uploadify Usage After install, go to http://your-plone-site/@@upload


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