Thomas DeWeese wrote: > > Would it be possible to make some of these methods and fields protected, > it would ease the process of controlling the generated SVG Tree.
>> I would actually prefer to make protected 'createXXX' methods for >> these so your subclass can override and construct your version of >> them. This prevents issues with swapping the various managers >> in the middle of a document. >> Why don't you make the changes and check? Then if it works well >> you could submit the changes as a patch ;) OK, I will do that, and send the changes after checking it is OK. > Another enhancement in svggen would be great too : > - allow to set a custom XMLWriter (in some cases I encountered with > exotic Unicode Strings, the actual failed to provide a proper > conversion) >> Well since currently the code references XmlWriter statically, >> I'm not sure how much this would help for extension. We are likely >> to move to using dom.util.DOMUtilities for output. For users to >> extend output (which I think makes sense) this would have to become >> instance based. You are right. > And it would be great too if the SVGShape class could manage Java arcs > without automatically converting them to Curves. It could be done by > providing a new SVGArc class... >> This might be nice as well. You should feel free to make bugzilla >> entries for any or all of these so they don't get forgotten. We >> really do look at bugzilla. Done for the three RFEs. Thank you ! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
