Thanks for the positive feedback. I fixed the redraw bug in Processing JS, so now it redraws only when something is moved (no more CPU drainage).
I will try to work a bit this weekend on the user-interface. I see some great suggestions by Rob, that are straight-forward to implement. I don't do much graph theory, so if you've seen good graph editor interfaces, send me a link for inspiration. Adding a context menu on vertices and edges can possibly be done with jquery overlaying elements, but I would like to keep the interface all canvas (keep it simple for now). Also it shouldn't be hard to add the sage: g = graph_editor() functionality by making calling a jscript to open the editor in a new window and passing the graph as a python dictionary (which is readily available). I will add a js parser that would construct the graph given a python adjaceny lists dictionary. The graph_editor window will have a button "back to sage" which would send the new python dictionary back to sage (I already have included the code that makes a python dict string out of the graph). I would need some help on this by someone who understands exactly how the notebook works (don't want to break something else). What might be even better is to send a particular embedding to the editor (i.e. send the adj. lists + vertices coordinates), but I am not sure if this info is easily extractable (in simple (x,y) form) from the graph theory libraries. Rado --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
