W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2009

Re: Separate Draft of Canvas API Uploaded to CVS

From: FUJISAWA Jun <fujisawa.jun@canon.co.jp>
Date: Tue, 18 Aug 2009 18:17:34 +0900
To: Doug Schepers <schepers@w3.org>
Cc: HTMLWG WG <public-html@w3.org>, public-canvas-api@w3.org
Message-Id: <20090818173715.C55A.2E34A820@canon.co.jp>
Hi Doug,

On Mon, 17 Aug 2009 13:49:20 -0400
Doug Schepers <schepers@w3.org> wrote:

> There was quite a lot of talk about splitting out Canvas from the rest 
> of HTML 5, but there seemed to be a roadblock in actually getting this 
> effort started.  I took the initiative to create a draft [1] of the 
> Canvas 2D API that is split out from HTML5, and just concentrates on the 
> API, rather than the <canvas> element.

Thanks for taking an initiative to start splitting out the Canvas 2D API!
Together with the WebGL API, Canvas 2D can be an important addition to
SVG-based Web applications.

> I took the opportunity to make it a little more generic (i.e., not 
> HTML-specific), so that SVG could also include the Canvas API (for 
> example, to be used on <image> elements in SVG);

As for the use of in SVG, I think the Canvas API would be useful for any
elements that establish a new viewport, including 'svg', 'image', 'video',
'animation', and 'foreignObject' elements.

There is no element that provide graphics rendering context in HTML, so
we need to introduce 'canvas' element. In the case of SVG, however, we
already have a good set of graphics elements with independent rendering
contexts, and we should take full advantage of the available rich
features of SVG.

-- 
Jun Fujisawa
<mailto:fujisawa.jun@canon.co.jp>
Received on Tuesday, 18 August 2009 09:18:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 18 August 2009 09:18:30 GMT