Next up, endless complaint about how Adobe's javascript code is slow, or they're doing something horrible to the canvas or some other B.S.
(I can't wait for my quad core computer to grind to a halt with dozens of unblockable canvas advertisements wallpapering every website I go to from now on...sigh, the end is near)
If anything it should be easier to block them as it's simpler to inspect the inside of a javascript/canvas banner than a flash one, from the context of a browser extension.
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.
1 is impossible because Adobe does not control the platform.
2 isn't really possible since Adobe could easily be proven wrong. Adobe is very much in favour of HTML5, and they only care about their development tools. By releasing a converter, they improve their expensive toos.
Adobe makes authoring tools, and directly makes no money on Flash Player: If advertisers need a way to attack every iOS user with ads, Adobe wants to be there with a tool.
However I laugh at point #2 -- it is simply inconceivable that Flash, with over a decade of a head start in heavy animation, actually does look better in many cases (which it does) -- it has to be FUD.
However I laugh at point #2 -- it is simply inconceivable that Flash, with over a decade of a head start in heavy animation, actually does look better in many cases (which it does) -- it has to be FUD.
I don't think the FUD was that things will look better in the original Flash. That really only would make sense. The FUD was that "Oh, this thing that converted my Flash into HTML5 looked like crap afterward; therefore HTML5 must be crap", when it could really be an issue of the conversion process rather than HTML5 itself.
>"Wallaby" is the codename for an experimental technology that converts the artwork and animation contained in Adobe® Flash® Professional (FLA) files into HTML.
Not quite as exciting as a SWF -> HTML5 converter. I wonder about the feasability of that.
Testing it out, it seems to be a dialog that accepts .fla files and tells you it can't convert them. At least that's all I could get it to do with any of my Flash projects.
Has anybody managed to find a subset of Flash that it will actually convert?
Is it possible to do anything with that apart from run the existing Smokescreen demos? There's nothing on the site that refers to anything having shipped or even a target ship date.
How about Actionscript 2? Flash basically has two VMs . . . one is used to run legacy content (up to Flash 8, AS2), the other for newer content (Flash 9+, AS3).
But my reading of the project page suggested it was just converting graphical and animation elements in .FLA files.
Then it's not Flash. I really don't have a need to convert any animations from 2002 into the hippest standards. I've never thought to myself "Boy, All Your Base is still really funny, but if only the underlying technology that powered it was open and modern....."
What don't Adobe get? It's not that Flash is bad "just" because it's not HTML5, it's also bad because it enables crap things. HTML5 or not, that's always going to be the case.
This kind of knee-jerk anti-Flash thing is getting tiresome.
We get it. You don't like animated ads. I don't like them either. You can make annoying animations using any technology.
Are you seriously implying that animation/interactivity in general is a bad thing? I seriously doubt that. Stop blaming the tools. Use Adblock and get over it.
Flash is great when used for the right purpose. HTML is great when used for the right purpose, too. Some may overlap; no problem as competition is good for tech.
What bothers people is the fact that sometimes entire websites that would work perfectly in HTML are built in Flash.
I quite agree but Apple's anti-Flash play has almost certainly made this a thing of the past.
OP seems to be saying something different and altogether less defensible: "Anything made with Flash is bad". This is denying an entire range of applications that are currently unfeasible with HTML-based technologies.
I should have said "encourage" instead of "enable". And it's not a knee jerk reaction, I've been anti flash for years. I used to make my money exclusively as a flash designer/developer. And of course I'm not implying what you suggest.
I struggle to find a different interpretation of your statement even with the word substitution you suggest.
I've seen astonishing creativity from the Flash community over the years in the areas of games, UI experiments, generative art to name a few. Do you remember when Javascript had the same soiled reputation? DHTML anyone?
But it's not skilled users using it? Nor is it an informed public using it. Even if those two ingredients did come together, Flash itself would still be a resource hungry, unstable dog.
(I can't wait for my quad core computer to grind to a halt with dozens of unblockable canvas advertisements wallpapering every website I go to from now on...sigh, the end is near)