The full source code of Apparat is now available at GoogleCode. It is the whole framework behind TDSI and Reducer.
Apparat is released under the GNU Lesser General Public License. Please contact me if you want to contribute to this project. Maybe someone is interested in writing an Ant task for Reducer? I am also happy to receive feedback if you have used the framework to build something cool with it.
Please join the Apparat Discussion Group if you are interested in collaboration.
Could this aid development of something like Loom, a bytecode weaving AOP project for AS3? http://code.google.com/p/loom-as3/ There has been no code posted yet but it seems like maybe Apparat could help?
Here is a simple ANt-Task to call Reducer:
Could be configured with defined properties.
Thanks for this great tool !
quarkus: Sorry but WordPress strips all XML tags. For the Ant Task I was thinking about a Java solution.
Exciting exciting exciting! Let’s see where this goes.
You really are becoming the Luke Skywalker of better as3/abc.
For Reducer, it seems there is no way to set individual quality factors for different bitmaps – and maybe it’s a tricky task. When parsing the file, is there a way to find the original bitmap file’s name, so that one can match each DefineBitsLossless2Tag with an argument sent to the Reducer tool?
Thanks!
The original filename is lost after exporting a SWF. You could write a GUI that shows each picture and a quality slider right next to it. In that case it is no problem to have individual levels. But I do not see this option for the command line now.
I feared as much. Do you know, though, if the mxmlc preserves the order in which the [embed]‘s were found when generating the swf? That would let me achieve the same result (for the “Embedder” tool I’m writing).
Sorry Jonas, I have no idea about the order. Especially not when you think about other libraries that are embedded as well and they contain embeds too.
I can confirm that it does not keep the order even in flat structures, and I can’t see any pattern either.
For my purposes, I guess I could identify them by checking pixel size and/or pixels with the list of files I’m sending to my tool, but it’s not a pretty solution.