Hi all,
Like Cameron I think that this is essentially already done. The list of constants in CSSConstants is just for convenience, Except for a small number those constants aren't used by the CSSEngine. You can easily configure your own subclass of CSSEngine to support any set of properties you want.
I don't think the small space savings afforded by separating the constants is really all that useful but if someone wants to produce a patch they could.
Since you say you have already applied the CSS engine to another XML grammar I suspect that I may be missing something important in your request.
Cameron McCormack wrote:
Jamie Browning:
However, as an XML utility, the CSS engine could stand alone. Applying CSS to an XML document is a general task, not limited to SVG. A standalone CSS engine might be useful for other developers working with XML and CSS, using other XML dialects.
To achieve this, the properties supported by the engine would need to be decoupled, perhaps using some pluggable mechanism.
I think this is an excellent idea.
And also not very difficult, since the CSS engine really isn't very coupled to the rest of Batik. See how the SVGCSSEngine class extends the abstract CSSEngine to add the managers for all of the types that SVG supports.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
