zeam.form.table
zeam.form.table is a extension to zeam.form.base to create CRUD forms: it let define forms that can work on a collection of contents sharing the same form schema.
As well zeam.form.table can be embedded as a sub form in a composed form built with zeam.form.composed.
Changelog
1.1.1 (2012/10/11)
Update SelectField to be compatible with zeam.form.base 1.3.
1.1 (2012/09/24)
Add support to provide item specific identifiers for lines checkbox.
Update API to use zeam.form.base 1.2.3.
1.0.1 (2012/04/27)
Update to use grokcore.chameleon instead of megrok.chameleon.
Fix some action type when used with postOnly.
Fix template, add missing fields in it.
1.0 (2011/11/07)
Add different strategies to apply actions to table lines. You can by choice have one action that takes all selected and all not selected lines, one actions on lines that have been selected or deselected or lastly an action that execute only on select lines.
Add support for batching on table forms.
You can now customize the selection field.
Update to work with zeam.form.base 1.2.
Update tests.
1.0b1 (2010/10/27)
Initial proof of concept release.
Metadata
Release files for zeam.form.table 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zeam.form.table-1.1.1.tar.gz | 7.7 kB | Without provenance | Details for zeam.form.table-1.1.1.tar.gz |
Release files / zeam.form.table-1.1.1.tar.gz
| Download URL | zeam.form.table-1.1.1.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b206a97a78515b4f98ee9e31bcc2b26835d6b4cf9de33bd20150a77b1a3572e9
|
|
BLAKE2b-256 checksum How to use checksums |
0e2ae526525b491d458cfcbd38f4fa316d8d1dadee52335fe3b628d317e3b00a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zeam.form.table 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.