From the site: Macromedia recently opened up the file format for their SWF movies. Despite some rather horrific errors in the original spec, reverse engineering has been done and a correct version, along with an updated version of swfparse.cpp, an app for parsing SWF files. SWF is a vector based movie format which has become the de facto standard for web based animations. Unfortunately, unless you buy the very expensive 'Generator' from Macromedia it cannot interact with the user at a CGI level (so for example, you cannot type in your name in a form and have that appear on the screen). I started this project when the company I work for was looking into dynamic Web based animation. Mark Fowler (who owns TwoShortPlanks, cheers Mark), who'd been doing a lot of work with Java and Flash, came up with the idea of decompiling SWF files to XML. We talked about it a bit but nothing really came of it. Since I have to do an individual, final year project at College however the idea came up again. However it has been expanded. The plan now is to have a Flash::Object which is an internal representation of an SWF/Flash movie. Tags (and hence objects) will be able to be manipulated, added and removed. In this way it will be possible to create an SWF file from scratch. In addition the object can be 'loaded' by any number of filter modules. The most obvious input filter is an SWF file but others could include * XML * Out put from SWFparse In the same way the object can be 'dumped' via any number of output filters. Again, SWF, XML and SWFparse are the obvious filters but one interesting one would be to have something that dumps a Perl script which, when run, would create the SWF file from scratch. I also plan to have variable substitution, so that when you create your SWF file you could have a text string which has something like "hello $name" in it. By loading this into an SWF object and then doing a call like $swf->substitute('name','simon'); and when the SWF file was dumped the text would read "hello simon". All feature ideas are gratefully received. Reproducible: Always Steps to Reproduce:
I'm closing this one out as invalid, but let me explain why it's not valid first. * Big one for me - you didn't give us anything to work with. Never mind that we don't add modules to the tree without some form of justification, all you gave us was a URL. * The upstream site hasn't been touched in 5 years. Unlikely to get any form of support on any bugs that crop up. * Upstream doesn't offer an installable package of any form. Great effort and all, but all I could find were a loose collection of module files - no framework to work with without putting in a bit of effort on my end. Sorry, Mike
