Google Swiffy currently supports a subset of SWF 10, ActionScript 2.0 and ActionScript 3.0.

Although this imperative approach might be less efficient, the level of control it provides is required to match all SWF functionality. We have therefore chosen to use JavaScript to animate SVG on the client. Finally, these standards are not widely available: The CSS animation specification is still in working draft state, while SMIL is not implemented in the Internet Explorer browser. Mapping these definitions back onto CSS or SMIL transitions is not always possible. Another limiting factor is that animation in the SWF file itself is not defined in terms of high-level transitions, but defines the position of every object at specific keyframes. For example, although the concept of keyframes exists in CSS animation, it does not provide a mechanism to synchronise the JavaScript code to those keyframes or to modify the timeline from JavaScript, which is a basic feature required for SWF compatibility. However, both technologies provide insufficient control over the animation when support for ActionScript scripting is required. At first sight, both CSS animation and SMIL, adhere to our design goal of using a declarative representation when possible. The choice of SVG for rendering leaves us with several options to animate the SVG content. The Swiffy thesis (2012) explains its general approach in the following way: : 15 This representation is in turn converted into SVG in the web browser via JavaScript, which is also used for animations.

A closed source web service hosted by Google converts SWF to an intermediate representation serialized as JSON.

Fdt external swf viewer