[Grok-dev] Heads up: Renamed AddForm to Form
Philipp von Weitershausen
philipp at weitershausen.de
Thu Mar 15 17:52:12 EDT 2007
From the commit log message:
- Renamed grok.AddForm to grok.Form because there was no additional
functionality in that base class that was specific to adding. Yes, it
used formlib's AddForm, but none of the features that has to make
adding objects easy for you were used (adding objects in Zope 3 is
overly complicated anyway, thanks to IAdding). Everybody writing add
forms was writing his/her own actions anyway, which is exactly what
the point of a general grok.Form base class is.
- Got rid of the "form in form" weirdness. It turns out that a very,
very simple mix-in with a custom render() method makes it possible to
mix formlib's base classes with grok.View. This makes the ViewGrokker
simpler and exposes more of formlib directly in Grok forms.
Apart from having to use grok.Form instead of grok.AddForm, existing
applications shouldn't have to change.
http://worldcookery.com -- Professional Zope documentation and training
More information about the Grok-dev