#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 | 2f6a6703ba31efa50c24b8eab742151ac5adbd25
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by gagern):
The recent changes from #17234 interfere heavily with my work here.
I'm working on a rebase just now (which is somewhat annoying, considering
that this ticket is waiting for review for 9 months now, and this is the
third time I have to rebase it). But in some points I'm not certain how to
integrate my goals with what #17234 did. For video, there are different
formats to choose from, no single format will satisfy everybody, so I
needed some flexibility there. On the other hand, almost all the different
formats are the result of passing some PNG frames through ffmpeg,
providing a suitable file name for the output, and then writing a HTML tag
to embed that file. So all I need to know about a video format is a file
name extension which ffmpeg will recognize and a mime type which the
browser will recognize. I can even obtain one of these from the other
using `mimetypes.guess_extension` resp. `mimetypes.guess_type`.
Now #17234 introduced the rich output type catalog, using yet another way
to name types, and as far as I can see at the moment without hookups to
either file name extensions or mime types. But what seems worse to me is
that this catalog is an explicit list of allowed types, with no obvious
room for extension at runtime.
* Should I restrict users to e.g. Theora and WebM as video formats?
* Should I add some `OutputAnyVideo` class to catch all cases?
* Should I dynamically create new classes, one for every user-requested
format?
* How about support for more than one format, should we introduce a type
which generates a bunch of common video formats (e.g. again Theora and
WebM) to plug them into a single `<video>` tag so the browser can pick
what he likes best, at the cost of increased conversion time?
Judging from e.g. the handling of LaTeX output, it looks as if I could
simply generate HTML and have that recognized by the notebooks. I hope
that's the case. I'll have to look whether embedding animations into
tables still makes sense, but I hope it does.
--
Ticket URL: <http://trac.sagemath.org/ticket/7298#comment:48>
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.
