Copied from the related thread on reddit: "the folks at ccbv.co.uk have been looking to build some sort of diagram..."
We have indeed! In fact, in response to excitement generated by this thread, I've shipped our best version so far. To see it: go to any class on ccbv (eg http://ccbv.co.uk/TodayArchiveView/) and click the "Hierarchy diagram" link towards the top right. This feature is still a work in progress, and hopefully will show attributes/methods soon (and be better integrated into the page). For the moment, I hope this keeps everyone happy! Meshy `:D`. On Tuesday, August 20, 2013 9:56:56 AM UTC+1, George Hickman wrote: > > Seth, > > This sounds like a great idea. I believe the folks behind ccbv.co.uk are > also trying to do something like this, maybe you could collaborate with > them? > > George > > On Monday, August 19, 2013 8:40:36 PM UTC+1, Seth Moon wrote: >> >> Such as one for each of the pink CBVs (CreateView, UpdateView, etc)? >> Yeah, I'll see what I can do. >> >> On Monday, August 19, 2013 12:54:29 AM UTC-7, Daniel Greenfeld wrote: >>> >>> Seth, >>> >>> I like it a lot. Is there any chance you can provide a focused version >>> per Class-Based View? >>> >>> Daniel Greenfeld >>> >>> On Sunday, August 18, 2013 10:03:59 PM UTC+2, Seth Moon wrote: >>>> >>>> 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): >>>> >>>> -- 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.
