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

Re: Proposal: Nesting SVG Graphics Elements

From: Jeremie Patonnier <jeremie.patonnier@gmail.com>
Date: Mon, 3 Dec 2012 14:01:50 +0100
Message-ID: <CAEi838mq2TX35ebP3+FKW0qOdcMJdH8W-DQ6oO+Y_YiLq6TAEg@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: Doug Schepers <schepers@w3.org>, SVG public list <www-svg@w3.org>
2012/12/3 Dirk Schulze <dschulze@adobe.com>

>
> On Dec 3, 2012, at 3:12 AM, Jeremie Patonnier <jeremie.patonnier@gmail.com>
> wrote:
>
> > This alternative proposal does not really change SVG as it is and offer
> a nice short cut for user who wish to perform SVG hand editing.
>
> But where is the difference of using: transform="translate(dx, dy)"?


Almost none, it's syntactic sugar with a little difference: those
attributes act like the translation is applied before any other transform
and the transformation operate by those attribute is not visible in the
list of transformations. They act really like the point of origine has
changed, not just by moving the elements. This is why, in this proposal, it
is possible to reset the coordinate system with the x and y attribute
(doing this with transform is just a pain in the ass because you have to
check all the transformation applied along the DOM tree if you have nested
elements with a transform on each).


> I would rather say that HTML+CSS authors won't have this big problem with
> it, given the fact that we have CSS3 Transforms in HTML as well.
>

You should'nt assume that. HTML+CSS authors are fare from familiar with CSS
Transforms, and transformation in the CSS world are really disruptive (I
see that every day with many people around me). From my perspective, only
authors with advanced skills are ok with transforms. Most of the time they
use it with JS on top of it and when they edit it by hand it's to perform
very small change (especially because it's not supported in legacy browser
so they cannot relay on it, therefor they learn slowly how it works). And
to be  honest, the quality of cross-browsers implementation of CSS
transform is not very good (poor rendering or horrible performance, make
your choice) which does not help the authors to embrasse them at a large
scale. So it remains an aside technologie in HTML+CSS.

Best
-- 
Jeremie
.............................
Web : http://jeremie.patonnier.net
Twitter : @JeremiePat <http://twitter.com/JeremiePat>
Received on Monday, 3 December 2012 13:02:45 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:53 GMT