W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2009

ISSUE-2233 (transform-syntax): adopt the syntax for CSS Transforms [Module: Transforms]

From: SVG Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 18 Mar 2009 12:32:11 -0400 (EDT)
To: public-svg-wg@w3.org
Message-Id: <20090318163211.AFEC14DD60@crusher.w3.org>

ISSUE-2233 (transform-syntax): adopt the syntax for CSS Transforms [Module: Transforms]


Raised by: Doug Schepers
On product: Module: Transforms

Per http://lists.w3.org/Archives/Public/public-svg-wg/2009JanMar/0148.html

* why not adopt the syntax for CSS Transforms (which was written to be  
as compatible as possible with SVG)?

In particular, I see this:
AG: I agreed to remove translateX/Y/Z and scaleX/Y/Z
JF: translateX/Y is part of the CSS specification but that's just  
syntactic sugar

While these might shortcuts look like syntactic sugar, they allow for  
something important - which is the ability to break a transform list  
into components that can manipulated individually. This is especially  
important when you're animating between transforms (not necessarily  
with CSS Animations, even JS gets the benefit). Flattening all the  
transform operations is a lossy process (not in the final matrix  
result, but you lose the list).

In general I'm not sure there is benefit in minimising the syntax.  
What is the cost?
Received on Wednesday, 18 March 2009 16:32:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:29:41 UTC