On Sep 1, 2010, at 1:04 PM, Chris Marrin wrote: > On Sep 1, 2010, at 12:29 PM, Maciej Stachowiak wrote: > >> On Sep 1, 2010, at 11:43 AM, Chris Marrin wrote: >> >>> >>> But I agree with Maciej that all of the public API is transformation >>> oriented. Even things like inverse() and transpose() have application in >>> doing transforms. I think it would be a stretch to use this 4x4 matrix for >>> general purposes. A general matrix class usually has to deal with different >>> dimensions, for instance. >>> >>> But I am loath to call it HomogeneousTransform, given the fact that Maciej >>> and I have spelled it differently (both are accepted spellings) and it will >>> be really hard for people to get used to spelling such an uncommon word. >>> >>> If you look at the "Uses" section of >>> http://en.wikipedia.org/wiki/Transformation_matrix you'll see that they >>> consider the term improper as well. And they have a good point. Since they >>> recommend the term "general transformation matrix" to distinguish it from >>> the more restricted "affine transformation", then simply calling it >>> Transform seems appropriate. >> >> Transform sounds ok to me, actually, even though it is a little broad. > > Filed as https://bugs.webkit.org/show_bug.cgi?id=45051. I also opened > https://bugs.webkit.org/show_bug.cgi?id=45052 for the work to change > Transform back to floats. I'm not sure we've fully committed to do this, but > I wanted it recorded in the bug list. We can invalidate it if we don't end up > doing it.
SVG already has SVGTransform, the interface for one of the component transformations within an SVGTransformList, which has an SVGMatrix property, which represents the matrix. I think Transform is going to get too easily confused with existing transform terminology related to CSS and SVG transforms, and maybe XSLT too. Simon _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
