[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[platform-swt-dev] Re: Mac port: Status Update
|
Why not try a JNI -> Cocoa/ObjC bridge? There shouldn't really be any
technical problems that I can think of, if the library maintains that
one-to-one. Certainly it means doing what is effectively a new Java
bridge, but we'd have to do that with Carbon anyway. And it's different
than the traditional OS.java procedural API approach, but that may not be a
bad thing.
I just think (and I think you'll agree) that Cocoa would be more exciting
to work with when porting *all* those widgets. :-)
Cheers
Stu
---------Original Message ----------------
From: Maurice Parker <maurice@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 07 Dec 2001 08:23:05 -0600
User-agent: Microsoft-Entourage/10.0.0.1309
Hey,
I didn't have any luck finding out what the problem with using Cocoa's
Notification Center from Java was. At this point I am assuming it is a bug
in the JavaBridge most likely attributed to the use of NSSelector (a
reflection like mechanism).
I know how to work around this bug, but I'm not really sure that I should
try at this point. I've posted to the cocoa-dev list twice reporting
problems with using the JavaBridge and haven't yet received a reply back
from an Apple employee. Once I even cc'd an Apple employee who directly
involved in a thread on the JavaBridge and I still didn't receive back a
response.