Speaking as a Python newbie who is currently learning Django then OOP (i.e. the opposite of the logical, preferred order), I would really love documentation on this sort of thing. I wrote a hackish workaround to a very similar problem just yesterday which I can currently updating with your example in mind. :-) Thanks! - whiteinge
On Feb 11, 9:27 pm, "Benjamin Slavin" <[EMAIL PROTECTED]> wrote: > On 2/11/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > > > > As Honza suggested, you're already able to do this in a *much* more > > generic fashion by simply subclassing the form and implementing > > __init__(). I'm marking the ticket as a wontfix. > > Fair enough. > > Is there any interest in adding this to the newforms documentation? > You, Honza, and I came up with a workable solutions quite quickly, but > from what I've seen, most Django users are using Python for the first > time. I don't know how easily they would be able to solve this > problem. > > I don't mind putting together some documentation to help newbies, but > I figured I'd test the waters before committing the effort. Thoughts? > > - Ben --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
