Adrian Holovaty wrote:
> Ah, you're talking about the *old* form system...django.newforms has a
> way of dealing with this -- check out
> CheckboxSelectMultiple.value_from_datadict(), which is automatically
> called by Form.full_clean().
Ah... I was in fact just looking at HTML and just recalle
On 11/30/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> > Instead of this it can look like this (note the value attribute which
> > replaces default "on"):
> >
> >
> >John
> >Paul
> >
> >
> > and a POST would be exactly as with without the need
> > of `prepare`.
>
>
On 11/30/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> Currently using checboxes it looks like:
>
>
>John
>Paul
>
>
> and a POST is:
>
> beatlesJ=on&beatlsP=on
>
> And then you should remeber to call manipulator.prepare(new_data) to
> convert these names into a li
Adrian Holovaty wrote:
> How would CheckboxSelectMultiple work otherwise, and how is the
> compatibility broken?
Consider :
John
Paul
If you select both items in a POST you'll get:
beatles=John&beatles=Paul
... which you will then nicely get as request.POST.getl
On 11/30/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> CheckboxSelectMultiple is in effect just an alternative representation
> of . Ideally one would be able to just switch between
> these widget types not having to touch any other code. However
> CheckboxSelectMultiple uses different names for
Hi!
I'm now 'having a look' at newforms upon Adrian's request.
I noticed a thing I was long forgotten to file as a ticket. So may be
it's a good time to fix it.
CheckboxSelectMultiple is in effect just an alternative representation
of . Ideally one would be able to just switch between
these
