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
t; <[EMAIL PROTECTED]> wrote:
> 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 yo
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
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):
Thanks for your answers so far, great to see this discussion take off.
On a personal level I'll take the advise given to heart for future
contributions.
Rgds,
Jeroen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
While browsing through the open, unreviewed tickets I encountered some
tickets like 1049 (http://code.djangoproject.com/ticket/1049) which
imo should be closed/rejected for various reasons. In this case:
1) the topic of the ticket is oldforms, which will be phased out soon
(hence it is unlikely
I just read Brian's latest (?) blog entry on his full-text indexing
efforts
(http://blog.case.edu/bmb12/2006/08/merquery_summer_of_code_results)
and wanted to pitch in, however was unable to post comments to the
blog. As it's django development related, I'll just post it here
instead.
He writes
