Slashdot Mirror


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."

19 of 168 comments (clear)

  1. Finally, but by Anonymous Coward · · Score: 2, Insightful

    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).

    1. Re:Finally, but by fuzzyfuzzyfungus · · Score: 4, Insightful

      Only time will tell, in terms of Adobe's specific implementation; but given that Flash consists of Actionscript(practically Javascript), bitmap and vector graphics(canvas/SVG), A/V decode support for specific codecs(HTML5 video), and flash cookies/data storage(HTML5 local data store), there is no broad reason to expect that HTML5(at least in the medium term) shouldn't be able to do the majority of Flash stuff(omitting specific cases like some special streaming capabilities and DRM) with efficiency on roughly the same order as Flash(better if the browser maker is more competent/platform integrated than Adobe, worse if they are less competent, or if Adobe's conversion tool produces pathological code)...

      Unfortunately, drawing lots and lots of fancy vectors with an interpreted language is always going to be more computationally expensive than more... restrained... tastes in web design; but at least it won't all be crammed into a proprietary runtime with a ghastly security record...

    2. Re:Finally, but by VGPowerlord · · Score: 4, Informative

      ActionScript is practically JavaScript? Good god, that's like saying VB is practically C.

      If VB and C were based on the same standard, you might have a point.

      Recent versions of JavaScript and ActionScript are both (partial or complete) implementations of ECMAScript version 3.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    3. Re:Finally, but by TheRaven64 · · Score: 3, Interesting

      You're confusing two different issues. Adobe has an incentive to add new features to the Flash authoring tools, much less incentive to improve the plugin: it doesn't directly generate revenue and it's got no competition.

      If HTML5 support matures a bit more, Flash Professional will probably evolve into an HTML 5 rich content authoring platform. This is great from Adobe's perspective - they get to keep the profitable bit (the authoring tool) and let other companies absorb develop their their loss leader.

      Flash Player is currently a strange beast. It has some amazing technology (the JIT compiler is pretty impressive), and some really hideous legacy stuff (like doing colour space transforms and compositing entirely on the CPU, because that made sense 15 years ago) that cripples performance. There's no incentive for Adobe to rewrite the legacy parts that are 'good enough', but if Mozilla's canvas implementation is significantly slower than the one in IE or WebKit then they lose marketing points so they have a strong incentive to improve it.

      --
      I am TheRaven on Soylent News
    4. Re:Finally, but by fean · · Score: 2

      You're suggesting that Adobe hasn't 'improved things', when in fact, they've been releasing new versions faster than ever before. 10.2 was just recently released, with support for 'StageVideo', allowing HD movies to be rendered via the graphics pipeline, giving native performance because it uses your hardware.

      They improved their cursor support, hooking into the OS to provide 'native' cursors, rather than just drawing them in Flash.

      IE rendering speed was increased by 33% due to new hooks into their 'native' graphics pipeline, they improved their OSX integration, however they didn't release performance numbers.

      Their sub-pixel rendering has been updated, removing optimizations for CRTs, giving crisper, cleaner lines on IPS displays.

      10.3 beta was just announced, which will provide echo cancellation for audio input, improved analytics for video-based sites, integration into browser privacy settings (no more super-cookie), and a 'local' settings panel for all Plugin settings.

      Also on their labs site is their 'incubator', which provides a full and true 3D rendering API, though the release date for this has not been announced.

      So, while you can speculate on what their incentives might be, you certainly cannot fault Adobe for not updating and improving their plugin.

  2. Re:Good news for linux? by RobbieThe1st · · Score: 3, Informative

    You mean like say... Smokescreen? http://smokescreen.us/
    Looks like exactly what you want, though it seems a bit slow on my cellphone.

  3. Is a subject really necessary? by LizardKing · · Score: 2

    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.

    1. Re:Is a subject really necessary? by gmueckl · · Score: 2

      There is a simple catch: performance. Some parts of Flash are really highly optimized (like the vector rendering engine - yup, that was once the primary purpose of the whole beast...). I highly doubt that any potential HTML5 counterpart to these parts reaches even remotely the same performance. End result: choppy animation, poor battery life, you name it.

      --
      http://www.moonlight3d.eu/
    2. Re:Is a subject really necessary? by dingen · · Score: 3, Interesting

      Why wouldn't browsers be capable of the same level of performance in rendering vector graphics as Flash? Especially since hardware acceleration is already implemented by most browsers on most platforms and Javascript engines are already highly optimized, creating smoother canvas / SVG animations could well be the next big thing browser developers will aim for.

      --
      Pretty good is actually pretty bad.
  4. Re:Meh by Galestar · · Score: 3, Insightful

    You must be new here. Adobe has come out publicly and said that HTML5 doesn't scare them because they know their plugin does not have much of a future. They want to sell authoring software, that is their entire business model. As far as Apple is concerned I don't think they really care what SJ has to say one way or another.

    --
    AccountKiller
  5. Re:I'm amazed by tixxit · · Score: 2

    What, exactly, about Flash do you think Adobe makes money on? It isn't the free Adobe flash player, but rather the tools to create content for the flash player. Adobe knows that HTML5 will be a mean competitor, so why wait while it gains momentum? If you can't beat 'em, join 'em. They'll still get lots of sales for their HTML5 compliant authoring tool that lets artists make cool, inaccessible, fancy things, rather than forcing companies to hire a JavaScript Guru to do the same thing.

  6. Re:I'm amazed by trollertron3000 · · Score: 2

    I would bet that they would gladly give up their flash player because they don't really sell it. If you think about it the world is doing Adobe a favor by providing a file format and viewers for the content created by it's tool sets, that it actually sells. They sell their creative tools, the flash player was always needed to provide a way to view these creations. Now that HTML5 can accomplish much of this they see a way out of the constant development on their player.

    Steve Jobs probably thought he was punching them in the balls, but in reality he just handed them more cash. The adobe creative suite is on almost every designer machine in the western world. "Flash", meaning SWFs might be going away, but the creative tool sets are here to stay for a long while. Then throw in their new "Flash Builder", aka Flex, and you have a powerful set of tools. That's what they sell.

    --
    Tiger Blooded Bi-Winning Machine
  7. Re:Meh by Galestar · · Score: 4, Insightful
    Aha here it is Interview with Kevin Lynch, CTO of Adobe

    Q: How is Adobe going to react to HTML5?
    A: I wouldn’t say reacting to HTML5. We see whatever people are using to express themselves. We’re going to make great tooling for HTML5. We’re going to make the best tools in the world for HTML 5.

    It’s not about HTML 5 vs Flash. They’re mutually beneficial. The more important question is the freedom of choice on the web.

    --
    AccountKiller
  8. Not that silly... by itsdapead · · Score: 4, Informative

    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.
  9. Re:Inverse Embrace and extend by mcelrath · · Score: 4, Informative

    OTOH, Adobe makes their money from selling Flash authoring tools. I'm sure they couldn't give a crap less what the target format for their tools is, if people still buy their authoring tools. Being able to dump the expense of maintaining and distributing the Flash player, but still selling authoring tools that output HTML5 and let Flash slowly die? Sounds like a damn good business decision.

    --
    1^2=1; (-1)^2=1; 1^2=(-1)^2; 1=-1; 1=0.
  10. Re:Interesting. by Skidborg · · Score: 2

    Adobe makes their money on the flash authoring tools, not the player. The more things that their tools can be used for the better.

    --
    Supporter of the +1 Over Dramatic mod option. In memory of apk.
  11. Re:Good news for linux? by creepynut · · Score: 2

    Great suggestion! Have you ever tried it? A colleague and I were looking at Smokescreen and some other similar projects when we wanted to an old page with some Flash for a client working on the iPad.

    Smokescreen looks fantastic in their demos, but they don't make it available for download anywhere and the last update to their site was nearly a year ago. This was a post "weeks" before they get the source code out. Hopefully eventually it is out eventually because it seems like a great project.

    By grabbing the JS source we did try to demo it with a few pages and it croaked. It might be that our SWF files were poorly coded, we didn't create them. I suspect this might be a case similar to IE rendering bad code correctly while other browsers croak.

    The other major problem is that this kind of solution needs to be implemented by the web author. I can't "install" this on my iPad and hope all Flash content magically works.

    Another script we tried was called Gordon (src: https://github.com/tobeytailor/gordon/wiki/). Unfortunately this only works with Flash v1/v2 SWF files.

    Both Gordon and Smokescreen render SWF files in the browser which is great if this is all you have. I certainly imagine this Adobe one that compiles some HTML5 code from the Flash source file works better.

  12. Re:Meh by cmburns69 · · Score: 2

    They're both turing complete languages. From a technical perspective, there's nothing Javascript can do that can't also be done in Basic.

    Of course, Actionscript has some nice features that JS doesn't have-- like optional strong typing and automatic closure context. It's true they're both (mostly) syntactic sugar, but they're really nice to have when you need them and they don't get in the way the rest of the time.

    --
    Online Starcraft RPG? At
    Dietary fiber is like asynchronous IO-- Non-blocking!
  13. RTFA PLEASE!! NOT really a Flash to HTML converter by MobyDisk · · Score: 2

    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