On Mar 11, 4:52 am, "Jeroen van Dongen" <[EMAIL PROTECTED]> wrote:
> Jeff: the case in snippet 82 is covered with the FormList idea.
> However, the case as presented in snippet 27 is not. And I'm in doubt
> it's something that requires a special form class actually.
I don't think I was arguing t
An early version can be found at: http://code.djangoproject.com/ticket/3706
--~--~-~--~~~---~--~~
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@googlegro
Jeff: the case in snippet 82 is covered with the FormList idea.
However, the case as presented in snippet 27 is not. And I'm in doubt
it's something that requires a special form class actually. What's to
prevent you from just creating a normal form and then altering the
required setting of one of
On Mar 10, 6:47 am, "Jeroen van Dongen" <[EMAIL PROTECTED]> wrote:
> Jeff: could you elaborate a bit on what you mean with "dynamic
> fields"?
Assigning a field dynamically is what occurs
when you only know at runtime which (or how
many) fields must be displayed. This is not
simply a matter of u
I'm currently working to get a releasable version that I can post to
Trac - perhaps tomorrow.
Thomas: I've replied to you yesterday, but my reply does not seem to
show up. Longer story short: the javascript is not autogenerated yet,
but could be done. I'll first get a basic version in a releasabl
Jeroen,
Right now my biggest time sink with newforms is dealing with dynamic
fields (in contrast to dynamic forms). I'd like to work up some
examples and present them as possible use cases to address, if you
think dynamic fields might fall within the scope of SuperForms.
--
Jeff Bauer
Rubicon,
+1 - Sub forms and form lists are great and IMHO very common. Please
submit the patch.
On Mar 9, 11:18 am, "Jeroen van Dongen" <[EMAIL PROTECTED]> wrote:
> Apart from the SubForm "field" I've also created a FormList "field"
> which takes a form definition, a min_count and a max_count which
> allo
Hi all,
As far as I'm aware (from browsing the mailinglists and the newforms
code) newforms currently does not support compound or nested forms.
With this I mean something like (fairly dumbed-down example, but taken
from an app I'm currently working on):
class AddressForm(forms.Form):
street
