After bashing at it some more, I had to conclude I was out to lunch. It is killing me to wait for newforms. It's senseless for me to learn old forms, but I'm having a helluva time making heads or tails of newforms. Some things that I swear must be common as mud -- like a form that sends to several tables (ye olde address vs purchase order scenario) -- seems far, far too difficult.
I think I'll just hardcode it all, and deal with improving it when newforms is better documented. On 07-May-18, at 12:09 AM, Doug B wrote: > > My suggestion would be to NOT implement it! I took a similar approach > when I was trying to learn python/django, wasted a bit of time, and > almost never use the monstrosity I created. I'd have been better off > just doing it the django way and/or waiting for newforms to be > completed (which may break my implementation anyway). > > However, looking at my mistake may give you enough info to make your > own! > > (it works, but should really have been a metaclass... but didn't know > anything about that at the time). > > http://dpaste.com/10566/ > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
