#18289: Revert the changes that #17821 made to graph/
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.7
      Component:  graph theory       |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:  Nathann Cohen
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vbraun/faster_output_for_large_graphs|  
e9e7759f34e46e610f9f477e433919893973cf37
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by ncohen):

 > But when the user types
 > {{{
 > sage: g = compute_some_graph()
 > sage: g
 > }}}
 > then they do not want a picture? The displayhook is just an implicit way
 of telling the UI to show something.

 A plot is just 'one representation' of a graph. Like for posets, for
 matrices (they have a .plot too). I type 'g' very often just to see
 whether this variable that is named 'g' in indeed a graph (as you would
 for any other Python object), but also because it tells me whether that
 graph allows multiple edges or loops.

 This being said, like Vincent I expect that the expected behaviour is
 different in the notebook. If you want to improve that side of the
 interface, however, I believe that it might be better to output *both* in
 the notebook:
 - The one-line description that we have in the console
 - A drawing

 Of course, not being able to plot large graphs is a problem. So like for
 matrices, perhaps a size limit may be good.. But really, most graphs do
 *NOT* look good when you plot them, and the result may appear very very
 very unprofessional, which is probably something you want to avoid:

 {{{
 sage: graphs.RandomGNP(50,.5).show()
 }}}

 Perhaps the default layout can be slightly improved, but I have no idea
 how to solve the performance problem with matplotlib.

 > Unrelated to this ticket, but I agree that we don't want huge tikz
 output.

 Why is that unrelated to this ticket? Didn't you say that this change
 (from picture to latex output) had been made by #17821?

 > Bonus points if you can guess correctly what happens without trying it
 out (I could not)

 With this branch applied it gives me the latex code `O_o`

 Nathann

--
Ticket URL: <http://trac.sagemath.org/ticket/18289#comment:45>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to