[whatwg] "canvas" tag and animations ?
Ian Hickson
ian at hixie.ch
Tue May 16 13:35:18 PDT 2006
On Wed, 15 Jun 2005, Charles Iliya Krempeaux wrote:
> >
> > Surely, the canvas element is updated every time a drawing method is
> > called. End of story.
>
> Well, we need to decide on one or the other, and make it explicitly
> "spelled out" in the spec.
>
> (And if drawing operations are done and shown immediately, then it would
> be desirable to have "drawing transactions".)
>
> To be honest, the think the idea of "drawing transactions" is better.
> Here are the reasons:
>
> #1: It makes it so, if the develop wants it, that they can have things
> that are "drawn" show up immediately. (I.e., they aren't forced to use
> "double buffering" [or whatever].)
Well, the implementation in the browser will double-buffer, so this isn't
an issue.
> #2: It makes it so you could have "long lasting" scripts execute.
You can't do this anyway in a browser.
> #3: It makes it so Java and C++ interfacing will work the same. (I.e.,
> you don't have to give C++ and Java an API to effectively do "drawing
> transactions" without also giving this API to JavaScript.)
It seems that this is a very hypothetical case on the Web.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg
mailing list