> Does this mean that the Albert package no longer
Correct. The Albert package is no longer there at all.
(Though a different storage format is still used for Area in order
to speed up doing the geometry calculations. The new format more
closely matches the Shape/PathIterator requirements, though. Think
of it as an annotated PathIterator segment format.)
> Has there been any improvement on the intersect methods ?
Are you referring to the CAG method for calculating the intersection
of two paths or the methods for testing intersection with a rectangle?
The new code for doing intersects() and contains() is much more
direct, especially from a GeneralPath which now does its own
hit detection using the same facilities rather than constructing
an Area object (every time!) and relaying the request. The
performance improvement is quite noticeable. (The results are
also "correct" now... ;-).
The new package for doing CAG has much more stable run times. The
two packages still have the same recursive Bezier curve intersection
test at their heart, but the framework which surrounds that test was
rearchitected and reacts much better to the corner cases. The storage
format for the curves is also new and much faster at performing the
computations for the test itself.
The new code could still stand to be tuned, but since a lot of the
performance "bugs" were fixed by the rearchitecting, I went on to
other problem areas and left the tuning for a later stage...
...jim
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 2D Home Page: http://java.sun.com/products/java-media/2D/
