----- Original Message -----
From: "Vladimir Vukicevic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
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;
to
return self;
in correspondent C/C++ functions.
And this change will not break any existing scripting code.
Andrew Fedoniouk.
http://terrainformatica.com
