Re: [whatwg] Canvas comments

2008-02-09 Thread Ian Hickson
On Fri, 1 Feb 2008, Oliver Hunt wrote: > > I believe Hixie is already looking at speccing the ImageData object to > require a fast native backing buffer (i could be wrong), but i'll add my > two cents here. Indeed, that has now been done. > That said i would still very much like to have the ab

Re: [whatwg] Canvas comments

2008-02-01 Thread Oliver Hunt
... lots of stuff that hixie has already responded to ... * There's no fast way to edit the pixels on the canvas. putImageData and getImageData are glacial, as is fillStyle= + fillRect(). Byte arrays (well, if strings were bags of bytes, they'd work too) or a shader language, maybe? I don

Re: [whatwg] Canvas comments

2008-01-31 Thread Ian Hickson
On Tue, 25 Dec 2007, Ilmari Heikkinen wrote: > > Some comments on the canvas spec, based on my experiences in writing a > SVG renderer and some interaction demos on canvas > (http://glimr.rubyforge.org/cake/canvas.html) Cool stuff. > I would change the transforms to affect only path segments,

[whatwg] Canvas comments

2007-12-25 Thread Ilmari Heikkinen
Hi, Some comments on the canvas spec, based on my experiences in writing a SVG renderer and some interaction demos on canvas (http://glimr.rubyforge.org/cake/canvas.html) 1. I would change the transforms to affect only path segments, fills and strokes done _after_ the transform. Currently, Firefo