On Feb 14, 7:10 am, Collin Grady <[EMAIL PROTECTED]> wrote:
> Rock said the following:
>
> > Some thoughts:
>
> > Inplementing form.as_items returning a list of form lines would be
> > nice.
> > This allows a variety of custom formatting options. Examples:
>
> >
> > {% for item in forms.as_items
Rock said the following:
> Some thoughts:
>
> Inplementing form.as_items returning a list of form lines would be
> nice.
> This allows a variety of custom formatting options. Examples:
>
>
> {% for item in forms.as_items }}{{ item }} , {% endfor %}
> <...submit directive...>
>
>
>
> {{ item[
Some thoughts:
Inplementing form.as_items returning a list of form lines would be
nice.
This allows a variety of custom formatting options. Examples:
{% for item in forms.as_items }}{{ item }} , {% endfor %}
<...submit directive...>
{{ item[0] }} -- {{ item[1] }} -- {{ item[2] }}
{{ item[3]
David,
I'm a little behind (two weeks, maybe?) on some mailing list stuff, but
this seems to have gone relatively unanswered...
On Mon, 2008-02-04 at 21:46 -0800, David Cramer wrote:
> We've had many interesting situations come up with newforms where we
> couldn't use the simple form.as_p method
My take on this.
Each BoundField already has 'as_' methods for widgets so 'as_p' would
not belong there.
But you can override __getitem__ in the Form/ BaseForm to return your
own version of BoundField that has a 'as_p' method.
On Feb 5, 6:46 am, David Cramer <[EMAIL PROTECTED]> wrote:
> We've h
We've had many interesting situations come up with newforms where we
couldn't use the simple form.as_p method.
Myself, being the lazy person I am, use form.as_p anywhere possible.
We've even modified it to spit out class names based on widget type.
What I'd like to propose (and hear a good reaso
