Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-swt-dev] Mac OS X Port

My mistake. Allow me to call it JCocoa if you will. I agree with you about bypassing the JNI layer. Given that the question decomposes to where to encapsulate JCocoa calls. Should we do it in the widgets packages or in the internal packages by creating an aqua package.

Cheers

On Monday, November 12, 2001, at 04:29 PM, Mark Phippard wrote:


Correct me if I am wrong, but isn't JDirect a way to make calls to native
methods on a Mac, sort of like JNI?

I am suggesting that the port just bypass native methods and instead use
the Java classes that Apple has provided.  These classes encapsulate the
native method calls altogether, and let you just code in Java.

Otherwise, one of the problems you are faced with is that I believe you can
only code the Cocoa widgets in Objective-C and there are not a lot of
programmers that know this language.

Also, back to JDirect, on OS X can't you just use JNI if you do decide to
make native calls?  I think JDirect is provided to support OS 9.

Thanks

Mark






                    Suhail Ahmed
<ilyanov@xxxxxxx> To: platform-swt-dev@xxxxxxxxxxx
                    Sent by:                       cc:
platform-swt-dev-admin@e Subject: Re: [platform-swt-dev] Mac OS X Port
                    clipse.org


                    11/12/01 10:18 AM






Hi

It seems most folks would like to use Java bindings for Cocoa to port
SWT. Given the JNI layer (org.eclipse.swt.internal.motif (or win32, in
osx's case org.eclipse.swt.internal.aqua) exposes a class named OS
encapsulating the various native calls, we would have two ways to use
JDirect, one would be to call JDirect methods directly from the classes
found in org.eclipse.swt.widgets package or we could maintain the
porting layer but without using native calls from the OS class but
instead use JDirect calls. Any thoughts on this?

Cheers


On Monday, November 12, 2001, at 03:49 PM, Mark Phippard wrote:

I just want to add my vote for a Mac OS X port.

With its BSD underpinnings and easy to use UI, I think that OS X has the
potential to become very popular among developers and it deserves
consideration as a supported Eclipse platform.

OS X comes with a set of Java classes that wrapper their native Cocoa
widgets.

This URL has everything you need to know about Cocoa:

http://developer.apple.com/techpubs/macosx/Cocoa/CocoaTopics.html

A couple of links off of that URL are to the docs for the Java classes:


http://developer.apple.com/techpubs/macosx/Cocoa/Reference/ApplicationKit/
Java/AppKitTOC.html


http://developer.apple.com/techpubs/macosx/Cocoa/Reference/Foundation/Java/
FoundationTOC.html

I do not have the right background to assist much in the programmin
effort,
but I am certainly willing to help in testing.

Every copy of OS X has Java 1.3 with Hotspot VM.

If anyone knows of some good Mac development forums or mailing lists,
please post them.  I think we should go to those places to try to
solicit
some Mac programmers to come over to Eclipse and help out.

Thanks

Mark Phippard




_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev

_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev






Back to the top