You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by Thierry Kormann <Th...@sophia.inria.fr> on 2000/11/21 11:58:46 UTC
Re: SVG elements
> If we have an example that uses a feature, users will copy it.
> I don't think putting our definition in our own namespace will
> be a sufficient deterrent.
They will copy the example using the batik's namespace, so there is no prob. It
should even be an example of 'how to integrate custom elements in batik'
> I'd like to have a look at what would be required to treat
> Dean's textPath (as a child of <text>, in the officially sanctioned
> syntax) as a special case of our current TextElement...what
> do you think, Dean ?
I think it's too late now for the first release to change the text element. I
am a bit nervous now to add new features. I am focus in the error handling and
I would like to finish this work.
Then, supporting textPath in the TextElementBridge is *not* easy and still a
temporary solution. What we need is a complete and full implementation of SVG
text elements. To do this, I think we need to design an API that takes care of
textPath, tspan, SVG fonts and the various attributes (x, y, dx, dy, rotate...).
So I vote to *not* hack the text and the bridge and design an API for text
after the first release.
Thierry.
--
Thierry Kormann
email: Thierry.Kormann@sophia.inria.fr http://www.inria.fr/koala/tkormann/
Koala/Dyade/Bull @ INRIA - Sophia Antipolis