W3C home > Mailing lists > Public > www-svg@w3.org > December 2005

SVGT 1.2: SVGMatrix gratuitously incompatible with SVG 1.1 version

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 28 Dec 2005 15:13:21 -0700
Message-Id: <B0F9E0D8-C5D8-42FB-A459-FE260BEE5B89@apple.com>
To: www-svg@w3c.org

SVGT 1.2 uDOM SVGMatrix has the following differences from the SVG  
1.1 version:

- float getComponent(in unsigned long index) raises(DOMException) in  
place of separate a, b, c, d, e, f attributes.

- mMultiply, mTranslate, mScale, mRotate in place of multiply,  
translate, scale, rotate which mutate the matrix instead of multipy,  
translate, scale, rotate which return a modified copy (although the  
mutation behavior is only made clear in a note, not really in the  
method descriptions themselves). However, inverse is left the same  
and still gives a new matrix.

This means you need to write totally different code for matrix  
manipulation in SVG 1.1 Full DOM vs. SVG 1.2 Tiny uDOM. Is there a  
deep reason for these differences? Why not stick with a compatible  
subset of the 1.1 SVG DOM?

Received on Wednesday, 28 December 2005 22:13:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:05 UTC