Skip to main content

Providing a proxy class for plone.registry allowing IObject fields to be stored as separate records using the plone.registry collection support.

Project description

collective.complexrecordsproxy

Providing a proxy class for plone.registry allowing IObject fields to be stored as separate records using the plone.registry collection support.

Motivation

With z3c.form it is possible to create forms allowing users to create and edit lists of complex records.

An example:

TODO from here.

We have a main interface with an object field etc.

We build a hierarchic structure composed of native types. All boils down to simple native types in the end, and so in theory is possible to store in the registry without violating this principle of plone.registry:

“To avoid potentially breaking the registry with persistent references to symbols that may go away, we purposefully limit the number of fields supported.

Usage

Changelog

1.0 (2016-01-29)

  • Initial release [sunew, tomgross]

Project details


Release history Release notifications

This version
History Node

1.0

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
collective.complexrecordsproxy-1.0.tar.gz (8.0 kB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page