You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage zope.contenttype-3.5.5-2.lbn13.noarch
zope.contenttype
RPMPackage zope.contentprovider-3.7.2-2.lbn13.noarch
This package provides a framework to develop componentized Web GUI applications. Instead of describing the content of a page using a single template or static system of templates and METAL macros, content provider objects are dynamically looked up based on the setup/configuration of the application.
RPMPackage zope.container-3.12.0-2.lbn13.x86_64
This package define interfaces of container components, and provides container implementations such as a BTreeContainer and OrderedContainer, as well as the base class used by zope.site.folder for the Folder implementation.
RPMPackage zope.configuration-3.8.1-2.lbn13.noarch
The zope configuration system provides an extensible system for supporting various kinds of configurations. It is based on the idea of configuration directives. Users of the configuration system provide configuration directives in some language that express configuration choices. The intent is that the language be pluggable. An XML language is provided by default.
RPMPackage zope.componentvocabulary-1.0.1-2.lbn13.noarch
This package contains various vocabularies.
RPMPackage zope.component-3.10.0-2.lbn13.noarch
Zope Component API
RPMPackage zope.catalog-3.8.2-2.lbn13.noarch
Catalogs provide management of collections of related indexes with a basic search algorithm.
RPMPackage zope.cachedescriptors-3.5.1-2.lbn13.noarch
Cached descriptors cache their output. They take into account instance attributes that they depend on, so when the instance attributes change, the descriptors will change the values they return. Cached descriptors cache their data in _v_ attributes, so they are also useful for managing the computation of volatile attributes for persistent objects. Persistent descriptors: property A simple computed property. See property.txt. method Idempotent method. The return values are cached based on method arguments and on any instance attributes that the methods are defined to depend on. **Note**, only a cache based on arguments has been implemented so far. See method.txt. Cached Properties ----------------- Cached properties are computed properties that cache their computed values. They take into account instance attributes that they depend on, so when the instance attributes change, the properties will change the values they return.
RPMPackage zope.browserresource-3.10.3-2.lbn13.noarch
Browser resources implementation for Zope.
RPMPackage zope.browserpage-3.12.2-2.lbn13.noarch
ZCML directives for configuring browser views for Zope.
RPMPackage zope.browsermenu-3.9.1-2.lbn13.noarch
Browser menu implementation for Zope 3.
RPMPackage zope.browser-1.3-2.lbn13.noarch
This package provides shared browser components for the Zope Toolkit.
RPMPackage zope.broken-3.6.0-2.lbn13.noarch
This package defines a marker interface, zope.broken.IBroken, used to identify objects which cannot be correctly loaded from the ZODB, typically because the class named in their pickle is not importable. The package exists as a dependency inversion, preventing packages which need to use this interface (e.g., zope.container) from inheriting the dependencies of zope.app.broken (where the interface used to be defined).
RPMPackage zope.bforest-1.2-2.lbn13.noarch
BForests are dictionary-like objects that use multiple BTrees for a backend and support rotation of the composite trees. This supports various implementations of timed member expirations, enabling caches and semi-persistent storage. A useful and simple subclass would be to promote a key-value pair to the first (newest) bucket whenever the key is accessed, for instance. It also is useful with disabling the rotation capability. Like btrees, bforests come in four flavors: Integer-Integer (IIBForest), Integer-Object (IOBForest), Object-Integer (OIBForest), and Object-Object (OOBForest). The examples here will deal with them in the abstract: we will create classes from the imaginary and representative BForest class, and generate keys from KeyGenerator and values from ValueGenerator. From the examples you should be able to extrapolate usage of all four types.
RPMPackage zope.authentication-3.7.1-2.lbn13.noarch
Definition of authentication basics for the Zope Framework
RPMPackage zope.applicationcontrol-3.5.5-2.lbn13.noarch
Zope applicationcontrol
RPMPackage zope.app.zptpage-3.5.1-2.lbn13.noarch
zope.app.zptpage
RPMPackage zope.app.zopeappgenerations-3.5.1-2.lbn13.noarch
zope.app.zopeappgenerations
RPMPackage zope.app.zcmlfiles-3.7.1-2.lbn13.noarch
Zope application server ZCML files
RPMPackage zope.app.zapi-3.5.0-2.lbn13.noarch
zope.app.zapi