>From my reading of the comments it seems that it is only the
Java-Cocoa pieces that are going away. I suspect that if you are
using the bridge to talk to Java libraries everything will remain
functional. Time will tell but I would be surprised if they shut the
bridge down completely.
On 7/11/05, Brad BARCLAY <email@hidden> wrote:
>
> On Jul 11, 2005, at 11:31, Brad O'Hearne wrote:
> This was posted today on TheServerSide -- anyone have any comments? As a
> Java developer, I'm curious if Apple is trying to ween Mac app developers
> from Java and steer them toward Cocoa development
>
> All I can say about this is: I hope they don't!
>
> I'm in the situation where I have a very large, existing library of
> existing classes in Java which have taken several man-years of development
> (with only one "man" at that). It encapsulates protocols, hardware
> communications and abstraction, and a LOT of data manipulation. Re-writing
> all of this in Objective-C isn't really realistic.
>
> However, as this engine was designed to allow any GUI to be easily
> layered atop it to create an application (via a callback interface such a
> GUI needs to implement), creating a Cocoa-Java version has been a snap. I'm
> now able to give Apple users of my software a tightly integrated version of
> my app for their (and my!) platform of choice, while still supporting Linux,
> Windows, and OS/2 users via the standard Swing interface.
>
> I'm no stranger to Objective-C -- some of my recent projects have been
> pure Objective-C -- but re-writing all of this heavily tested Java code to
> Objective-C isn't feasible. Which either means I'll have to retract my
> Cocoa support and have Mac users use the same Swing GUI everyone else is
> using, that I'll simply have to eschew whatever new features are added to
> Cocoa but aren't reflected in Cocoa-Java, or that I'm going to have to write
> my own JNI routines to access said features.
>
> (Of course, I suppose the Open Source community could always create its
> own libraries to encapsulate the functionality for any Cocoa routines which
> aren't in Cocoa/Java. Hey Apple -- if you're not going to maintain this
> technology, why not Open Source it so the community can keep it up for you?)
>
>
> Brad BARCLAY,
>
> Lead Developer & Project Administrator,
>
> The jSyncManager Project.
>
>
>
>
> =-=-=-=-=-=-=-=-=-=
>
> From the Mac OS X Desktop of Brad BARCLAY
>
> E-Mail: email@hidden Web: http://www.jsyncmanager.org
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Java-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/java-dev/email@hidden
>
> This email sent to email@hidden
>
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
