Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
Re: Im starting to despise java programming for the mac (QT4Java)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Im starting to despise java programming for the mac (QT4Java)



Adam Ornstein wrote:

So... In other words, I should just commit application suicide now, and avoid potential customers purchasing my application and being extremely upset that they cannot use it?! I suppose I can develop using jni and learn the new code-base... but I dont have a 64-bit mac, and Im in extreme start-up mode without enough cash for the investment (for now). Any advice for me moving forward, other than purchase a brand spankin new mac and spend a month learning, and converting my app to work with these new libraries and JNI? I think the best idea would be to simply abandon using mac libraries altogether and
spend the month making pure java code that can make an avi.


Im amazed that by choosing to use java so that I could port my app most easily to the mac and the pc, AND choosing to use Quicktime libraries - libraries that come directly from Apple, I have indeed screwed myself for 64 bit processor macs.

I had thought that QT4J was developed by the QT team, not the Java guys, so it could be that a 64-bit version is pending -- QT scheduling priorities are probably very different. QT4J has had a turbulent history, there was a period of time around the 1.3.1 -> 1.4.1 transition (when Java was moved from Carbon to Cocoa) where QT4J didn't work very well. It did come back (albeit with an incompatible API) eventually.


My advice is to limit your app to run in Java 1.5 for now, and watch how the QT4J situation evolves. If you want to hedge your bets, look at moving to QTKit over time. Our application's webcam interface (QT Carbon-based C code via JNI) also got totalled off by the move to 64- bits (all Carbon APIs were dropped), but it only took me about 2 weeks to rewrite for QTKit (it went *much* faster than I anticipated). Moving to JNI will mess up single-source cross-platform code, so you'd need to do some architectural changes to handle it (we already had those structures in place).

As a rule Apple does not talk about its future plans, so you'll have to decide how to proceed without knowing what Apple will do. That sucks, but nobody on this list has the power to change that.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2011 Apple Inc. All rights reserved.