- From: Dirk Schulze <dschulze@adobe.com>
- Date: Mon, 17 Nov 2014 10:28:28 +0000
- To: Juergen Roethig <roethig@dhbw-karlsruhe.de>
- CC: "www-svg@w3.org" <www-svg@w3.org>
On Nov 15, 2014, at 7:37 PM, Juergen Roethig <roethig@dhbw-karlsruhe.de> wrote: > You really want to tell me that the SVG WG does not even want to consider non-affine transformations for SVG because it might take more computational power than "simple matrix math"? My question was whether such transformations were already discussed or taken into account (especially for SVG2)! I did not ask for the reason why transformations were restricted to affine transformations 10 or 15 years ago, when SVG1 was developed! Changes to transformations no longer just affect SVG. When we talk about transforms, we talk about CSS Transforms[1]. Discussions about transforms usually happen on www-style@w3.org. Even though we added a new z-axis and allow a perspective and representations as 4x4 matrices, CSS Transforms still describes affine transformations. Complexity is for sure one reason why non-affine transformations were not considered yet. The lack of interest of web authors has a much bigger impact though. In fact, the vast majority of use cases does not require non-affine transformations at all. It needs compelling use cases to get implementors on board. As Rik, I am not aware of authoring tools that would support non-affine transformations. There might be pixel based authoring tools. Quite often these would use WebGL as the technology of choice on the web stack. Greetings, Dirk [1] http://dev.w3.org/csswg/css-transforms/
Received on Monday, 17 November 2014 10:28:59 UTC