I just wanted to say that this is the reason I'm reluctant to use Django's forms (new or old) no matter how stable it is. I like that any major chunk of HTML code is visible for tinkering in my template files. Maybe a template solution would be more work (probably some repetition, I haven't really thought about how to combine both some automation and custom template files), but it would also be less surprising for me.
Same here. For most projects I've worked on that required forms, I've written my own because the forms output XHTML widgets and we're using HTML 4. And for all the talk of separating the database from the logic from the view, doesn't this violate this anyway -- having XHTML in the forms code? I'd much prefer the flexibility of template based forms. +1 from me on this. It's been suggested a few times in other places as well. -Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
