#7298: use html5 video tag for animations
-------------------------------------+-------------------------------------
Reporter: whuss | Owner: whuss
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: graphics | Resolution: fixed
Keywords: animation, video | Merged in:
Authors: Martin von Gagern | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/gagern/ticket/7298 | 025c6c12fdaf4ac34636712b2ad5da5c315ec6e4
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by gagern):
* status: needs_work => needs_review
Comment:
Yet another rebase. Perhaps it can be merged for Sage 6.7?
Right now, I support videos if the user explicitely requests a given
format. When no format is specified, animated GIF remains the only option.
I know Volker doesn't like it if people ''have'' to specify such low level
stuff like file formats. And I wouldn't mind some sane automatic choices
based on requests of a higher level, e.g. requests for full-color output
or whatever. But getting that to work is far from trivial, so I'd ask you
to postpone any fancy automatic format detection to a follow-up ticket, so
that we can get the basic support in without getting lost in the details
of fancy automatisms.
Right now, I don't support APNG as a format for `show` yet. #16650 should
take care of that once this here gets merged. There might be some
controversy ahead that way, so again I consider it best to get this bit
here in before expanding on it.
Right now, I only support Sage Notebook, since that is all I use when
creating animations. While I could test small examples using command line
or the IPython notebook, I'm not using either on a regular basis, so I
might be missing important aspects of how they operate. I'd prefer to
merge this support for what I know, and postpone support for other
backends. I have some ideas there, but I'd be asking more input from users
of said backends, which could possibly delay things somewhat.
So please try to review this change with the scope I chose, keeping in
mind that this is but the first step in a direction aiming for more high-
level requests, more consistent support for various formats, and more
support from various backends other than the Sage notebook. Feel free to
create follow-up tickets if you want to start a discussion for one of
these subsequent steps. If this gets merged early in the 6.7 cycle, we
might get some of the other things in as well.
--
Ticket URL: <http://trac.sagemath.org/ticket/7298#comment:62>
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.
