I believe it would be beneficial to the Django developers and users if the documentation included a diagram showing the complete structure of how Class Based Views get their functionality. This would be a relatively simple diagram that shows the classes each generic view inherits from. The reason I am proposing this is because the current state of Generic Class Based Views is too complex for many people, myself included, with some views inheriting from 9 other classes (CreateView, UpdateView) down a long chain of both single and multiple inheritance. This would also enable people to gain a deeper understanding of why the Views are structured the way they are, and encourage people to explore the available BaseViews and mixins in order to assemble more customized applications without having to reinvent the wheel.
I posted this on the Django Reddit community<http://www.reddit.com/r/django/comments/1kkl2t/a_diagram_showing_the_entire_django_class_based/>with relative success being the top post. There is a DIA <https://projects.gnome.org/dia/> diagram file and SVG available on a Google Drive folder<https://drive.google.com/folderview?id=0B4OX1EeVEeoKQWtQNF9ZMUpMOVE>that is publicly accessible for you to download and modify. Version 3 is the most current revision and differs extensively from what I originally posted on Reddit. A preview of the diagram can be seen below (It's a fairly large image): <https://lh3.googleusercontent.com/-O0AortNlukI/UhEnV_9uRpI/AAAAAAAAG5s/f0jIkiqqT-E/s1600/djangocbv-3.png> -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
