> I've looked at #7004. There are parts I could safely review, but > other parts I don't feel comfortable with. Any chance it could be > chunked up into a few coherent parts that might be easier to review?
Thanks for your interest in this huge patch. I think that #7004 becomes too big to be understandable (moreover it is not ready for review !). I do not have so much time to do it right now (and it is too much work). Perhaps it could be a good idea to put a proposal on graph drawing for Google Summer of Code ? There is a lot of things to improve in this direction - interaction layout <-> plot : (no control on loops, no control on the size of the labels of the vertices, no size control on the label of the edges, no control on the limit of the graph, ...). Networkx/ matplotlib does better work than Sage (http://networkx.lanl.gov/ gallery.html) - the plot / plot3d / latex consistency as explained above. - work on plot options (for example, edge_colors accept only a dictionnary (color -> list of edges) which is really non natural. One would prefer a function (label -> color) or a more general function (edge -> color). The latter seems to be the best option.). - direct dot, ps, svg, gml outputs (plaintext format) without calling latex which sometimes crashes because of memory overload. - the graph_editor. There could be in Sage a java interactive editor for both 2d and 3d graphs as jmol is used vor visualization ! This could allow vertex labels, colors, ... Vincent -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
