W3C home > Mailing lists > Public > www-style@w3.org > September 2013

Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions

From: Dirk Schulze <dschulze@adobe.com>
Date: Wed, 25 Sep 2013 07:45:09 -0700
To: Simon Pieters <simonp@opera.com>
CC: Simon Fraser <smfr@me.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <0A07B903-DE01-4F8E-9944-332813A7F220@adobe.com>

On Sep 25, 2013, at 2:46 PM, Simon Pieters <simonp@opera.com> wrote:

> On Mon, 23 Sep 2013 21:30:06 +0200, Tab Atkins Jr. <jackalmage@gmail.com>  
> wrote:
> 
>> On Mon, Sep 23, 2013 at 11:28 AM, Simon Fraser <smfr@me.com> wrote:
>>> Why do we need both DOMPoint and DOMPointLiteral?
>> 
>> DOMPointLiteral exists so that you can call methods that expect points
>> without having to wrap it in a verbose DOMPoint() constructor at
>> call-time.
>> 
>> That is, you can say "el.transformPoint({x:5, y:10})" instead of
>> "el.transformPoint(new DOMPoint(5, 10))".
> 
> transformPoint, is that convertPointFromNode or something else?

No, it transforms the passed point by the matrix.

var m = DOMMatrix();
m.scale(3);
var newPoint = m.transformPoint(oldPoint);

will scale the point by the factor 3.

I will change the argument type to a DOMPointLiteral.

Greetings,
Dirk

> 
> -- 
> Simon Pieters
> Opera Software
Received on Wednesday, 25 September 2013 14:45:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC