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.'"
Nothing. Flash will never be replaced, and by the time you start seeing Canvas ads, you'll have Canvasblock :)
HTML5 Canvas is only as slow as the JavaScript engine in the browser in question...
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.
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 ....
Puteulanus fenestra mortis