You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage zope-z3c.pagelet-2.0.0a1-1.lbn13.noarch
Pagelets are Zope 3 UI components. In particular they allow the developer to specify content templates without worrying about the UI O-wrap. This package provides a very flexible base implementation that can be used to write view components which can be higly customized later in custom projects. This is needed if you have to write reusable components like those needed in a framework. Pagelets are BrowserPages made differently and can be used to replace them. What does this mean? We separate the python view code from the template implementation. And we also separate the template in at least two different templates - the content template and the layout template. This package uses z3c.template and offers an implementaton for this template pattern. Additionaly this package offers a pagelet directive wich can be used to register pagelets. Pagelets are views which can be called and support the update and render pattern. How do they work A pagelet returns the rendered content without layout in the render method and returns the layout code if we call it. See also z3c.template which shows how the template works. These samples will only show how the base implementation located in the z3c.pagelet.browser module get used. BrowserPagelet The base implementation called BrowserPagelet offers builtin __call__ and render methods which provide the different template lookups. Take a look at the BrowserPagelet class located in z3c.pagelet.browser and you can see that the render method returns a IContentTemplate and the __call__ method a ILayoutTemplate defined in the z3c.layout package.
RPMPackage zope-z3c.objpath-1.1-1.lbn13.noarch
This package contains two things: * the z3c.objpath.interfaces.IObjectPath interface. * some helper functions to construct (relative) object paths, in z3c.objpath.path. The idea is that a particular application can implement a utility that fulfills the IObjectPath interface, so that it is possible to construct paths to objects in a uniform way. The implementation may be done with zope.traversing, but in some cases you want application-specific object paths. In this case, the functions in z3c.objpath.path might be useful.
RPMPackage zope-z3c.macro-2.0.0a1-1.lbn13.noarch
This package provides an adapter and a TALES expression for a more explicit and more flexible macro handling using the adapter registry for macros.
RPMPackage zope-z3c.jbot-0.6.3-2.lbn13.noarch
Overview The z3c.jbot (or "Just a bunch of templates") package allows easy customization of existing templates and images. It works on Zope 2 and Zope 3. The Chameleon rendering engine is supported [1]. Use of this package adds a small (2-3 ms per request on Plone) to the total application response time. [1] To enable Chameleon on Zope 2, use the five.pt package (CMF-apps like Plone should use cmf.pt which adds full support). Usage To override a particular file, first determine its canonical filename. It's defined as the path relative to the package within which the file is located; directory separators are replaced with dots. Example: Suppose you want to override: /plone/app/layout/viewlets/logo.pt You would use the filename: plone.app.layout.viewlets.logo.pt Simply drop the file in a directory and register that directory for use with jbot using a ZCML-directive: <include package="z3c.jbot" file="meta.zcml" /> <browser:jbot directory="<path>" layer="<layer>" /> Templates in views, viewlets and portlets Any template that is defined as a class-attribute can be overriden using jbot, e.g. those used in views, viewlets and portlets. The template overrides may be registered for any request layer or only a specific layer. CMF objects Any skin-object (e.g. images, templates) on the file system (directory views) can be overridden.
RPMPackage zope-z3c.formwidget.query-0.10-1.lbn13.noarch
This package implements a widget that lets users enter a query and select from the results.
RPMPackage zope-z3c.formui-3.0.0a2-1.lbn13.noarch
This package provides a set of default layouts for the z3c.form framework. In particular it provides a DIV-based and a TABLE-based layout. The developer can use either layout by inheriting from a different base layer. The package also has some support for layout/pagelet templates.
RPMPackage zope-z3c.form-3.1.0-1.lbn13.noarch
This package provides an implementation for HTML forms and widgets. The goal is to provide a simple API but with the ability to easily customize any data or steps.
RPMPackage zope-z3c.deadlockdebugger-0.2-3.lbn13.noarch
The z3c.deadlockdebugger package provides a thread debugger. Usage: /debug_threads (requires the 'cmf.ManagePortal' permission) Caution: You should not use this package in production.
RPMPackage zope-z3c.coverage-1.2.0-2.lbn13.noarch
z3c.coverage
RPMPackage zope-z3c.checkversions-0.4.1-3.lbn13.noarch
Find newer package versions on PyPI
RPMPackage zope-z3c.caching-2.0a1-2.lbn13.noarch
z3c.caching
RPMPackage zope-z3c.blobfile-0.1.5-4.lbn13.noarch
This package provides an implementation of zope.app.file.interfaces.IFile which uses the Blob support introduced in ZODB 3.8. It's main purpose is to provide an easy migration path for existing instances. For more advanced file implementations see zope.file and z3c.extfile. The standard implementation in zope.app.file uses chunk objects to break big files into manageable parts. These chunks flow the server caches whereas blobs are directly consumed by the publisher. The main difference between this blob implementation and the old zope.app.file implementation can be seen in a replacement of the chunk objects by Blobs.
RPMPackage zope-z3c.batching-1.1.0-5.lbn13.noarch
This module implements a simple batching mechanism that allows you to split a large sequence into smaller batches.
RPMPackage zope-z3c.autoinclude-0.3.5-1.lbn13.noarch
This package adds two new ZCML directives to automatically detect ZCML files to include: "includeDependencies" and "includePlugins". When you want to include a Zope-based package in your application, you have to repeat yourself in two places: you have to add the package itself (in a setup.py, buildout, etc) and you also have to include its ZCML with an include directive or a package-includes slug. Because you have to repeat yourself, you can easily make an error where you add a new package but forget to include its ZCML. z3c.autoinclude lets you circumvent this error-prone process with automatic detection and inclusion of ZCML files.
RPMPackage zope-z3c-3.1.0-1.lbn13.noarch
Zope 3 base module hierarchy
RPMPackage zope-wildcard.fixpersistentutilities-1.1b7-1.lbn13.noarch
Introduction This product was created to help you remove nasty local persistent utilities that won't go away and can destroy your instance when you try to remove a product that registered one. Features * remove adapters * remove subscribers * remove provided interfaces * remove provided interfaces across the entire site - useful for removing collective.flowplayer Just append '/@@fix-persistent-utilities' onto your plone site root or the root of zope(for gsm) and browse through all your registered utilities on your site and remove things at will. By default, the tools prevents you from removing certain registrations; however, you can enter "expert mode" and remove whatever you want. WARNING!!! You can really screw up things if you do this wrong so use with extreme care and backup your instance before you use it. I will not take responsibility if you misuse this tool... Advice Do not include this product as part of your normal set of products. Only install this product on debug zope clients. This product should allow you to remove things from products that are no longer installed on the system; although, if you experience problems removing things, make sure to add those eggs to the system again.
RPMPackage zope-transaction-1.1.1-2.lbn13.noarch
Transaction management for Python
RPMPackage zope-tempstorage-2.12.2-2.lbn13.noarch
A RAM-based storage for ZODB
RPMPackage zope-pgsql-2.13.18-2.lbn13.x86_64
This package contains the PostgreSQL backend for Zope and necessary startups
RPMPackage zope-oracle-2.13.18-2.lbn13.x86_64
This package contains the Oracle backend for Zope and necessary startups