Re: Cocoa Java vs Swing Java classes
Re: Cocoa Java vs Swing Java classes
- Subject: Re: Cocoa Java vs Swing Java classes
- From: Chris Hanson <email@hidden>
- Date: Sun, 14 Oct 2001 17:25:37 -0500
At 9:54 AM +0100 10/14/01, Finlay Dobbie wrote:
As someone else pointed out when you use Cocoa Java you lose
portability, but then you can probably keep all your model and
backend for your application and just rewrite the UI layer. It's up
to you, though.
The advantage to Cocoa Java is that you can *easily* re-use Java code
from other projects while building an application very quickly that
fully implements the Mac OS X look and feel. For some people, this
isn't a big deal. For others it may be. Some people are content to
write Objective-C that calls Java through the bridge, others aren't.
This advantage extends to database applications right now too, since
EOF 5 is only available as a Java framework (and only as part of
WebObjects). Also, when building WebObjects applications using Cocoa
Java Client could be a significant value-add for things like
administration tools if you know users are going to be running Mac OS
X.
-- Chris