Roger Ineichen wrote:
> Since this is a miss behavior and I agree that this should get fixed. We
> probably should think about a solution which supports the old behavior by
> Note, this whould probably also break other packages like
We've thought about this some more. Our current suggestion is to implement
both behaviours using a class attribute for switching, with the base class
implementing the new, better one and a subclass setting the attribute
differently for BBB.
We'd like to register the base class with changed behaviour as the
default, though, in order to facilitate adoption of the new and better
implementation and provide an override registration for the BBB widget.
Applications would then have an easy migration path, having to add only
one line of ZCML after the zope.app.form update.
Also, we'd like to implement the new behaviour in such a way that the "no
value" value isn't shown for required fields that already have a valid
value set. What do others think about this?
Thomas Lotze · [EMAIL PROTECTED]
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -