Am Sonntag, den 08.07.2007, 11:31 -0400 schrieb Stephan Richter:
On Sunday 08 July 2007 10:02, Christian Theune wrote:
Log message for revision 77624:
More work on bug 98287: Introduced an event to signal that an object
value is going to be assigned.
Ahh, this is crazy! Why would
On 7/8/07, Christian Theune [EMAIL PROTECTED] wrote:
Please revert. The solution is to rip out setting the value from within the
field
altogether.
Humm. Ripping out setting the value from within the field doesn't make
sense to me. The field is the only demonitator between zope.app.form and
On Sunday 08 July 2007 10:02, Christian Theune wrote:
Log message for revision 77624:
More work on bug 98287: Introduced an event to signal that an object
value is going to be assigned.
Ahh, this is crazy! Why would zope.schema depend on zope.event, which depends
on zope.component (if not
Am Sonntag, den 08.07.2007, 11:31 -0400 schrieb Stephan Richter:
On Sunday 08 July 2007 10:02, Christian Theune wrote:
Log message for revision 77624:
More work on bug 98287: Introduced an event to signal that an object
value is going to be assigned.
Ahh, this is crazy! Why would
On Sunday 08 July 2007 11:38, Christian Theune wrote:
Am Sonntag, den 08.07.2007, 11:31 -0400 schrieb Stephan Richter:
On Sunday 08 July 2007 10:02, Christian Theune wrote:
Log message for revision 77624:
More work on bug 98287: Introduced an event to signal that an object
value is
On Sunday 08 July 2007 13:19, Tres Seaver wrote:
I don't see how that can be: 'zope.event' hsa no dependencies[1], and
provides a service which is at least as low-level (lower, in my opinion)
as 'zope.schema': I can imagine *lots* of Zope3-based applications
which do not use zope.schema, but
