John Hunter wrote: > On Thu, Jun 19, 2008 at 3:05 PM, Michael Droettboom <[EMAIL PROTECTED]> 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. >> >> 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 think these will be really useful. I hope we can tweak the layout > somewhat -- I think some of these graphs are too wide, for example (eg > the artist graph). One cheap way to deal with the width might be to just use the class name, not "matplotlib.artist. ...". But in general, if you have four levels of nesting, you're guaranteed four columns with the dot algorithm (excepting manual tweaks). > Of course, the rendering is also somewhat painful > to me, after years of looking at agg rendering. Maybe I need to write > a dot output renderer.... > > But aside from these minor stylistic nits which we can improve, the > functionality is great and I suspect sphinx will be interested in > including this.... Gee, we sure are acting like typical developers: > spending all our time working on the doc *system* rather than the > boring old docs themselves :-) > Yep... ;)
Mike ------------------------------------------------------------------------- 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
