<p><pre><code> The source code is a bit of a mess, but if anyone is
interested in the non-bookmarkletized code, I can upload it
somewhere.
</code></pre>
How about hosting the source code on GitHub? I'd love to see how this works!
How strange. Until last month, I was running gifexplode.com, a site where you could share 'exploded' gifs - i.e. it took an animated gif and stepped over it frame-by-frame. I took the service offline last month because people were using it to store porn. I had tried finding a client-side solution in vain. The long-term plan for gifexplode was to introduce a player just like this!<p>Soon as I get a chance, I think I'll relaunch gifexplode with your viewer.<p>Here's the blog post about how gifexplode was born, it's quite an interesting story: <a href="http://www.puremango.co.uk/2009/08/gifexplode-community-powered-web-development/" rel="nofollow">http://www.puremango.co.uk/2009/08/gifexplode-community-powe...</a><p>edit: Hmm, using XHR to fetch the gif will give me cross-domain issues unless I first mirror the image on my server. Anyone know of a way around that?
Some really clever work there.<p>Add a timeline slider and it's really usable!<p>ps. for those wanting to read the source more easily,<p>paste the bookmarklet into <a href="http://jsbeautifier.org/" rel="nofollow">http://jsbeautifier.org/</a>
I like this simply for the content on the page, not necessarily the actual project (tho it's cool too). It's snarky, self-deprecating, and dryly funny.
I made a similar Chrome plugin called GIF Scrubber: <a href="https://chrome.google.com/webstore/detail/gbdacbnhlfdlllckelpdkgeklfjfgcmp" rel="nofollow">https://chrome.google.com/webstore/detail/gbdacbnhlfdlllckel...</a><p>It also uses a canvas element to render each frame but it does support weird disposal methods. You can see the (very sloppy) source by just viewing the source of the plugin window.<p>You mentioned getting test images for the disposal methods and I found these to be very helpful: <a href="http://algif.sourceforge.net/#18" rel="nofollow">http://algif.sourceforge.net/#18</a><p>I'd also recommend using some kind of movie player-style control like I used and some kind of "explode" function. They both proved popular.
This is the way forward for codecs on the web. Alan Kay has previously complained about how dumbed-down the browsers are in comparison to the possibilities of mobile code, and that's now starting to become less true.<p>The next step beyond that is to provide browser extensions for programming network protocols. One-way HTTP over NAT sucks, web-sockets do not and will not work.<p>We're starting to come back around to the vision of the Internet in the 80s - multi-protocol, multi-host (if you're on the web, you can be a server), mobile code via bytecode (or source code), and with pervasive remote access (VNC and X11/NX).
Nice! I was swearing at Wikipedia's animation of a flipflop a couple days ago. Downloading and fiddling with 'convert' was substantially more annoying.