System based on annotation to make a configurable browser view by Makina Corpus.
Project description
Introduction
Harlequin provide infrastructure to make configurable browser view without to have to deals with how the configuration data are stored. Most of the time developers faced to this issue store data in the model. This is bad because all instances have those data and do not necessary need it.
Your configuration view data are stored and your view can access to this configuration easily.
This module doesn’t provide any ‘user’ feature to Plone.
How to use it
You can checkout the example package inside.
Credits
Authors
JeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>
Contributors
Changelog
1.0b4 (2010-05-31)
add example package; used as a test and as documentation [toutpt]
portal_properties can be now used to override schema default values: use ‘schema.__identifier__’+’-‘+field name as property id.” [toutpt]
1.0b3 (2010-05-31)
remove property manager storage component
move functionnal test in tests folder and add integration example
update interfaces: Now you have harlequin_form, harlequin_schema as attributes
harlequin_form is optional (A form will be generated from the schema) [toutpt]
1.0b2 (2010-05-28)
Replace harlequin_schema by harlequin_form
The browserview is now the only entry point of harlequin
1.0b1 (2010-05-27)
Initial release
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.
