Search results

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.sqlalchemy-1.4.0-2.lbn19.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.sqlalchemy-1.4.0-2.lbn25.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.table-2.0.0a1-1.lbn13.noarch

The goal of this package is to offer a modular table rendering library. We use the content provider pattern and the column are implemented as adapters which will give us a powerful base concept. Some important concepts we use * separate implementation in update render parts, This allows to manipulate data after update call and before we render them. * allow to use page templates if needed. By default all is done in python. * allow to use the rendered batch outside the existing table HTML part. No skins This package does not provide any kind of template or skin support. Most the time if you need to render a table, you will use your own skin concept. This means you can render the table or batch within your own templates. This will ensure that we have as few dependencies as possible in this package and the package can get reused with any skin concept. Note As you probably know, batching is only possible after sorting columns. This is a nightmare if it comes to performance. The reason is, all data need to get sorted before the batch can start at the given position. And sorting can most of the time only be done by touching each object. This means you have to be careful if you are using a large set of data, even if you use batching.

zope-z3c.tabular-0.6.2-1.lbn13.noarch

This package provides a table implementation including form support for Zope3 based on z3c.form and z3c.table.

zope-z3c.template-1.4.1-2.lbn13.noarch

This package allows you to register templates independently from view code. In Zope 3, when registering a browser:page both presentation and computation are registered together. Unfortunately the registration tangles presentation and computation so tightly that it is not possible to re-register a different template depending on context. (You can override the whole registration but this is not the main point of this package.) With z3c.template the registration is split up between the view and the template and allows to differentiate the template based on the skin layer and the view. In addition this package lays the foundation to differentiate between templates that provide specific presentation templates and generic layout templates.

zope-z3c.template-2.0.0-1.lbn25.noarch

This package allows you to register templates independently from view code. In Zope 3, when registering a browser:page both presentation and computation are registered together. Unfortunately the registration tangles presentation and computation so tightly that it is not possible to re-register a different template depending on context. (You can override the whole registration but this is not the main point of this package.) With z3c.template the registration is split up between the view and the template and allows to differentiate the template based on the skin layer and the view. In addition this package lays the foundation to differentiate between templates that provide specific presentation templates and generic layout templates.

zope-z3c.template-2.0.0-1.lbn25.noarch

This package allows you to register templates independently from view code. In Zope 3, when registering a browser:page both presentation and computation are registered together. Unfortunately the registration tangles presentation and computation so tightly that it is not possible to re-register a different template depending on context. (You can override the whole registration but this is not the main point of this package.) With z3c.template the registration is split up between the view and the template and allows to differentiate the template based on the skin layer and the view. In addition this package lays the foundation to differentiate between templates that provide specific presentation templates and generic layout templates.

zope-z3c.widgets-1.0c1-4.lbn13.noarch

Zope 3 widget base module hierarchy

zope-z3c.widgets-1.0c1-4.lbn19.noarch

Zope 3 widget base module hierarchy