W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2012

Re: Matrix4x4 proposal

From: Dean Jackson <dino@apple.com>
Date: Tue, 24 Jan 2012 12:48:42 +1100
Cc: Kristian Sons <kristian.sons@dfki.de>, public-fx@w3.org
Message-id: <52F99C4B-F0C3-4647-AF72-40D084BDCB9A@apple.com>
To: Gregg Tavares (勤) <gman@google.com>

On 24/01/2012, at 12:46 PM, Gregg Tavares (勤) wrote:

> On Mon, Jan 23, 2012 at 3:57 PM, Dean Jackson <dino@apple.com> wrote:
> On 20/01/2012, at 11:03 PM, Kristian Sons wrote:
> > Hi,
> >
> >> // The value of angle is in radians.
> >>     void rotateAxisAngle(in double x,
> >>                          in double y,
> >>                          in double z,
> >>                          in double angle);
> >
> > I didn't follow the discussion from the beginning, so this might be already discussed:
> > In the CSSMatrix proposal, all angles are in degrees. Also SVG uses degrees in interfaces. Do you want to change to radians?
> We agreed to stick with degrees. I need to post an updated proposal.
> Really? Are angles expected to be in degrees by devs who will actually use these classes?

This is why I originally proposed radians. I don't feel strongly either way.


> I ask because it seems silly to take the dot product of 2 vectors and have to convert to degress before I can use the answer. I'm sure people better at math can name a bunch of other cases.  How about 2 functions, rotateAxisAngleDegress and rotateAxixAngleRadians. I suppose with either one you can write a quick wrapper to produce the other, it just seems wrong to pick the less efficient one when the whole point of this API is speed (otherwise just do everything in JS)
Received on Tuesday, 24 January 2012 01:49:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 June 2015 03:33:46 UTC