George Armhold wrote:
M�ns Rullg�rd wrote:
> There are platforms with nothing later than Java 1.3 available.
> Requiring Java 1.4 might irritate some users of those.
Are there really many people using Batik on Java 1.3? (That's not a
rhetorical question- I'd really like to know.)
Well, I still mostly use JDK 1.3 but a large part of that is
just to ensure that Batik still works on JDK 1.3. I don't think
this really counts though.
Also if someone in the know could comment on my question about
potential performance improvements by using the new APIs in 1.4
Image IO, I'd appreciate it.
This is a little tricker to know. We currently use the JDK
JPEG decoder so that shouldn't be significantly faster. We
don't use the JDK PNG decoder because it is/was not compliant with
the SVG specification (IIRC it was the way it handled the
gamma chunk, it is possible that this problem could be 'fixed'
with Image IO).
The real win would likely be in using Image I/O to write images.
In particular our PNG encoder is extremely slow (I haven't noticed
this to be a large problem with the decoder but I must admit to
not testing it too much).
In the svg12 branch we already have a code fork for 1.3 vs 1.4
so I would expect that as development moves to that branch that
new 'features' would be enabled for users on JDK 1.4 such as using
Image I/O for reading images.
It should be fairly simple for someone to write a
ImageTagRegistry Entry that used Image I/O I haven't done so
since I didn't think it warranted introducing the split for
jdk 1.4.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
