#12827: Expand Animation class to accept more graphics types
-----------------------------------------+----------------------------------
Reporter: niles | Owner: jason, was
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.0
Component: graphics | Resolution:
Keywords: animate, graphics, 3D | Work issues: docstrings, testing,
think about img protocol
Report Upstream: N/A | Reviewers:
Authors: Niles Johnson | Merged in:
Dependencies: | Stopgaps:
-----------------------------------------+----------------------------------
Comment (by gutow):
My take on this is that G.image() should return an image object. I
haven't looked at PIL, but I would expect an image object to have a
publicly accessible .type value that tells the image type and a .data or
.imgdata that contains the binary representation of the image. I would
suggest that we want graphics objects to have two routines G.image(type
=XXX, height=XXX, width=XXX, **kwds) and G.save_image(type=XXX,
filename=XXX, height=XXX, width=XXX, **kwds). I suppose the height and
width could have default values. G.save_image should return a success
value, but raise an exception on failure.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12827#comment:6>
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.
