durusmail: quixote-users: So what _does_ the Quixote Form mechanics buy you?
So what _does_ the Quixote Form mechanics buy you?
So what _does_ the Quixote Form mechanics buy you?
2003-11-24
So what _does_ the Quixote Form mechanics buy you?
2003-11-24
So what _does_ the Quixote Form mechanics buy you?
2003-11-24
2003-11-24
So what _does_ the Quixote Form mechanics buy you?
2003-11-25
2003-12-05
So what _does_ the Quixote Form mechanics buy you?
Nicola Larosa
2003-11-24
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> What *I* would like to know how to do is to spit the form back to the user
> if some validation step fails.  That is, I'd like to render the form
> again with the values filled in, a message displayed identifying the
> problem, and perhaps highlight erroneous values.

Look at the "handle" and "process" methods of the form.Form class.
Interestingly, they didn't make it to the new form2 framework, but I find'em
a good starting point anyway.

Also, a number of members self.error among them, have been
decentralized, and now each Widget keeps its own data. In fact, the
form2.Form class has grown a "has_errors" method that wasn't previously needed.

Having used the original form framework, I find the diff between form and
form2 quite instructive.


By the way, form2.RadiobuttonsWidget.__init__ is broken, two parameters to
the call of the SingleSelectWidget constructor, at line #428 of widget.py,
survived while they shouldn't have, namely "allowed_values" and "descriptions".


- --
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr

Nicola Larosa - nico@tekNico.net


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/wiPIXv0hgDImBm4RAqwYAJ9SDqIC21cXhu+B8itMwBy4vo6jOwCgvp/O
vu8QSHCSKe2V5YScNNf+GXY=
=zbHd
-----END PGP SIGNATURE-----



reply