#5975: [with patch, needs work] Implement latex output for (combinatorial)
graphs
--------------------------+-------------------------------------------------
Reporter: rbeezer | Owner: rbeezer
Type: enhancement | Status: new
Priority: major | Milestone: sage-feature
Component: graph theory | Keywords:
Reviewer: | Author: Robert Beezer, Fidel Barrera Cruz
Merged: |
--------------------------+-------------------------------------------------
Comment(by rbeezer):
Replying to [comment:18 jhpalmieri]:
Some answers.
1. Even if the right tkz-graph packages are not present on a system, then
I'd still like the user to be able to get out a proper string. I often
use Sage as a sort of Latex assistant - build an object {{{obj}}} and run
{{{latex(obj)}}} and cut/paste the string into a document. So a warning
should be useful, but an error would be too severe I feel. You ought to
be able to get legitimate Latex snippets from Sage, even if you have no
tex on your system. But if you are asking for a rendering in {{{view()}}}
or the notebook, then errors and warnings are in order.
2. Yes, I think the documentation is out-of-sync with the above, since I
pulled some warnings at the last minute. I'll fix that.
3. The code snippet
>
{{{
sage: g = graphs.CompleteBipartiteGraph(1,3)
sage: g.latex_options(tkz_style = 'Art')
}}}
should have no immediate ovious effect or output. But {{{latex(g)}}}
should differ if run before and after these commands - afterwards it
should have the tkz-graph commands to use the pre-built "Art" style,
rather than the default "Normal" style.
4.
> In the following, the nodes are overlapping, and it doesn't look good.
It looks like there is room to space them out more:
{{{
sage: g = graphs.CompleteBipartiteGraph(1,15)
sage: view(g)
}}}
Eventually the user will have control over vertex sizes, bounding boxes,
and vertex locations. The intent of this patch is to get the
infrastructure right for changing options, then many, more localized
changes, will open up more control. So I think this can slide for now,
but this sort of control should be first on the list of changes.
5.
> Finally, I found the documentation not as helpful as it could be, partly
because it was scattered around.
Great suggestions. I'll spruce up the documentation when its not so late
in the evening sometime tomorrow night and get up a patch with that, plus
other suggestions.
Thanks,
Rob
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5975#comment:19>
Sage <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
