#17234: Rich output and the IPython Notebook
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.4
Component: graphics | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: R. Andrew Ohana
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/rich_output_and_the_ipython_notebook|
2d915f086b25c7c72cf1fc9d0dd441015abd9fad
Dependencies: #16996, #16640, | Stopgaps:
#17284 |
-------------------------------------+-------------------------------------
Changes (by ohanar):
* status: needs_review => needs_work
* reviewer: Andrew Ohana => R. Andrew Ohana
Comment:
A few more comments:
1. I think it would be better to have a latex output type rather than a
mathjax output type -- different backends might use different renders for
latex, (e.g. the command line currently uses the pdflatex command + a pdf
viewer). This should work fine with ipython which supports the text/latex
MIME type (which it renders with mathjax).
2. Sure, we can hold off on the show stuff for another ticket, this is
already quite big. (Note for future ticket) From talking with William, he
convinced me that `show` should be an alias for `pretty_print`, which
should always tries to use a rich output for an object (falling back on
the plain text), while the plain `print` function should always use the
plain text for the object.
3. I don't really like right now how the graphics and text are treated
very differently at the moment -- the graphics object are responsible for
creating their own output types, while the display manager/backend is
responsible for creating text output types. I would define both ascii art
and latex output as rich output rather than plain text output, and would
then move the logic for an object's rich output to the `_rich_repr_`
method of the object itself (in this case it would go into
`SageObject._rich_repr_`).
4. I'm getting a lot of doctests failing under `sage.plot` (I can attach a
log if you aren't getting them). A lot of them are fixed with changing
`tachyon.png.save` to `tachyon.png.save_as` on line 244 of
`sage.plot.plot3d.base` (this also fixes 3d plots in SageNB for me).
--
Ticket URL: <http://trac.sagemath.org/ticket/17234#comment:29>
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.
