[webkit-dev] The future of TransformationMatrix

Chris Marrin cmarrin at apple.com
Fri Jan 14 16:30:05 PST 2011

On Jan 14, 2011, at 4:12 PM, Dirk Schulze wrote:

> At first SVGMatrix and the complete SVG code itself is not using TransformationMatrix. We had bigger performance problems and the memory amount raised up by 6-10%. Thats why we decided to turn back to AffineTransform.
> Because of the platform dependencies of TransformationMatrix. I noted that replacing AffineTransform, that was platform dependent at that time, by TransformationMatrix, which wasn't, may cause performance losses. At this time it was not clear that we would use 3D all over the place. I was told that the great benefit of a independent implementation is, that we get same results across platforms (a bigger problem that we saw on DRT and which caused a lot of platform dependent results). Is this argument not valid or important anymore?

Sorry, you're right. AffineTransform and TransformationMatrix interoperate because of the casting operators. I've had a desire for a while to supplant AffineTransform and make TransformationMatrix switch its internal storage when a 2D affine transform is stored. Maybe that another bug!

cmarrin at apple.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20110114/ab9ab82b/attachment.html>

More information about the webkit-dev mailing list