--
Ticket URL: <https://code.djangoproject.com/ticket/19227>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: apollo13 (added)
* needs_docs: => 0
* needs_better_patch: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
As seen on a pycon-de presentation, a treelike structure is easier to
follow visually.
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:1>
Comment (by timo):
Component should be documentation I assume? What page does this refer to?
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:2>
Comment (by ohumbel):
This refers to: /ref/class-based-views/generic-display.html,
source: /docs/ref/class-based-views/generic-display.txt
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:3>
Comment (by ohumbel):
please note that the space before a dedent is due to the css
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:4>
* component: Uncategorized => Documentation
Comment:
Ah, makes sense. Would also be helpful to add a description of what the
"method flowchart" is trying to show I think.
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:5>
Comment (by pydanny):
I would love to have a tree view of the method flowchart. In fact, that is
what I originally submitted. However...
Even a Tree view is not adequate. The methods really need a proper
flowchart, not a text tree. Something perhaps even done in Graphviz.
Indeed, months ago @Jacobian started to work it in Graphviz and then ran
out of free time while working on the format for the Method flowchart.
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:6>
* status: new => assigned
* owner: nobody => garrypolley
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:7>
Comment (by garrypolley):
I've started taking a look at a gist from @Jacobian
https://gist.github.com/jacobian/5020615. I want to attempt to find a way
to automate the creation of these graphs.
Either way I'll try and get some more graphs done this Django sprint.
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:8>
Comment (by estebistec):
@garrypolley would this include new info in the "writing documentation"
section of the contributing HOWTOs?
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:9>
Comment (by garrypolley):
@estebistec I do not plan to update the "writing documentation" section.
After looking into writing a graph generator and talking to @jacobian I
don't think it's a good idea to make the graphs. It's rather difficult
and where do you decide to start the graph? Do you start at dispatch? Do
you list every method call in side each method?
Looking into ccbv.co.uk and seeing if there is a good way to fork it so it
will auto generate a version with each django release/branch. I think
ccbv.co.uk does a good job of showing what you can access on a CBV and
it's more detailed than a graph would be. I'm not convinced a graph or
flow chart is better than just using that site.
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:10>
* cc: garrypolley (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:11>
* cc: garrypolley (removed)
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:12>
* status: assigned => new
* owner: garrypolley =>
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:13>
* owner: => jambonrose
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:14>
* easy: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:15>
* owner: jambonrose => (none)
* status: assigned => new
--
Ticket URL: <https://code.djangoproject.com/ticket/19227#comment:16>