Greg Veen is explaining canvas. Showing several examples of both Flash and canvas animations.
Now showing Bespin, an online code editor that uses canvas. Very cool. I had forgotten about that project. Ben Galbraith used canvas instead of Flash for performance, font rendering and browser interaction.
Alon Salant is now showing a dashboard for a large scale storage cluster network that is written in Canvas. The dashboard graphs are rendered with a JQuery plugin called flot and canvas.
Veen asked Salant why he chose Canvas over Flash. Answer: the client was very anti-Flash. Had previously used Flash for charting and had a bad experience. So it wasn’t exactly a technical reason.
Chet Haase works on the Flex SDK. Thinks it might have been a huge waste of time and resources to code a new solution (flot). He’s giving the standard Adobe line about all the existing development work behind Flash and how people shouldn’t bother reinventing the wheel. Says people latched on to Flash because of the tools available for developing in it. He finds the Flot/Canvas API to be good, but it’s lacking tools.
My thought: the tools will come. And probably faster than Adobe would like.
Germick as a game developer agrees with Haase. No argument that existing tools for Flash are more robust and well developed. The problem is with Flash itself, not its tools.
Canvas doesn’t work in any version of Internet Explorer. Is that a show-stopper for using canvas? Everybody is providing different answers. Most agree with common sense: it is a show-stopper for consumer sites but not so much in smaller, niche uses.
Current slide is just a link: http://code.google.com/p/explorercanvas/. That’s a script that adds canvas functionality to Internet Explorer.
Canvas is a really small API. Consequently implementation across browsers that support it are extremely compatible.
Sites with Flash won’t work on iPhone/iPadd. Sites with canvas won’t work in IE, so no one solution will achieve ubiquity.
Germick, a Flash game developer, is excited about the next version of Flash and it’s ability to package up Flash files as native iPhone apps.
User Experience
Flash breaks browser experience. No back button, you can’t copy text and images, you can’t link to pages within the Flash, etc. These are extremely well-known complaints.
Haase says if it’s for a game the browser interoperability doesn’t matter very much because it’s about the experience. Salant called him out on that. It’s a very limited use case.
Overall I didn’t find this panel all that interesting but that may be because I’ve followed these arguments for a long time now.

