Re: [platform-swt-dev] Re: Help port IBM's Eclipse to OS X

[Stephane Boisson <sboisson@xxxxxxxxxxxxxxxx>]

le 17/11/01 16:07, Martin Sturzenhecker à msturzen@xxxxxxx a écrit :
> In case you didn´t read the mail archive yet, get yourself an account to
> read the newsgroups. This account will anble you to read the mailing
> list archives too.
> 
> Them come back and let us know your position.

I am new to SWT/JFace, and althrough I completly share the SWT/Jface
"vision", I am not aware of all the in and out of this framework..
I am an early Mac user and a very experienced Unix developper (mainly
Motif). 

My point of view is:
- Java Cocoa bindings provided by Apple: For me, I don't think we can make a
thinner bindings. The Java Bindings are almost a 1-to-1 binding to the
Objective C original API (was [Next/Open]Step). Why re-invent the wheel?
IMHO Cocoa is the most mature OO GUI framework. But It seems they are issue
with the some event things in SWT, I don't know yet enough about it..

- Carbon and Java. Carbon is for easily porting classics apps. The only
reason I would go for carbon would be for plain C (excepted Quartz, the
rendering engine, real Cocoa bindings don't seems to exist for other
languages than ObjC and Java because Cocoa is pure OO) and OS 9
compatibility with "pascalish" style. But, remember that on OS9, Java
lastest version is still 1.1 (Through I don't know exactly about the JDK
requirements for Eclipse)...

So I vote for CocoaSWT

Stephane