Xcode 3.0 actually has improved support for Java in a lot of ways,
and of course the Java team continues to integrate new Java
releases from Sun into Mac OS X.
I think perhaps what you're referring to is that the Java API for
Cocoa was deprecated at last year's WWDC. That API was an attempt
to wrap every Cocoa API in a corresponding Java API so you could
write Cocoa apps using Java rather than Objective C. The mismatch
between APIs proved to be too great, though, and it was too hard to
keep the Java API in sync with the Cocoa API, so the Cocoa team has
deprecated the Java API for Cocoa.
You're right, that's mostly what I was referring to. But I'd much
rather write in Java than Obj-C, so I consider it a loss. Even if it
weren't the case, I'd much rather write in C++ (or D!), and use the
Carbon API (which I still prefer. I think it's cleaner, and doesn't
have the legacy style of Cocoa).
However, the standard Java APIs (AWT, Swing, all of the standard
extensions) are and will continue to be fully supported, and
Xcode's support for Java will continue to improve.
Yeah, well, the standard Java GUI really leaves a LOT to be desired
on the Mac. I use the Mac because it is the details that are
important to me, and Java (as well as all those "cross-platform"
toolkits) seem to step all over the details.
--
Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
