[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-swt-dev] status of cvs for Mac OS X port?
|
Hey,
Whoa! Andre, slow down and save some work for the rest of us. ;-)
I wish I had known about the presentation before JavaOne. I was just
around the corner at the 4th Street Bar & Grill (at the WebWork gathering)
when everyone was at the Thirsty Bear. Heck, I was at the Thirsty Bear
for the JBoss sessions earlier that day. Bummer...
At JavaOne, I finally got the low-down on what went wrong with using the
Cocoa API's from an Apple engineer. If you don't initiate the interface
between the Cocoa and Java environments from Cocoa, you will experience
subtle, and random threading problems. Basically the Java Bridge will
never work for SWT in it's current form and may never be able to be used
in this way. Thank goodness we got the Carbon API's added to Mac OS X or
SWT wouldn't be possible at all!
McQ, could you please remove the BlackMoon code from the Eclipse website?
The only people that would be interested in it will be Apple engineers
trying to debug OS X's Cocoa/Java integration. ;-)
Back to the task at hand. Andre, I was trying implement live window
resizing last night on your last code drop, and found that I needed the
new Carbon Event Manager to get it done. I see that some code for it is
in there for the newer Event mechanism. Any updates to that code recently?
I don't want work on the Event mechanisms if you've done a lot of recent
updates.
-Maurice
On Tuesday, April 2, 2002, at 02:57 PM, Andre Weinand wrote:
I saw some activity a couple of weeks ago on the eclipse.org cvs server
that indicated that 'mcq' had added a folder hierarchy for Mac OS X
carbon support. Does anyone know the status of this?
A brief status update:
Last week I got Eclipse up and running on the MacOS X port of SWT (see
attached screen short).
I can import, edit, and build JUnit and most of Eclipse's functionality
works, albeit with small glitches and UI quirks.
Erich Gamma gave a demo of an early version of this work at JavaOne.
Because of this I decided to prioritize the demo work for JavaOne over
the effort to get the port into CVS.
I'm planning to get my code into CVS soon. However, I would prefer to
become self-hosting first :-)
Working with the CVS setup from within Eclipse would be much simpler....
--andre
