On Wed, Apr 29, 2009 at 10:33 AM, ken keller wrote:
>
> form.as_table is appealing but seems limited:
Ken, the consensus seems to be that the form.as_* methods are for
quick prototyping and not really meant for fine grained control. If
you want more control over the output of the form, build it up in the
template yourself from the various parts. Remember, you can loop
through the fields in your template and render each separately.
> * Many forms need field groups to be highlighted.
> * Sometimes multiple fields need to be in the same row (e.g., first &
> last name).
> * The use of for errorlist can cause layout problems.
>
> Sometimes I need to add non-bound fields to a bound form such as a CAPTCHA.
>
> Are these problems worth solving?
As these are all solvable now simply by ignoring the as_* methods, I
believe the answer is no. Of course, I'm not a core dev, so I could be
wrong, but my recollection of previous similar requests would seem to
indicate otherwise.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---
