On Feb 16, 1:07 pm, "waylan" <[EMAIL PROTECTED]> wrote:
> On Feb 16, 3:28 pm, "jfagnani" <[EMAIL PROTECTED]> wrote:
>
> > (I think I lost an earlier reply, so hopefully this isn't a dupe)
>
> > I think it's important to add t
(I think I lost an earlier reply, so hopefully this isn't a dupe)
I think it's important to add the classes to the fields themselves, as
well as the , , and elements.
For complex, non-linear forms, I place fields in the template via
{{ form.field }}, not with the as_ methods. I think the field
On Feb 2, 1:17 pm, "Frankie Robertson"
<[EMAIL PROTECTED]> wrote:
> Sorry, I had some trouble understanding your situation. So I'm not
> sure, but isn't this what prefixes are for? I suppose they're a bit
> tedious to use (what with having to inject the id of the child row
> into the clean_data
I've been using Django for a few months now and have recently started
looking into newforms. I was hoping that it would solve some issues I
was having with the old Manipulator/FormWrapper way, but one thing is
still a little painful to do when it seems like it could be handled
automatically.
I ha
