Eh, I’ve decided to stick it out and give newforms more of a chance. I’ve been writing forms that override different functions of the newform depending on what I need. I’ve also created a few custom widgets. Since I’m a fairly lazy programmer I’ve been slightly annoyed that I’m writing so much custom stuff. Oh well.
I think djangosnippets.org saved my relationship with newforms. I was able to find some pretty nice newform bits there and if you’re working with Django, it’s totally worth checking out. Scriptaculous also helped save newforms with its Event.observe() - a quick, browser-compatable way to add listeners to HTML objects.
3 Comments
Alexander Repty
“Three great virtues of programming are laziness, impatience, and hubris.” ~Larry Wall
Don’t worry, being a lazy programmer is a good thing.
Richard Kiss
I’m happy to hear you and the newforms could work through your differences. Communication is essential to any relationship. (I’m not sure how the analogy maps. May it translates to “read the documentation”. Or perhaps “email the developers incessantly”.)
Kelvin Nicholson
Newforms, imho, are going to be pretty badass once they get documented more. For me they have taken the hassle out of dealing with form data crap. Take a peak inside the reg tests if you haven’t already, was helpful for me.