Adobe Releases Flash To HTML 5 Converter
An anonymous reader writes "Adobe has released its Flash to HTML 5 conversion tool, codenamed 'Wallaby.' Wallaby is an application to convert Adobe Flash Professional CS5 files (.FLA) to HTML5 and its primary design goals were to get the best quality and performance on browsers within iOS devices like iPhone and iPad."
I wonder how efficient this is going to be. We don't want HTML5 to get a bunch of autogenerated bogged down code and become the next flash (performance wise, anyway).
Of course I did not RTFA, however is there any way this technology could be used to convert flash-heavy websites to HTML5, thus benefiting those platforms which don't have a flash plugin available? Linux/PPC comes to mind, but I am sure there are others. And no, Gnash and company do not even come close.
So is this the best of both worlds for all of us? Adobe can still sell Flash authoring software, while the need for their buggy plugin fades away. End users benefit from portability and (given Adobe's track record with the plugin) security perspective. There must be a catch.
I just hate it when companies end up wasting time and effort to prove Jobs right.
Adobe should have just stood their ground, and used THEIR bulk to break Apple, not the other way around.
And there was much rejoicing from the internet.
...Apple now demanding 30% of all sales and ad revenue derived from Flash->HTML5 applications.
Huzzah!
This is like MS offering a converter for Windows applications to run on Linux. I'm fine with that, although I don't get what sense Adobe sees in that help to kill off one of their cash cows.
Very nice, but where's the catch with this?
I downloaded and tested the Wallaby Technology demo on a few fla files I have.
The stop actions in the timeline don't work. Anything utilizing 3d doesn't work. The text was converted into lines (svgs). Buttons inside of buttons don't work. Videos don't play. It's Flash without all the benefits of Flash. Whats the point?
All websites display perfectly on my HP slate. Who needs backwards compatibility for the iPad anyways?
It will be interesting to see if the HTML5 code this generates actually runs faster than Flash on Linux and Mac (or anywhere else which has an competent HTML5 browser and incompetent Flash plug ins).
No ActionScript, no audio, no video... It's a good starting point, but useless out of banner scope. Then you have the HTML code openess vs. FLA decompiling.
That wasn't why we criticized Apple for refusing to support Flash, we criticized it because it was another instance of Apple telling their customers what they can do with their property. I think most of us support anything that makes Flash less viable.
And unfortunately, Adobe and Macromedia's efforts to make Flash too bloated to run on any existing system seems to have failed...
I was happier before they released this, last thing I care about is more blinky crap ads on websites.
Adobe is setting up HTML5 to be "flash-lite". Like the embrace and extend concept, they can offer more features leading people genetly away from HTML5. For example, you want to build a website but are not sure what the future holds. You could build it in HTML5 and then hope you don't get stuck with some content protection or interaction issues that demand HTML5. (e.g. maybe you think your social networking ite might someday offer simultaneous feature movie viewing that will demand FLASH DRM or something) Or you could build it in Flash and translate it to HTML5. and that will work till you really need flash, if ever. Going the other route: build it in HTML5 and then get stuck and have to rebuild it in Flash might look unappealing.
Some drink at the fountain of knowledge. Others just gargle.
ActionScript is practically JavaScript? Good god, that's like saying VB is practically C.
If I've got my version numbers right....
ActionScript 1 was an implementation of ECMAScript - i.e. the language was virtually identical to Javascript.
ActionScript 2 diverged from Javascript in that it included some elements that were being discussed for the next version of ECMAScript but never materialised (e.g. class-based OOP).
ActionScript 3 diverged a bit more (e.g. package-management stuff).
...AFAIK most of this was just "syntactic sugar" so, e.g. you can declare a class Java-style rather than creating a function and appending methods to its prototype JS-style. So cross-compiling ActionScript to Javascript should be mainly a job of translating shortcuts added in AS2&3 back into "longhand"
Of course, that's just the language - the Flash API is nothing like HTML DOM, but SVG seems a fairly good substitute for Flash's vector graphics. Pity that, unlike Apple, Android disabled SVG in their web browser (people forget that when they're ragging on iOS for not having Flash...) :-(
In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
I expected someone to come out with this, but I didn't expect it to come from Adobe. I was under the impression they were fighting HTML5 to keep flash dominant tooth and nail. Granted, I never really looked very far into their position on that.
What do I know, I'm just an idiot, right?
Any one know the link for this software???
that they release something like this... if apple thought their users were missing out, they'd support flash.
but adobe goes and does this because... why?
I found the link
http://labs.adobe.com/downloads/wallaby.html
if anyone is interested
Translates buttons, gradients, frame sets and some animation - though it generates multiple .svg's for animation. ... No more discussing pretty (annoying) Flash splash openings. Nice dynamic AJAXee navigation. But for games it's actionscript all the way. Until there's real .svg support.
This is for people who bought those (heinous) Flash templates for their restaurant/photo gallery/etc and are now horrified that the site doesn't play on iPad.
As a long time Flash guy I enjoy telling most new clients they should go with javascript/css etc
Physics is like sex: sure, it may give some practical results, but that's not why we do it.
In order to faithfully display the "new media format" a browser vendor will have to create a very compatible rendering engine.
WebKit is targetted, according to the article, but FireFox's Gecko will not be far behind. The obvious "last to support the standard" will be Microsoft and so I wonder how they will respond? Will there be an "HTML5 to Silverlight" converter? Will they pull in the WebKit rendering engine and when MSIE detects this form on HTML5 switch rendering engines? Whatever the case, failure to be compatible may get some unwanted attention.
I have few nice things to say about Apple, but I have to say that if Apple didn't take a stand against Flash, then progress away from it would be a lot slower. (I wonder what would happen if Apple decided to stop supporting IPv4?)
Like many here, though, I have to wonder how effective this conversion will be? Flash seems like a really complex thing. I guess I will have to see some results and decide for myself...
And then there are the web developers -- we want to be as compatible with everyone as we possibly can and to write it only once if possible. I have to wonder what the prevailing attitude and opinion will be?
Have they done this to try and appease the mass Youtube crashes many Linux and some Mac owners are having ?
don't like HTML5: there is no bake-in, draconian DRM.
Not at all. It was Apple trying to design the most robust mobile platform they could with decent battery life and allowing the consumer the choice as to whether they wanted to make the product their property.
"The world is a construct of forceful imagination. Those who don't know walk around in the reailties of those who do"
However, this initial version of Wallaby offers no support for conversion of ActionScript, Movies and Sound.
This is not a Flash to HTML 5 converter. As someone else pointed out, it is for banner ads.
The focus for this initial version of Wallaby is to do the best job possible of converting typical banner ads to HTML5
...and decided to commit suicide. Interesting.
If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
Although I like the idea of being able to convert Flash to HTML5, on many machines I *intentionally* block Flash because I do not want parts of normal websites having: animation, sound, movement, sucking down tons of bandwidth, CPU usage, battery use, etc.
I hope the browser designers will PLEASE give users some type of control to prevent/lower/stop animations. And before anyone mentions it: no, existing Firefox script-controlling addons (like No-Script) simply do not work for most people. They require way too much manual intervention and often leave websites relying on Javascript interactions completely broken.