Robert Niederreiter wrote:
Your proposal has some advantages. On the other hand this requires to
create CMF specific code and patterns in a place where a more generic
solution also works.
it does not if you call a formfactory inside the traverser, so it's
hoohable for CMF, Plone or whatever even with different formlib
formfactory = getAdapter(context,
which handles all the magic in there. just a thought.
Writing generic code is just the first step. Pushing this down the stack
and making it the default pattern for Zope is much harder.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests