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]
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Hashes for collective.complexrecordsproxy-1.0.tar.gz
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | c9a9a3fa287e88321bc64fd1a699d189edfa7313bad980e0c3c7c10eef55b085 |
|
| MD5 | 4bb382afb7a2c810e675cd6988e39cac |
|
| BLAKE2b-256 | 712ebfdb75c863dfa1a1ae245aaec38b634e2976f42f5e90791b70ad291e9ae6 |
