> I would consider adding SVGImage to SVGSalamander.  Since it would depend
> on the pivot binaries, I'd want to put it into a separate jar.

You could do that, though it shouldn't be a problem to include everything in 
the same JAR. The Pivot dependency wouldn't be an issue unless someone tried to 
use SVGImage or SVGImageSerializer, which they presumably would only be doing 
if they were actually building a Pivot app (and hence already had the Pivot 
JARs on the classpath).

> SVGImage looks quite similar to SVGIcon, which is Salamander's custom
> extension of Icon for decorating Swing buttons.  Does Pivot handle AWT
> Icons?  If so, this might be an even easier way to render SVGSalamander
> content in Pivot without having to extend either library.

We could potentially write a Pivot Image wrapper for the Swing Icon class. 
However, there are a couple of issues with that approach:

1) Pivot doesn't currently have any dependency on Swing, and we would prefer to 
keep it that way if possible.

2) The serialization support provided by SVGImageSerializer just as important 
as SVGImage itself. The serializer is what allows us to embed an SVG image in a 
BXML file. We could theoretically write an SVGIconSerializer class, but then 
we're right back where we started - needing to add at least one additional 
class to your project.

Thanks for your help,
Greg



Reply via email to