W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2006

[whatwg] Canvas 2d methods

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Tue, 04 Jul 2006 09:47:34 -0700
Message-ID: <003001c69f89$8c994a30$3401a8c0@TERRA>
----- Original Message ----- 
From: "Vladimir Vukicevic" <vladimirv@gmail.com>
To: <whatwg at whatwg.org>
Sent: Monday, July 03, 2006 9:47 PM
Subject: Re: [whatwg] Canvas 2d methods

> Even without using |with|, why not just create a simple JS wrapper for
> the context object that can have return-this or any other desired
> semantics?  This would avoid a change that would have some apps
> require "canvas 2D 2.0" or some such, and require authors to do
> version checks to see which version of canvas is supported -- and
> still write "old" code for quite some time.  Adding "a different way"
> to do the same things that can be done now without much benefit in
> simplicity or efficiency doesn't seem useful.
> Canvas supports multiple contexts for a reason; if there are
> compelling arguments for a complete rev of the 2D API, then a new
> context can be introduced to support that.
>   - Vlad

Is this 2D API already carved in the stone of standard? 
If 'no' then it is better to discuss it now then after.

And what to return it is far not "a complete rev of the 2D API".
It is a matter of changing:

return undefinedValue; 
return self;

in correspondent C/C++ functions. 
And this change will not break any existing scripting code.

Andrew Fedoniouk.
Received on Tuesday, 4 July 2006 09:47:34 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:47 UTC