On Thursday 19 June 2008 04:05:26 pm Michael Droettboom wrote: > I just committed support for inheritance graphs in the docs like the one > attached. In the docs themselves, an image map is included so clicking > on a node hyperlinks to the class docs.
Really cool, Mike. > It uses "dot" to render the graph, and therefore you must have graphviz > installed. If it isn't, the directive *should* insert warnings in the > docs and not hard fail, but please let me know if it does. We can just > as easily change that behavior so it doesn't even insert the warnings. > > I'm also interested in feedback on the usefulness of these graphs or > ways they could be improved. I personally find them quite helpful, as > long as they aren't too large. Rather than producing one graph for > everything, it works pretty well to create graphs on the level of the > current division of the API docs (artists, collections, transforms etc.) I agree, it works well with some boundary conditions. In the old users guide, the inheritance diagram for backend FigureCanvases could have a big rubberstamp across it that reads "COMPLICATED". (No offense intended, but damn. :) ) Darren ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
