On Wednesday, January 10, 2007, 3:39:10 AM, thomas wrote: tdkc> tdkc> Hi all, tdkc> I was tracking down why the 'super' and 'sub' script text in tdkc> the flow text examples isn't super and sub scripted and I found it. tdkc> tdkc> The new SVGTextElement bridge checks if the elements are subclasses of tdkc> the 'SVGOMTextPositioningElement' class, if they are then it adds the 'x', 'y', tdkc> 'dx', 'dy', and 'rotate' attributes to the Attributed string. However in this case tdkc> the flowSpan element really only supports dx,dy and perhaps rotate tdkc> (absolute positioning is not a good idea). tdkc> tdkc> I can think of three solutions: tdkc> 1) introduce a new interface or class that defines just the dx/dy/rotate, tdkc> and have the span elements implement that. tdkc> 2) Just make the span elements subclass SVGOMTextPositioningElement tdkc> and not worry about the 'x' & 'y' support. tdkc> 3) Chalk the whole thing up as a loss anyway since the WG has moved tdkc> in another direction.
Not really. For Tiny 1.2, yes, which was restricted to a single shape, which must be a rectangle: so there is a syntactic sugar equivalent with a lot less elements and just a width and height attributes instead. No need to toss the Full 1.2 implementation except perhaps to note that if there is both an @width @height *and* the child elements, the children win and the width and height attrs are not used for rendering. tdkc> tdkc> Normally I'd be inclined towards 3, except this is a true regression tdkc> (reasonable content that worked previously would stop working). tdkc> My leaning is towards 2 since it's simple and the whole thing is a tdkc> loss anyway ;) One is probably "the right thing" except the whole tdkc> thing is a loss anyway and it's not clear we will want to keep the tdkc> "albatross" once the WG points the correct direction. tdkc> tdkc> Any opinions from the peanut gallery? Have a cashew. -- Chris Lilley mailto:[EMAIL PROTECTED] Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
