Re: Differences between Cocoa and Cocoa-Java Projects/Targets
Re: Differences between Cocoa and Cocoa-Java Projects/Targets
- Subject: Re: Differences between Cocoa and Cocoa-Java Projects/Targets
- From: Dmitry Markman <email@hidden>
- Date: Sat, 19 Feb 2005 00:01:26 -0500
I wouldn't say that JNI is extremely complicated
I would say JNI is is extremely straightforward
JNI is java's standard and as such is widely supported by SUN and Apple
JNI is no more complicated than any other API.
however you have to know how it works
just like any other API you want to use, nothing new
to me Cocoa-Java bridge looks like ugly and complicate thing
just opposite you think
but maybe you have some specific requirement that you have to use Java
from Cocoa
if you need just GUIless classes it shouldn't be any problem working
with JNI
it' just very similar to work with other dylib
On Feb 18, 2005, at 2:26 AM, Phil wrote:
On Thu, 17 Feb 2005 17:57:37 -0800, David Dunham <email@hidden>
wrote:
I heard the same information as Finlay last month. The developer
whose issue this was seemed happy to use JNI (since it's new
development).
Really? I only need to use a few functions of a Java Library in my
application. JNI seems extremely complicated to get going and the
SimpleJavaLauncher application doesn't even run.
On the other hand, the bridge seems simple, easy and fast to get going
(and the runtime handles launching the VM).
Now I'm even more confused than when I started.
-Phil
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Dmitry Markman
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden