#18176: Show animation
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  critical           |    Milestone:  sage-6.6
      Component:  graphics           |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vbraun/show_animation            |  39263a4fc8c59879373a47d55a9040a5d6702de9
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by gagern):

 When was the last time you had a Sage-generated movie play at a cinema in
 your parts? On a more serious note, I believe that `delay` makes a lot of
 sense if one speaks of a number associated to individual frames, but less
 so if it's the same for all of them. Which is a reason why `delay` makes
 more sense in a GIF environment than an MPEG one.

 `show` does go through `save` only since your
 
[http://git.sagemath.org/sage.git/commit/?h=7747261d04e4ff0105fb514a2109b2d014396e2a
 commit 7747261]. It was calling `gif` before that. In
 
[http://git.sagemath.org/sage.git/commit/?h=dc0067dbd358313ffaf58119e32a18f5ee5872df
 dc0067d] for #7298 I had written a code path which routed `show` through
 `save` without breaking such stuff. Unfortunately, #7298 won't merge since
 it conflicts with your changes, and I haven't yet found the time to
 rewrite it appropriately.

 Test coverage is tricky. Since we don't bundle imagemagick, we can't rely
 on `convert` so we can't create GIF. The same holds for ffmpeg and the
 various video formats. And even if we had these tools enabled, how do we
 automatically verify that the file looks as it should? I guess we could
 disassemble the file to some textual representation of all its settings,
 but that would require considerable amounts of code. Or we could set up
 something like Selenium based tests. Although it's hard to get timing
 right with those. But I'm against punting a useful feature just because we
 can't auto-test it as well as we'd like.

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