- From: Erik Dahlstrom <ed@opera.com>
- Date: Wed, 16 Jan 2013 12:37:30 +0100
- To: www-svg@w3.org
On Tue, 15 Jan 2013 21:11:59 +0100, Dirk Schulze <dschulze@adobe.com> wrote: > Hi, > > I would like to request the following topics for the agenda this > Thursday: > > SVG2: > Philip Rogers and I created a diagram of the dependency trees from SVG > 1.1 and SVG2 [1]. > 1) Together with Cameron, we figured out that SVGLocatableElement and > SVGTransformableElement can be combined with the new inheritance concept. > 2) Should SVGTextContentElement inherit from SVGGraphicsElement or > SVGGeometryElement (currently in the draft)? The later provides neat > methods like isPointInPatth, which on the other hand are not so easy to > implement on some platforms. 3) why shouldn't e.g the <pattern> element have typed DOM access to @patternTransform? Basically I'm wondering why this shouldn't also inherit SVGTransformableElement. -- Erik Dahlstrom, Core Technology Developer, Opera Software Co-Chair, W3C SVG Working Group Personal blog: http://my.opera.com/macdev_ed
Received on Wednesday, 16 January 2013 11:38:00 UTC