Slashdot Mirror


Adobe Flash CS5 Exports Animations To HTML5 Canvas

An anonymous reader writes "Adobe's Flash CS5 will seek to make the Flash runtime less relevant with support for exporting animations to HTML5 canvas. Seth Weintraub from 9to5mac writes, 'In a previous post, I'd wondered why Adobe didn't spend its time building HTML5 authoring tools rather than putting so much time/energy/money into its Flash -> iPhone Apps exporter tool for Flash CS5. As it turns out, Adobe does have some, albeit rudimentary, HTML5 Canvas exporting tools, as demonstrated in the video above.'"

20 of 166 comments (clear)

  1. Next step: Apple bans HTML Canvas by Cyberax · · Score: 5, Funny

    Next step: Apple bans HTML Canvas except for animations approved personally by Steve Jobs.

    1. Re:Next step: Apple bans HTML Canvas by ukdmbfan · · Score: 4, Interesting

      In which case, you could take Steve Jobs' comments at face value, and it is just about the fact that Flash is crap, buggy, memory-hogging and inadequate to be run on a low-power, low-spec'd mobile device.

      --
      "If you do things right, people won't be sure you've done anything at all"
    2. Re:Next step: Apple bans HTML Canvas by auLucifer · · Score: 4, Interesting

      My bet would be, like most engineer posts I have seen, is flash sucks on the mac. It is apparently by far the most reported issue by the mac crash report, it is slow and very resource intensive so not likely to give a very good experience on the iphone. I don't have a link but that's what the engineers inside apple say. With the stamping out the flash compiler though perhaps it's grown to be something more ...

      --
      If I was witty I'd put something funny here but, as it stands, I am not and have just wasted seconds of your life
    3. Re:Next step: Apple bans HTML Canvas by Anonymous Coward · · Score: 4, Informative

      HTML5 Canvas is only as slow as the JavaScript engine in the browser in question...

    4. Re:Next step: Apple bans HTML Canvas by Tei · · Score: 4, Insightful

      It will take years to optimize HTML5 to something comparable to Flash. And maybe it will still be a bit slower than Flash. The point is not speed. The point is not scripting. Scripting is as bad if not worst, than a binary stream vectorial format. The points is a document model, that is easier to examine by bots and archivers, that can be modified by external tools, that can be linked, and all the good and cool features we have learn a Hyper Text have.

      A binary stream of bits that render vectorial stuff is not fun, because you can't do much with these bits. A greasemonkey script is fun, google page rank search engine is fun.

      Even if Flash is fast, a what price?, you have to support a separate things, with his own memory management and probably bugs. And is not that good either, Linux users have bad experience with Flash banners that take the 100% of the CPU.

      Having everything following the document model (dom), any optimization made will touch all. Any optimization on the memory handling will affect all. Any safety mechanism. Updating the browser will update the rendering of such canvas thing, or svg thing.

      I don't think Flash game dev's will move to HTML5 in 5 or 8 years. Flash will still be more interesting. But there will be a "leak" of the good features of Flash into the web, so the web will get whatever good we have learn from Flash. So Flash will not be required for some things. At a point, you will not *need* Flash. Needing Flash is *mucho* wrong, and we DO NOT WANT.

      Some people will argue that "Flash-like" features in the web are bad news. These people are right. Animated banners in HTML5 are not better than in Flash. But with a better model, these will be more easy to control, limit, optimize.
      And people want these Flash features. I serve no one to ignore that Flash add value to the web. We will steal (with HTML5 and SVG and Canvas) part of these value, to make the web AWESOME.

      --

      -Woof woof woof!

    5. Re:Next step: Apple bans HTML Canvas by PenguSven · · Score: 4, Insightful

      Yes, people are abusing Canvas just like they abuse Flash, but at least with Canvas, Apple, Google, Mozilla, etc can DO something about the poor performance, rather than just listening to Adobe piss and moan and blame others, because Apple doesn't give a fucking browser plugin direct access to hardware.

      --
      What is...?
    6. Re:Next step: Apple bans HTML Canvas by fuzzyfuzzyfungus · · Score: 4, Interesting

      I would suspect that Apple considers HTML5 to be "better", regardless of what benchmarks say today; because they have the power to improve it, subject only to the limitations of their engineering resources and any fundamental defects in the spec(which, because the process is at least moderately open and consensus based, and one where Apple has a fair seat at the table, they have some hope of ironing out). Flash, by contrast, is however Adobe wants it to be.

      Further, I suspect that Apple doesn't really need Flash-level performance out of HTML5. By virtue of their market share(and their customers' willingness to buy widgets), the "If you want performance, make an App and shut yer trap." argument has worked pretty well for them. I suspect that their intentions for HTML5 basically boil down to "Achieve broad enough adoption for video purposes that, for any random video website our customers go to, they'll get a lump of h.246 for our hardware decoder and a couple of vector widgets, rather than a 'you don't have flash, so sad' embed box." and "Achieve performance decent enough that, if web designers and their idiot customers simply have to have their fancy flash-based menu effects, they can implement them in HTML5 and not break the experience for iPod users."(and, presumably, in the not so distant future, Mac users).

      Long term, there isn't any particular reason why HTML5, which offers vector objects and bitmap canvases with javascript control, should be markedly slower than Flash, which offers vector objects and bitmap canvases with Actionscript control. In the short term, I suspect that Apple just doesn't care all that much.

    7. Re:Next step: Apple bans HTML Canvas by mgbastard · · Score: 4, Insightful

      It will take years to optimize HTML5 to something comparable to Flash.

      Why? The Flash Player has over a decade of poor design decisions in SWF, bug-for-bug reproduction, etc, that it has to keep backward compatibility with. HTML5 canvas gets a nice fresh start having (hopefully) learned those lessons. IMHO, you'll see a lot of work with phenomenal improvements optimizing the runtimes, just like we saw with Javascript, in a quick surge. A lot of the same engineers who did did the magic on javascript are working on the HTML5 canvas implementations.

      I don't think Flash game dev's will move to HTML5 in 5 or 8 years. Flash will still be more interesting.

      I think that depends on whether Adobe makes the judgment call as to whether its more important to keep their Flash tools on top or not. If they conclude that the future is HTML5, they will bring their Flash/Flex/Air dev tools to be first class development environments for targeting HTML5 canvas; rather than being marginalized and losing their market share to a competitor in web animation authoring. Or perhaps they'll choose to compete on the platform itself, so they can own it. Time will tell.

      --
      Anyone seen my low uid? last seen 10 years ago while panning the #@$# out of Taco's 'web based discussion system'
  2. Flashblock and cookies by Meneth · · Score: 4, Interesting

    What does this mean for Flashblock and Flash cookies?

    1. Re:Flashblock and cookies by dangitman · · Score: 5, Funny

      What does this mean for Flashblock and Flash cookies?

      What a strange question. It seems about as relevant as asking what this means for Flashdance.

      --
      ... and then they built the supercollider.
  3. Smart move and good news by mcvos · · Score: 4, Interesting

    Adobe has always been more about good editing tools, rather than runtime platforms. If everybody starts dropping flash support, why would they cling desperately to the flash plugin? Having their tools export to HTML5 is a smart move. Keeps them relevant, and they won't have to support their own runtime platform anymore. Instead, they'll have to compete, which is good news for everybody else.

    1. Re:Smart move and good news by dangitman · · Score: 5, Insightful

      Adobe has always been more about good editing tools, rather than runtime platforms.

      Yeah, maybe when Photoshop and Illustrator were their main products. Since then (and particularly since the acquisition of Macromedia) they have been all about "owning the platform" and trying to tie their products into the web. It's not just Flash, they took PDF from being a nice WYSYWIG print document format, and then started embedding all kinds of interactive bullshit into it. Or Adobe AIR.

      Since around the turn of the Century, they stopped being about creative tools and started marketing to executives as being "business tools." The rapid decline of their applications was very evident, as they lost focus and tried to shoehorn their "platform" thinking into every product, even if it didn't really belong there.

      --
      ... and then they built the supercollider.
    2. Re:Smart move and good news by jlebrech · · Score: 4, Interesting

      This was the logical step to go from the start.

      Adobe has kept that quiet whilst pretending to be worried about flash going down the pan.

      Flash is just an export file format, and they can now export to a slightly less bloated/featured format. this type of technology will cement Adobe more into the web development industry.

      If Adobe are smart they will be the number 1 HTML5 authoring tools around.

      Very impressive.

    3. Re:Smart move and good news by stimpleton · · Score: 5, Interesting

      "Adobe has always been more about good editing tools."

      I really must disagree. While Macromedia made Dreamweaver, it has been under Adobe control for a while and very little has changed. My brief list of why Dreamweaver might be seriously hampered in the next evolution of web(HTML5):

      - Data IDE to a database virtually unchanged since Dreamweaver 4.
      - Broken layer support such as nested layers. Try positioning a layer mid vertical and horizontal and then try editing that in Dreamweaver.
      - No virtualization for modern javascript techniques such as httpRequest, let alone HTML 5.
      - GUI implementation of CSS is poor. Old Skool technique of writing the style sheet first is fastest.

      In summary, Dreamweaver has not got these technologies right. I feel it is in real danger of dropping the ball. Adobe's attitude confuses me. But correct re Flash. It will be an IDE for HTML5 development or die. Within several years with a combo of increased processor specs and browser optimisations, the Canvas control will be the new VGA mode. With casual games being the biggest growth market, ignore this at your peril.

      --

      In post Patriot Act America, the library books scan you.
    4. Re:Smart move and good news by dangitman · · Score: 4, Insightful

      That seems true from observation of their actions, but I can't imagine the business case really lines up with it.

      Nobody ever accused most executives that run big businesses today of being particularly competent at business. They mostly exist to enrich themselves by selling the company down the river for short-term gains.

      From everything I can discern, Photoshop and Illustrator are still by far their cash cows.

      I haven't seen any figures, but I wouldn't be so sure. Flash and Dreamweaver are very popular in web design and production. Anyway, nobody buys Illustrator or Photoshop as standalone products anymore, you buy the Creative Suite, and get the other stuff thrown in with it.

      Their ownership of PDF helps them sell some PDF authoring tools, but it's not the revenue stream that Photoshop is.

      Again, I'm not so sure about this. People may not buy Photoshop and Illustrator as standalone products, but businesses do buy Acrobat Pro as a standalone product in large quantities. Sure it costs less to buy, but it also costs less to develop, and when you buy Creative Suite it counts as an Acrobat Pro sale as well as a Photoshop sale.

      I don't have any hard answers, but to me the weirdest thing is the change of culture. Having worked in design and photo editing, it used to be hell to try and get the boss to fork out for a copy of Photoshop. They would say "why can't we use something cheaper, like Corel, or [shudder] Microsoft Paint, or perhaps pirate it?" This was at a time when Photoshop had few serious competitors. Today, Photoshop has mounting competition, and the bosses have the opposite attitude - "If it's not Adobe, there must be something wrong with it. It can't be very good if it's that much cheaper." It's the "nobody ever got fired for buying IBM/Microsoft" syndrome all over again. And just like that syndrome, it is highly entrenched. There are courses all over the world in web design that basically teach Flash and Dreamweaver as the holy grail, and teach people to do web mock-ups in Photoshop, and those courses will address issues like HTML5 when hell freezes over.

      It's a bit sad, as someone who has used Adobe stuff from almost the beginning, to see that people now miss the point. Rather than seeing the potential of the tools, it's become entrenched rote-learning and slavishness to the product, rather than the vision.

      --
      ... and then they built the supercollider.
  4. Back to the Future by wombatmobile · · Score: 5, Interesting

    Adobe was pro web standards until it bought Macromedia. It was the leading supporter of Scalable Vector Graphics (SVG) for the first half of last decade, publishing and distributing an SVG plugin for Internet Explorer and supporting SVG in Illustrator and GoLive. Adobe lost its moral compass when it bought Macromedia, After failing to halt the popularity of web standards and standing at the edge of a precipice, Adobe is now seeking forgiveness from developers.

  5. Very telling post by Khyber · · Score: 4, Insightful

    "Adobe does have some, albeit rudimentary, HTML5 Canvas exporting tools"

    Tells me they only had this as a backup plan for when shit hit the fan, which they never expected to have happen so soon.

    Apple got Adobe with their pants down and now Adobe is scrambling.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    1. Re:Very telling post by Yvanhoe · · Score: 4, Funny

      Well, I don't know if I agree with this analysis, all I want to say right now is : Thanks Adobe ! Welcome to the open web ! Finally ! Stop being an enemy and let's be friends ! Let's make the web fantastic again !

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
  6. I can't read TFA! by $RANDOMLUSER · · Score: 4, Funny

    Or rather, can't view TF video - FlashBlock prevented it.

    --
    No folly is more costly than the folly of intolerant idealism. - Winston Churchill
    1. Re:I can't read TFA! by $RANDOMLUSER · · Score: 5, Insightful

      Just to clarify, I like it that way. I don't look forward to the day when any old site can peg my CPU and I can't prevent it. God knows, some people's JavaScript is bad enough.

      --
      No folly is more costly than the folly of intolerant idealism. - Winston Churchill