Yes, QTJava is basically the only game in town, but it's still
eminently usable and good enough to ship in my opinion, as long as
you're careful and don't mind tinkering a bit (eg. using JNI if you
need access to newer APIs).
Yes, there are a few major annoyances such as lack of updated
documentation and sample code, but apart from fiascos with various
recent update installers on both Mac and Windows (which can generally
be resolved by reinstalling QuickTime with the standalone installer)
I don't think Apple have introduced any new bugs or memory leaks the
last few years. On the contrary, they have continued to support it
(eg. for Leopard) and provide fixes (albeit with a disappointing
level of commitment).
Apple want to concentrate their limited QuickTime development
resources on iPod+iTunes+FinalCut rather than supporting technology
they don't see as strategic. Obviously they would like the whole
world to develop in Objective C and Cocoa, but that's simply not
going to happen if you have any interest at all in developing
Java's not going to go away. Windows and Linux aren't going to go
away. The only thing that *might* happen is that the hordes of
developers that have come to Mac OS X in recent years might go away.
I don't think Apple are so stupid not to realise that, however, so
I'm not unduly pessimistic about QTJ.
I share your frustration however.
(Before anyone corrects me, I realise Linux doesn't support
QuickTime, but these comments apply just as much to the situation
with Java 6 as they do to QTJ.)
I'm glad you're positive, and I share your JMF pain. Yes, QTJ is pretty
much the only game in town, but the reason I'm
so cross is that the only game in town isn't good enough to ship anymore.
Square Box Systems Ltd
Do not post admin requests to the list. They will be ignored.
QuickTime-java mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden