----- Original Message -----
From: "L. David Baron" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 03, 2006 2:48 PM
Subject: Re: [whatwg] Canvas 2d methods
On Sunday 2006-07-02 22:47 +0200, Stefan Gössner wrote:
hmm ...
ctx.scale(2,1)
.rotate(Math.PI/4)
.translate(4,-6);
illustrates a sequence of manipulations semantically very well, doesn't
it?
In my opinion, this pattern generally makes sense semantically when used
on immutable objects (e.g., strings in JavaScript).
I don't think this pattern makes sense for mutable objects. It just
suggests immutability. And making the canvas context objects immutable
doesn't really make sense without much more significant changes.
-David
"this pattern generally makes sense semantically when used on immutable
objects (e.g., strings in JavaScript)."
Why?
For me personally it is close to
context << moveTo(..) << lineTo(...) << arcTo(....);
which is perfectly close to what is going on in reality:
drawing is a stream of graphical commands.
Andrew Fedoniouk.
http://terrainformatica.com
