Hi Carl, To be honest, I think that Django will never achieve complete separation in terms of MVC model staying this convenient tool. There are many places where Django has a simple way of doing things, even when it's not full MVC-compilant. Current Form.as_(table|ul|p) methods are examples. I believe that Django should keep simple things simple.
Template-based forms are great idea (however can't say I've read the whole patch, it's rather huge), but I don't think that creating template to separate groups of fields is keeping simple things simple. Fair point about `classes` and several fields in a row though. I think you're right and decided not to do that. Mikołaj -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/Qn4IXnZihmoJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
