On Fri, Sep 16, 2011 at 8:34 AM, Reinout van Rees <rein...@vanrees.org> wrote: > Watch out, in general, with adding more and more mixins. > > I explained just the most basic template CBV to a colleague: there are just > two mixins and a base class there, but his eyes already started to glaze > over because I had to jump from class to class to class to explain how it > all hung together.
that is my own reaction too when trying to see where in the code is everything that i knew from the old generic view functions. mixins are a great way to encapsulate specific, well defined behavior; but tracing the code is a real chore, even so clean code as Django's. I guess that when you know by heart exactly what does each one do, they become a pleasure to use. So, my two cents: please do the documentation first. once there's a single place to find exactly what the purpose, mechanism and span of each one, then adding more would be welcomed. -- Javier -- You received this message because you are subscribed to the Google Groups "Django developers" group. 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.
