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 that #27 should be handled by SuperForms, it was more a response to answering your question regarding dynamic fields. Actually my first post was to ask if this issue even falls within the scope of SuperForms. Based on your response, no. Regarding #82: Thanks, I was hoping that FormList covered this use case. Your patch (ticket #3706) mentions some known bugs with FormList that will be addressed later this week. Suggestion: Since your patch doesn't require any modification of newforms, you could also post it to djangosnippets.org where it might get more coverage from people who don't monitor Trac. Thanks again and best regards. -- Jeff Bauer Rubicon, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
