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! ----- ~Chris cmar...@apple.com
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
