If this is the end of QTJava; thanks for the great ride (makes a
backup).
Perhaps things will gradually stop working over time but it doesn't
mean QTJava will be actively removed. There are *lots and lots* of
people who depend on QTJava. If Snow Leopard 10.6 removes it
altogether then users simply won't update to 10.6 (or indeed 10.5).
It's true you won't ever see QTJava support from Apple in Java 6,
but remember that Leopard still ships with Java 1.3.1 even now, and
even if they drop that then 1.4 and 1.5 will still be around and are
perfectly usable for most things.
I don't think it is the Java side that will break QT4J. The move to
Quicktime X, from what I've gleaned from rumors sites and the like, is
a clean-ish break from QT of the past. If 10.6 is primarily a
refactoring, de-Carboning, and de-crufting release, it makes sense
that Apple also addresses these issues in QT which, again in my
imperfect understanding, form the core of the Java <---> QT bridge.
I mostly read this list for my own edification as I stopped doing any
work with QT4J several years ago and I hate to be alarmist, but this
may well be the death knell for QT4J unless they release something or
at the very least license some QT4J OS community to continue bridging
to QT. I hate to see it go because it was such a great asset to
Java. OTOH, it may finally spur enough development interest for a
*useful* Java-native solution...
