[Zope-CMF] Form validation

Florent Guillaume fg@nuxeo.com
21 Feb 2003 20:47:11 +0100


On Fri, 2003-02-21 at 19:40, Alan Runyan wrote:
> > I'd put all the navigation targets as additional attributes of the Type
> > itself. Which either requires extending a bit the ActionsTool, or simply
> > use not-visible pseudo-actions  la
> >   id: edit_target
> >   action: mytype_edit
> > and some logic to automatically go to indirect through edit_target,
> > for instance
> >   <form action="portal_form/action_target?target=edit">
> > or even
> >   <form tal:attributes="action here/portal_form/action_target/edit">
> > or something...
> 
> iirc this is *exactly* what gdavis plans to do.  then maybe we can roll
> alot of this back into the CMF at some point ;-)  It would be nice
> if we all used the same mechanism for form validation across CMF
> projects.
> 
> which reminds me.. how does CPS do this?  inside the xxxx_edit.py
> scripts?

In current CPS, all form validation is ad hoc.
For the future, we're working on completely redesigning document and
forms, so that all forms in CPS are generated and validated
automatically from an abstract description of the form/document. This
won't land before 1-2 months though.

Florent

-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87  http://nuxeo.com  mailto:fg@nuxeo.com