You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage repoze.errorlog-1.1-1.lbn25.noarch
This package implements a WSGI middleware filter which intercepts exceptions and writes them to a Python logging module channel (or the wsgi.errors filehandle, if no channel is configured). It also allows the browsing of limited exception history via a browser UI.
RPMPackage python2-zodbpickle-1.0.1-1.lbn25.x86_64
This package presents a uniform pickling interface for ZODB: - Under Python2, this package forks both Python 2.7's pickle and cPickle modules, adding support for the protocol 3 opcodes. It also provides a new subclass of bytes, zodbpickle.binary, which Python2 applications can use to pickle binary values such that they will be unpickled as bytes under Py3k. - Under Py3k, this package forks the pickle module (and the supporting C extension) from Python 3.2, Python 3.3, and Python 3.4. The fork adds support for the noload operations used by ZODB.
RPMPackage python2-persistent-4.2.4.2-7.lbn25.x86_64
This package contains a generic persistence implementation for Python. It forms the core protocol for making objects interact transparently with a database such as python-ZODB3.
RPMPackage python-repoze-2.3-1.lbn25.noarch
Python moduel for repoze
RPMPackage python-ZODB-5.4.0-1.lbn25.noarch
The ZODB package provides a set of tools for using the Zope Object Database (ZODB).
RPMPackage python-ZEO-5.2.0-1.lbn25.noarch
ZEO is a client-server system for sharing a single storage among many clients. When you use ZEO, the storage is opened in the ZEO server process. Client programs connect to this process using a ZEO ClientStorage. ZEO provides a consistent view of the database to all clients. The ZEO client and server communicate using a custom RPC protocol layered on top of TCP.
RPMPackage python-BTrees-4.5.0-1.lbn25.x86_64
This package contains a set of persistent object containers built around a modified BTree data structure. The trees are optimized for use inside ZODB's "optimistic concurrency" paradigm, and include explicit resolution of conflicts detected by that mechanism.
RPMPackage Products.PlacelessTranslationService-2.0.7-1.lbn25.noarch
What is PlacelessTranslationService? ------------------------------------ PTS is a way of internationalizing (i18n'ing) and localizing (l10n'ing) software for Zope 2. It's based on the files supported by the GNU gettext set of utilities. A good source of information and background reading is the gettext documentation: http://www.gnu.org/software/gettext/manual/ Using PlacelessTranslationService --------------------------------- PTS is used in the following steps: 1. i18n your software 2. Prepare a translation template 3. Prepare translations of the template 4. Install translations Each of these is explained below. 1. Internationalizing Your Software A good overview of this can be found at: http://www.upfrontsystems.co.za/Members/jean/mysite-i18n 2. Preparing a Translation Template A translation template is an empty Portable Object file as defined by the gettext standard with a special header block. The PO format is described in detail here: http://www.gnu.org/software/gettext/manual/html_node/gettext_9.html#SEC9 The header block is fairly self explanatory and can be seen in the sample.pot file included in this directory. All phrases in capitals, the language code, language name and (optionally) the content type and preferred encodings should be replaced with their correct values. There are several ways to prepare a PO template: -- By hand: This can be done by copying the blank.pot included in this directory, replacing the sample values as described above and and then manually adding msgid and empty msgstr pairs for each of the msgid's used in your software. -- Using i18ndude: i18ndude is a tool that is useful when all your software is in the form of ZPT's that are stored in files on the filesystem. It can be downloaded from: http://plone.org/products/i18ndude 3. Prepare Translations of the Template Preferably, find a translation company that can handle the gettext standards and send them your .pot file. They should send back .po files for the languages you require. If you're doing it yourself, copy the .pot file to a file on the name of the language you're translating to and with a .po extension. Then go through that file and fill in the msgstr sections. Finally, update all the metadata fields at the top of the file so they are correct for the translation you have just completed. At this point, you should have a .pot file and a collection of .po files. 4. Install Translations PTS will look in folders called 'i18n' for .po files to use as translations. These 'i18n' folders will be searched if they are in the INSTANCE_HOME or in the directories of any of the Products you have installed. Copy your .po files to a 'i18n' folder of your choice in one of these locations. Once that's done, restart Zope.
RPMPackage zope.contenttype-4.2.0-1.lbn25.noarch
A utility module for content-type handling.
RPMPackage zope.contentprovider-4.0.0-1.lbn25.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.componentvocabulary-2.0.0-1.lbn25.noarch
This package contains various vocabularies.
RPMPackage zope.catalog-3.8.2-2.lbn25.noarch
Catalogs provide management of collections of related indexes with a basic search algorithm.
RPMPackage zope.cachedescriptors-4.2.0-1.lbn25.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-4.1.0-1.lbn25.noarch
This package is at present not reusable without depending on a large chunk of the Zope Toolkit and its assumptions. It is maintained by the Zope Toolkit project. This package provides an implementation of browser resources. It also provides directives for defining those resources using ZCML. Resources are static files and directories that are served to the browser directly from the filesystem. The most common example are images, CSS style sheets, or JavaScript files. Resources are be registered under a symbolic name and can later be referred to by that name, so their usage is independent from their physical location. You can register a single file with the <browser:resource> directive, and a whole directory with the <browser:resourceDirectory> directive, for example <browser:resource file=”/path/to/static.file” name=”myfile” /> <browser:resourceDirectory directory=”/path/to/images” name=”main-images” /> This causes a named adapter to be registered that adapts the request to zope.interface.Interface (XXX why do we not use an explicit interface?), so to later retrieve a resource, use zope.component.getAdapter(request, name=’myfile’). There are two ways to traverse to a resource, with the ‘empty’ view on a site, e. g. http://localhost/@@/myfile (This is declared by zope.browserresource) with the ++resource++ namespace, e. g. http://localhost/++resource++myfile (This is declared by zope.traversing.namespace) In case of resource-directories traversal simply continues through its contents, e. g. http://localhost/@@/main-images/subdir/sample.jpg Rather than putting together the URL to a resource manually, you should use zope.traversing.browser.interfaces.IAbsoluteURL to get the URL, or for a shorthand, call the resource object. This has an additional benefit: If you want to serve resources from a different URL, for example because you want to use a web server specialized in serving static files instead of the appserver, you can register an IAbsoluteURL adapter for the site under the name ‘resource’ that will be used to compute the base URLs for resources. For example, if you register ‘http://static.example.com/’ as the base ‘resource’ URL, the resources from the above example would yield the following absolute URLs: http://static.example.com/@@/myfile and http://static.example.com/@@/main-images
RPMPackage zope.browserpage-4.1.0-2.lbn25.noarch
This package is at present not reusable without depending on a large chunk of the Zope Toolkit and its assumptions. It is maintained by the Zope Toolkit project. This package provides ZCML directives for configuring browser views. More specifically it defines the following ZCML directives: browser:page browser:pages browser:view These directives also support menu item registration for pages, when zope.browsermenu package is installed. Otherwise, they simply ignore the menu attribute.
RPMPackage zope.browsermenu-4.3.0-1.lbn25.noarch
This package provides shared browser components for the Zope Toolkit.
RPMPackage zope.browser-2.1.0-1.lbn25.noarch
This package provides shared browser components for the Zope Toolkit.
RPMPackage zope.broken-3.6.0-2.lbn25.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.authentication-3.7.1-2.lbn25.noarch
Definition of authentication basics for the Zope Framework
RPMPackage zope.applicationcontrol-3.5.5-2.lbn25.noarch
Zope applicationcontrol
 
Distributions
To see exactly what is included in BastionLinux™, visit our online RPMDistro Builder.
Buy Now
Bastion CD
Subscribe Now
and get BastionLinux™ ...
Sponsored Links