To read all comments associated with this story, please click here.
I didn't do it indeed, but I've done SVG and I don't get canvas. Elements in canvas are not identifiable. It's bad in many aspects in my opinion, starting from lack of accessiblity. A lot of people using the web are blind, or have disabilities that prevent them to use the web like the web master think they should use it. SVG is well formed XML and therefore is DOMable. That makes it way better suited for the web in my opinion. If they make canvas because it is easier to use, why don't they put energy in making tools to generate SVG instead? Cairo does it. Why can't they convert canvas to SVG?
By the way, the same is true for flash. They should convert it to SVG and be done with their opaque format.
Edited 2008-09-23 13:18 UTC
Flash has all but killed SVG. Why? Because the numpties that drew up the specifications probably never actually tried to use the specifications to actually make any thing. If they did they would see why the geeks use SVG, and why everyone else making websites sided with Adobe and Flash.
Have you used SVG or Canvas?; trying to compare it to Flash because you see two shapes on the screen and assume that Flash is better is 2-D thinking.
O, if I only had my project ready yet, I'd so prove [you] wrong. Let me just say that I'm building a couple of things that show what Canvas can do in a completely open and cross-platform compatible way.
SVG is about solving global document problems, not generating revenue for expensive tools.
Edited 2008-09-23 10:51 UTC







Member since:
2006-11-17
Why don't they stick to SVG? What does canvas do that SVG doesn't? SVG is way better in my opinion. I don't see any case where canvas should be used instead of SVG. They should kill it right now IMO. If possible, they should kill flash as well and properly support SVG.
Edited 2008-09-23 09:50 UTC