W3C home > Mailing lists > Public > public-html@w3.org > June 2009

Re: Canvas - SVG Bridge

From: Klaus Förster <klaus.foerster@uibk.ac.at>
Date: Mon, 29 Jun 2009 14:39:00 +0200
Message-ID: <4A48B5E4.8090406@uibk.ac.at>
To: Robin Berjon <robin@berjon.com>
CC: www-svg WG <www-svg@w3.org>, "public-html@w3.org WG" <public-html@w3.org>
well done Robin,

maybe we should tell browser vendors to implement what the HTML 5 spec 
already mentions under canvas.toDataURL([type,...]): "The possible 
values are MIME types with no parameters, for example image/png, 
image/jpeg, or even maybe image/svg+xml if the implementation actually 
keeps enough information to reliably render an SVG image from the 
canvas" [1]

Your library could act as "reference implementation" to get a better 
idea what "keeps enough information" and "reliably render an SVG Image" 
could mean, could it?

Klaus Förster

[1] 
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#dom-canvas-todataurl

Robin Berjon wrote:
> Hi all,
> 
> for various reasons explained on the page below I thought it fun to make 
> a wrapper for canvas that could output SVG (not entirely unlike the IE 
> emulators). It can be used either to turn some of the cool pics that 
> people make with canvas into SVG that can be edited, pasted elsehwere, 
> etc., and it can also produce a live SVG mirror for canvas.
> 
> It's not finished but usable, get it from:
> 
>   http://berjon.com/hacks/canvas-getsvg/
> 
> It's certainly not an option, but it *might* be a data point in the 
> canvas and accessibility discussion.
> 

-- 
Klaus Förster
Institut für Geographie
Universität Innsbruck
A-6020 Innsbruck, Innrain 52
Tel.: +43 (0)512 507 5434
Received on Monday, 29 June 2009 12:45:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:39 GMT