-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
collective.z3cform.datagridfield-0.11-2.lbn13.noarch
Version of DataGridField for use with Dexterity / z3c.form
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
collective.z3cform.datetimewidget-1.2.6-1.lbn13.noarch
z3c.form date and datetime widgets
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
collective.zopeedit-1.0.0-2.lbn13.noarch
ZopeEdit : External Editor Client
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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).
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
dm.profile-1.0-2.lbn13.noarch
Easier readable profile statistics -- especially for caller and callee analysis
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
dm.reuse-1.1-3.lbn13.noarch
Support for object reuse with slight modifications
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
