Paul,
The reason there is no caching done is that the Image API does not
contain information that would let you do proper caching. For example,
because an image may be mutable, the SVGGraphics2D cannot cache an
image between two drawImage calls, as the image data may change between
the calls, even though the same java object is passed to the method...
This is why there is no generic method that can be offered by default
that would do proper image caching and this is why an image is embeded
for every single drawImage call. However, as Thomas pointed out, you
can write an image handler for a *specific* context. If you know that
your images do not mute between API calls, then you can do caching. But
this is not a generic solution and as such cannot be the default
SVGGraphics2D handling of images.
I hope this explains what we have done. Good luck with your project.
Cheers,
Vincent.
"Evenblij, Paul" wrote:
>
> -----Original Message-----
> From: Thomas E Deweese [mailto:[EMAIL PROTECTED]]
> >[...]
> >There are already good examples of
> >doing this for export to image files and the Base64 encoding, so even
> >someone not overly familure with Batik should be able to put this
> >togeather in a day or two (hint hint :).
>
> Hint taken.
>
> ;)Paul
>
> ---------------------------------------------------------------------
> 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]
