- From: ddailey <ddailey@zoominternet.net>
- Date: Sun, 11 Mar 2007 19:45:57 -0400
I have had no interest in learning (or teaching) about the Canvas tag since, from what I can see, it is quite impoverished relative to SVG. And, to boot, it is not universal across browsers. The browsers that support Canvas, pretty much already do support, or seem to be close to supporting SVG. The one advantage that VML had over SVG, was the ease of co-integration of it with HTML (albeit in precisely one browser). If Canvas can be standardized as a place for drawing SVG, then I can deliver a million votes (plus or minus a million) to the the party that adopts it in its platform. I know... nobody cares about a million votes any more. ddailey ----- Original Message ----- From: "carmen" <_@whats-your.name> To: "Matthew Raymond" <mattraymond at earthlink.net> Cc: <whatwg at lists.whatwg.org>; "carmen" <_ at whats-your.name> Sent: Sunday, March 11, 2007 5:47 PM Subject: Re: [whatwg] canvas elements <rect> <polygon> etc > On Sun Mar 11, 2007 at 05:06:06PM -0400, Matthew Raymond wrote: >> carmen wrote: >> > are there plans to support html style creation of elements within the >> <canvas> tag? >> >> How would that be different from Scalable Vector Graphics (SVG)??? > > thats kind of what i'm asking, it looks like SVG has its own API already, > sort of similar to canvas. are there plans to merge? can you use svg > elements inwide a canvas element or will the browser not find them? are > there plans for that to change? etc. > > i guess a roadmap explaining the relationship between <canvas> and <svg>.. > is this another xhtml2 vs html5, simultaneous development? what was wrong > with SVG that required a simpler replacement (but i guess not element > level interface).. > > anyways, i guess i'lll scour faqs and unsubscribe > >> > >
Received on Sunday, 11 March 2007 16:45:57 UTC