Actually, you might try adding them in your form's __init__ method,
again, after calling
the superclass method. I've done this with choices on a field.
Since self.fields is a
deep copy, you might be safe setting an attrs attribute on the field's widget:
self.fields['fieldname'].widget.attrs.up
On Jun 3, 12:05 pm, Thomas Allen wrote:
> I'm able to get pretty far with the template tag approach. The trouble
> is that BoundForms offer no way to directly add attributes, which I
> think can only be included when defining the form field in question.
Actually if I bypass unicode() and use as_w
On Jun 3, 12:00 pm, Bill Freeman wrote:
> If you can't use _html_output, then you have to duplicate a lot of
> it's functionality.
I'm able to get pretty far with the template tag approach. The trouble
is that BoundForms offer no way to directly add attributes, which I
think can only be included
If you can't use _html_output, then you have to duplicate a lot of
it's functionality.
That's a lot internals, and you would have to track any changes with
revisions. Of
course, _html_output is, itself, an internal, according to the naming
conventions.
If what you're wanting to do is change the
How can I create my own form renderer, like as_p, as_table, etc? I see
that the form class provides _html_output to assist in formatting
markup like this, but that substitution technique does not provide
enough control for what I am doing, where certain properties of the
field in question affect th
5 matches
Mail list logo
