Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-08 Thread Roger Ineichen
Hi Martin > Betreff: Re: [Zope3-Users] z3c.form: LookupErrors [...] > What I'd like to see: > > 1) z3c.form catches the LookupError and treats it as a > valdiation error (even on first render of the form), not a fatal error seems Ok to me > 2) z3c.form defaults to

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-08 Thread Stephan Richter
On Wednesday 08 April 2009, Martin Aspeli wrote: > Would you mind making a 1.9 maintenance branch and, Done. > if we fix a few bugs, could you release 1.9.1 soonishly. Yes. Please forward new fixes to the trunk as well. Thanks! Regards, Stephan -- Stephan Richter Web Software Design, Develop

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-08 Thread Martin Aspeli
Stephan Richter wrote: > On Wednesday 08 April 2009, Martin Aspeli wrote: >> What I'd like to see: >> >> 1) z3c.form catches the LookupError and treats it as a valdiation >> error (even on first render of the form), not a fatal error >> >> 2) z3c.form defaults to missing_value if there is a Loo

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-08 Thread Stephan Richter
On Wednesday 08 April 2009, Martin Aspeli wrote: > What I'd like to see: > >   1) z3c.form catches the LookupError and treats it as a valdiation > error (even on first render of the form), not a fatal error > >   2) z3c.form defaults to missing_value if there is a LookupError > against what the dat

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-08 Thread Martin Aspeli
Hi Roger, > I agree that this should not end in an error blocking the UI. Good. :) > Let's say you have a Choice with possible values defined in > a source, vocabulary or a simple list like: > > ['please select', 'Max', 'Peter', 'Fred', 'Admin'] > > And we have a field which looks like:

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-07 Thread Roger Ineichen
Hi Martin > Betreff: Re: [Zope3-Users] z3c.form: LookupErrors > > Hi Roger, > > >> What if your list of choices depends on constantly > changing data? For > >> example, a widget allows you to select a user from a userfolder. > >> Later the use

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-07 Thread Martin Aspeli
Hi Roger, >> What if your list of choices depends on constantly changing >> data? For example, a widget allows you to select a user from >> a userfolder. Later the user gets deleted. > > pang, legacy data created In the real world, this type of of thing happens all the time. It's incredibly

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-07 Thread Roger Ineichen
Hi Stephan > -Ursprüngliche Nachricht- > Von: Stephan Richter [mailto:srich...@cosmos.phy.tufts.edu] > Gesendet: Dienstag, 7. April 2009 19:30 > An: zope3-users@zope.org; d...@projekt01.ch > Cc: 'Martin Aspeli' > Betreff: Re: [Zope3-Users] z3c.form: LookupErr

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-07 Thread Stephan Richter
On Tuesday 07 April 2009, Roger Ineichen wrote: > > It'd be nicer if z3c.form would catch the error and return > > field.missing_value or something like that. As it stands, if > > this happens with a content object, it's impossible to reach > > the edit form and fix the value! > > This is a legacy

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-07 Thread Stephan Richter
On Tuesday 07 April 2009, Martin Aspeli wrote: > It'd be nicer if z3c.form would catch the error and return > field.missing_value or something like that. As it stands, if this > happens with a content object, it's impossible to reach the edit form > and fix the value! I agree. Regards, Stephan --

Re: [Zope3-Users] z3c.form: LookupErrors

2009-04-07 Thread Roger Ineichen
Hi Martin > -Ursprüngliche Nachricht- > Von: zope3-users-boun...@zope.org > [mailto:zope3-users-boun...@zope.org] Im Auftrag von Martin Aspeli > Gesendet: Dienstag, 7. April 2009 16:17 > An: zope3-users@zope.org > Betreff: [Zope3-Users] z3c.form: LookupErrors > > Hi, > > In z3c.form (a