Binding

Misc

write a form definition schema so that definitions can be optionally validated.

flatten the CForm-related component in cocoon.xconf. This will ease the transition to a non-Avalon container

restructure resources directory (group XSLs and put them into their own directories)

second wizard example - shows how one form that is used in several templates can be controlled by Flowscript

Review multi-form-per-page - does it work? - provide a sample

Update the tour block samples to be in sync with these changes

Requests for enhancement (not discussed and/or aggreed yet)

Enabled modify form define through api

I have a usecase for this too (RP): Depending on the content of a form, a dynamic number of actions can be triggered. The possible actions are stored in a database and have to be read out at form creation time and action-widgets have to be set dynamically.

Remove everything that has been deprecated (union/struct, old validators, ...)