Zachary, today I was thinking along the same lines and I really really like your proposal!<p>How do you propose object-based views to expand beyond the generic cases in order to handle for example multiple forms, or hiding a field from a form and then adding that (for example request.user) after form validation, before save , or add some additional logic to a detail view?<p>In my opinion, IDS['slug'] would be neater than ids.SLUG<p>And now for something completely different:
An other idea of mine which keeps going around in my head is having addable forms, so you can do total_form = profile_form + company_form and easily validate etc. What do you think?
Ruby on Rails had a lovely scaffolding system that everyone told me not to use.<p>Python tells me to be explicit instead of implicit.<p>It's also nice to not have much magic in our frameworks.<p>CBVs leave a lot to be desired but FBVs were terrible when you did really want to reuse code. I can never decide with CBVs whether I like the declarative approach but I can only see this resource magic being overridden as quickly as you can put it in at least with CBVs with every new mixin or subclass I feel I'm truly extending on something (albeit with additional MRO complexity but then maybe you have bigger problems if you're finding those kinds of issues).