On Tuesday 10 July 2001 19:38, Thomas E Deweese wrote:
Hi,
> Since this is your 100% typical speed vs. quality tradeoff it seems
> pretty clear that for color-rendering (perhaps shape rendering?) set
> to optimizeSpeed gradient anti-aliasing should be off for
> optimizeQuality it should be on. This of course leaves the question
> of what to do in the default case.
That makes sence. I agree that the default should by antialisingOff.
> My question is for Thierry or Vincent. Is the optmizeXXX stuff
> working yet? If so how are the hints mapped?
Yes. shape-rendering, text-rendering and image-rendering properties are
working. You have some examples that illustrate the mapping between J2D
rendering hints and SVG rendering hints in the sample/tests directory.
> Finally, Thierry, as I recall there was some debate over how
> gradients that use the same stop value twice should be handled, what
> is implemented in Batik doesn't match my recollection of the
> discussion. Right now Batik deletes the first stop at the value, I
> think it should keep it and have the gradient have a discontinuity:
This is something that could be easily handled by the bridge. The bridge
already does much more work for gradients. The SVG spec mentions what to do
is the radius of a radial gradient is 0, if an offset is greater than 1 or
lower than 0...
So I already do lots of things in the gradient bridges. I could do that one
if you think it's my job (I think it is). Anyway, the previous implementation
of the gradients handles the case of 2 offsets with the same value and do
what the spec says, so I just ignore this one in the bridge.
Finally, it's up to you. If you ignore this case, I can handle it in the
bridge.
> If you agree with my thinking then I will check in an updated
> version of the gradient bridge that does this.
I do (a bit late :)
Regards,
Thierry.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
