Martin Aspeli writes:
> If we want to be true to the tradition of Zope 3 and its simplified content
> types metaphor, then I think we should assume that a type consists of:
> - a class
> - a schema interface
> - an add form/view
> - an edit form/view
> plus the FTI to install it into the CMF site. I wouldn't try to be too clever
> and generalise away any of these.
+1 to keeping this simple at the CMF level. Clever libraries can always
hook into form lookup using the mechanics discussed and perform whatever
magic they need.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests