Currently Webkit only (uses CSS3 animation with the Webkit prefix). Did a fairly good job on a keyframe/tween animation I'd done. There were a few problems with masked images but I imagine that could be fixed.
Most features are supported where the HTML/CSS equivalent exists. No support for any Actionscript conversion (oh if only AS3 hadn't decided to reinvent itself as Java 2 this might have been possible).
Questions:
1. How modular is the code produced? Could I easily use Flash to create chunks of animation but then control them via Javascript?
2. Will Mozilla ever support CSS Animation? Last I heard they weren't too keen on it.
Most likely targeting certain mobile platforms that don't support Flash, so that they can still claim their tool is "write once, build everywhere," even if one build target isn't.
Kudos, I'm happy to see Adobe move back towards building tools rather than platforms.
True. Compilation isn't an ideal solution however as you end up with code that's not human readable or editable. I wanted to make the point that Javascript and Actionscript used to be so similar that some form of conversion that left the code usable might have been possible.
Most features are supported where the HTML/CSS equivalent exists. No support for any Actionscript conversion (oh if only AS3 hadn't decided to reinvent itself as Java 2 this might have been possible).
Questions:
1. How modular is the code produced? Could I easily use Flash to create chunks of animation but then control them via Javascript?
2. Will Mozilla ever support CSS Animation? Last I heard they weren't too keen on it.
3. IE? Scratch that. I'm not even going to ask.