Forgot your password?

typodupeerror
Graphics Mozilla Software

Mozilla's Open Source Project Shumway To Translate SWF To HTML5 57

Posted by timothy
from the why-don't-you-render-off-site-and-pay-for-it? dept.
An anonymous reader writes "Mozilla currently has an experimental project on github called Shumway to try to interpret SWF (aka Flash files) using browser-standard technologies like HTML5 and JavaScript. All I can say is please and thank you! 'Shumway is an HTML5 technology experiment that explores building a faithful and efficient renderer for the SWF file format without native code assistance. Shumway is community-driven and supported by Mozilla. Our goal is to create a general-purpose, web standards-based platform for parsing and rendering SWFs. Integration with Firefox is a possibility if the experiment proves successful.'" It's not the first such attempt; here's a post from a few years back about one called Smokescreen, and another about QuickTime programmer Steve Perlman's subscription-based workaround for iDevices.
This discussion has been archived. No new comments can be posted.

Mozilla's Open Source Project Shumway To Translate SWF To HTML5

Comments Filter:
  • Google Swiffy (Score:5, Informative)

    by aaron44126 (2631375) on Tuesday June 05, 2012 @09:35AM (#40218589) Homepage
    Google has a project going along these lines, called Swiffy [google.com]. Looking at the demos [google.com], it appears to work pretty well.
  • Re:Yeah right.... (Score:4, Informative)

    by tlhIngan (30335) <slashdot&worf,net> on Tuesday June 05, 2012 @11:42AM (#40220087)

    Quite funny how Steve Jobs decided not to support Flash on iOS because it was such a resource hog, consuming way too much processor power, and now people are going to try and get around that restriction by... making a flash interpreter in html5 :-)

    Except it's a lot easier for a browser to control resource usage by controlling its renderer and interpreter than blindly giving cycles to a black box plugin (which is how plugins worked - by sending periodic events to embedded plugins to let them process).

    And a browser has a lot finer grained security and privacy controls - if you say a site may NOT store a cookie (like Google DoubleClick), they can always use Flash as a workaround to that because Flash doesn't have easy support for it (it's all cookies, no cookies, or "annoy the hell out of me"). In the browser, you say no and the browser ensures it. Flash fixed that but it's still ages behind modern browsers.

    Heck, a browser can also let you "do not run any javascript or other crap from doubleclick" but Flash will just happily load it up if the SWF references it.

Hey, diddle, diddle the overflow pdl To get a little more stack; If that's not enough then you lose it all And have to pop all the way back.

Working...