Modified items

All recently modified items, latest first.

zope-z3c.sqlalchemy-1.4.0-2.lbn13.noarch: What is z3c.sqlalchemy? z3c.sqlalchemy is yet another wrapper around SQLAlchemy. The functionality of the wrapper is basically focused on easy integration with Zope 2 and Zope 3. The wrapper cares about connection handling, optional transaction integration with Zope 2/3 and wrapper management (caching, introspection). z3c.sqlalchemy gives you flexible control over the mapper creation. Mapper classes can be * auto-generated (with or without autodetection of table relationships) * configured by the developer What z3c.sqlalchemy does not do and won't do: * no support for Zope 3 schemas * no support for Archetypes schemas z3c.sqlachemy just tries to provide you with the basic functionalities you need to write SQLAlchemy-based applications with Zope 2/3. Higher-level functionalities like integration with Archetypes/Zope 3 schemas are subject to higher-level frameworks. z3c.sqlalchemy does not address these frameworks.

zope-z3c.relationfield-0.6.2-3.lbn13.noarch: A relation field framework for Zope 3.

zope-z3c.recipe.sphinxdoc-0.0.8-3.lbn13.noarch: Use Sphinx to build documentation for zope.org.

zope-z3c.recipe.scripts-1.0.1-2.lbn13.noarch: Recipe for installing Python scripts

zope-z3c.recipe.depgraph-0.5-2.lbn13.noarch: Buildout recipe to generate dependency graphs.

zope-z3c.recipe.compattest-0.12.2-2.lbn13.noarch: Buildout recipe to create testrunners for testing compatibility with other packages

zope-z3c.ptcompat-1.0.1-2.lbn13.noarch: This package provides a page template engine implementation based on Chameleon. It plugs into the zope.pagetemplate package and has an explicit dependency on this package. You can use the package to replace Zope's reference template engine with Chameleon in an application based on the Zope Toolkit.

zope-z3c.pt-2.2.3-3.lbn13.noarch: This is a fast implementation of the ZPT template engine for Zope 3 which uses Chameleon to compile templates to byte-code. The package provides application support equivalent to zope.app.pagetemplate.

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.

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.

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.

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.

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.

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.

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.

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.

zope-z3c.coverage-1.2.0-2.lbn13.noarch: z3c.coverage

zope-z3c.checkversions-0.4.1-3.lbn13.noarch: Find newer package versions on PyPI

zope-z3c.caching-2.0a1-2.lbn13.noarch: z3c.caching

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.

« Previous 20 items Next 20 items » 1 ... 2346 2347 2348 2349 2350 2351 2352 ... 2425


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

Sections

Modified items