Adobe Flash CS5 Exports Animations To HTML5 Canvas 166
Posted
by
timothy
from the take-this-jobs-and-shove-it dept.
from the take-this-jobs-and-shove-it dept.
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.'"
Re:Flashblock and cookies (Score:4, Informative)
Nothing. Flash will never be replaced, and by the time you start seeing Canvas ads, you'll have Canvasblock :)
Re:Next step: Apple bans HTML Canvas (Score:3, Informative)
Actually that's mostly using WebGL. If it was rendered using an HTML5 canvas alone I'm guessing you'd see maybe 0.1fps on a fast machine.
Re:Next step: Apple bans HTML Canvas (Score:4, Informative)
HTML5 Canvas is only as slow as the JavaScript engine in the browser in question...
Re:Next step: Apple bans HTML Canvas (Score:4, Informative)
It's not just "resource intensive", it's outrageously dog slow for seemingly no reason. It seems almost incredulous that it could be as bad as it is, but a simple H.264 stream inside a flash container (ie, no fancy extra stuff, just video in a box) is a painful hog in OS X. A 2Ghz Core 2 Duo should not be pushing 30% usage per core to play back 480i content.
Interactive flash content like games, or just heavy pages (like Blizzard's Diablo 3 site) do work, but they don't half push the CPU hard - considerably harder than the same site on the same machine booted into XP. (and we'll assume no H.264 hardware decoding on either platform - we're talking the animations and other stuff that flash does as well, it's not just video playback).
On2's flash player that was part of the program for testing your flash builds (it had a feature to create little ready made flash players from your movies) was better, and XBMC (running on top of OS X) is excellent at playing video streams that the browser plugin makes such a meal of.
It really is atrocious on OS X. (despite the considerable developer documentation about OS X's innards, although you will hear some people claiming it was somehow Apple "denying Adobe access" to the core of OS X to make flash better.
Re:Patented by Apple (Score:3, Informative)
Re:Patented by Apple (Score:4, Informative)
Apple disclosed the patents under the W3C's royalty-free patent licensing terms. This means means that Apple is required to provide royalty-free licensing for the patent whenever the Canvas element becomes part of a future W3C recommendation created by the HTML working group ....So Apple are not being "Evil" and so no double standards needed ....
Re:Next step: Apple bans HTML Canvas (Score:1, Informative)
That is not true for Mac OS X, and Flash is a prime example. The single leading source of application crashes on Mac OS X is a component that Apple can't fix.
The accelerator pedal in a car is the single leading source of car crashes, do we ban the accelerator pedal or just teach drivers how to use it properly (and accept that some of them will abuse the privilege and suffer the crashes).
Re:Next step: Apple bans HTML Canvas (Score:3, Informative)
Heh. But it's not too far-fetched to think that Apple's infamous new rules for the iPhone have something to do with Adobe suddenly annoucing that they're working on Flash->HTML5 conversion. It looks like something good might come out of that decision after all.
I doubt that, the video is from october 2009
Re:Next step: Apple bans HTML Canvas (Score:3, Informative)
Apple don't create the implementation of Flash (and can't). So if Apple allow Flash onto the iPhone OS then they cannot influence the quality of that implementation over time. Apple created their own implementation of HTML5, and they can improve it and maintain it over time. Apple want to be able to maintain the user experience - not because they love their customers, but because they want to keep selling iPhone OS devices: they have to remain competitive over time. Essentially Apple are alone in this "longterm thinking" other manufactures leave the software to other players, given what's happened with other players in the market we can see that Apple's approach does have advantages.
Many people think Apple are primarily interested in "App" sales - Apple see this as a side issue, and actually the AppStore is seen primarily as adding value to the iPhone OS devices (or to put it another way, the AppStore helps sell iPhone OS devices, rather than the other way around). What Apple want is that anything created in HTML5 works well on the iPhone - so buyers see the iPhone as a good choice for consuming that content.
Why does Apple really hate Flash? Well if you look at the implementations of Flash on Linux, Mac OS X, and Windows it is obvious that the Windows one gets far more love from Adobe than the other two - Apple hate that.
Re:Back to the Future (Score:3, Informative)
Take a look at Apple... the only HTML5 standard they are supporting is the one already implemented in Webkit (coincidentally, it's their own platform). Sure, they've put up a "standards group" to make it seem like they care about others think, but the WHATWG standard is really "what Apple thinks best suits their interest".
Um, what? The WHATWG standard is written by Ian Hickson, who works for Google. There's theoretically a short list of members who can overrule him, but a) that includes people from Apple, Opera, Google, and Mozilla, as well as one freelancer; and b) it does nothing in practice, just lets Ian call the shots.
The spec also currently has a W3C version that mirrors the WHATWG version. Changes to the W3C version can be made by a procedure that ultimately boils down to approval by the three co-chairs, who are employed by Apple, IBM, and Microsoft. The W3C itself, including the TAG headed by Tim Berners-Lee, also has a say in how the standard develops there. In principle, substantive differences could arise between the WHATWG and W3C versions, but so far Ian has implemented all the non-editorial approved change proposals in both specs (AFAIK).
I'm all for saying Apple is basically evil, but saying Apple controls HTML5 is ridiculous.