| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
same tool that doxygen uses.
This is not ready for primetime but I had already looked
at this and it didn't look to hard so I stuck it in.
With this CL nothing will happen unless graphviz is
added to third_party/graphviz/files but I wanted
to at least check in what has to happen so that if
someone else wants to finish it they can.
Basically jsdoctoolkit generates a .dot file that
lists the inheritance, that is passed to dot which
creates a png and a map file for a client side
image map. To actually use it online would require
inserting the map file into an html file, probably
using EZT or python.
Otherwise, to be useful we'd need to split the template
into ParamMatrix4 and its derived classes, Param and
its derived classes. RenderNode and its derived classes,
ParamObject and its derived classes and then finally
everything not covered by the above.
Otherwise the chart is too big.
http://www/~gman/images/class_hierarchy.png
To be honest though, given it's just a tree a simple
HTML page could also do this without the graphing.
Just a simple
-NamedObject
|
+-Param
|
+--ParamFloat
|
+--ParamInteger
etc.
Nearly as simple would be to save the data to JSON and
graph it in JavaScript live in the browser using
canvas or O3D. That would be a lot smaller than the 9meg
for the binary parts of graphviz
Review URL: http://codereview.chromium.org/174384
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25315 0039d316-1c4b-4281-b951-d872f2087c98
|
