#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):

 Replying to [comment:53 vbraun]:
 > Distinguishing between lossy / lossless compression for graphics is
 reasonable, and doesn't require the user to know what webm&apng is.

 Distinguishing between the color-reduction losses of GIF and the
 frequency-domain compression losses of WebM and Theora does, in my
 opinion, indeed require some knowledge of formats. Sure, I won't mind if a
 polyfill-supported APNG becomes the lossless and shiny default, so that
 only the tech-savvy people ever have to make such a distinction.

 I'd say that on the one hand, noone should be forced to make any format
 decision for elementary work (small 2D animations with few colors), but
 those who have the knowledge to choose a format should also have the power
 to get things displayed in their format of choice. I don't want to force
 anybody to save stuff to a file and open it in a different application
 just because showing it in line would offer too many choices.

 By the way, how are chances that every browser-based notebook will
 reliably detect whether the browser supports WebM, Theora, or perhaps even
 something else which FFmpeg already supports but Sage does not know about?

 I'd go a step further: there are many ways the animation composition might
 be tweaked. For ffmpeg videos you might control a million settings, bit
 rate probably the most important one. For GIF via !ImageMagick there are a
 number of steps one can perform to achieve smaller and better files,
 reduction to a global color table foremost among these. I'd like to one
 day offer all of this power to the user, so he can pass ffmpeg command
 line switches or enable !ImageMagick optimizations, whether he's saving to
 disk or viewing in browser. If you don't believe in “right click to save”,
 then you can still consider the “view in browser” as a preview to what
 will be saved to disk.

 With the changes I had here, passing `**kwds` from `show` through `save`
 all the way to the format-specific methods, where additional options could
 be introduced as needed. Now if you claim that the user shouldn't even
 have control over whether the animation goes through FFmpeg or through
 !ImageMagick, that approach doesn't make that much sense any more. I want
 to keep my power to choose.

--
Ticket URL: <http://trac.sagemath.org/ticket/7298#comment:56>
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.

Reply via email to