#11266: Wrapper for R graphics commands.
---------------------------+------------------------------------------------
Reporter: JoalHeagney | Owner: was
Type: enhancement | Status: new
Priority: minor | Milestone: sage-4.7.1
Component: interfaces | Keywords: R, graphics, cairo, wrapper
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
---------------------------+------------------------------------------------
Comment(by jason):
We use rpy(2?) (http://rpy.sourceforge.net/rpy2.html) in order to interact
with R. I wonder if there is an easy to modify it to do what you suggest
with saving graphics.
I agree with your last point; I wonder if the effort to implement the
caching (plus its reliance on specific notebook behavior) is worth the
benefits it provides. Of course, I'm not a heavy R user, but even as far
as Sage graphics go, we don't do that sort of copying between cells---I
think it would be practically impossible for us to tell if a graphic in
one cell should be exactly like the graphic in another cell without pretty
much generating the graphic anyway.
Your Rcommandlist class is turning into what looks like just a function.
How is better than something like defining a function, which also is a way
of storing a sequence of commands:
{{{
def myplot(argments):
r.boxplot(arguments)
r.lowlevelfunction()
r.dev_off()
myplot(arguments)
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11266#comment:9>
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 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.
