Re: [platform-swt-dev] MacOS X port status?

["Mike Wilson/OTT/OTI" <Mike_Wilson@xxxxxxx>]

Andre,

It would be great if we could write down the "runtime behavior that is not defined as API or as JavaDoc" which you know about. That's exactly the kind of thing which belongs in a "porting guide", which is something that I think would be very useful. 

McQ.

Andre Weinand <weinand@xxxxxxx> Sent by: platform-swt-dev-admin@xxxxxxxxxxx 11/25/2001 04:34 PM Please respond to platform-swt-dev

To:        platform-swt-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-swt-dev] MacOS X port status?

<snip>
Sure, but we have to change lots SWT code.
I'm somewhat reluctant to throw out too much stuff that really 
defines the runtime behavior of SWT. Since I am using (and loving) 
SWT from its inception, I know that lots of our (that is JFace and 
JDT) code relies on runtime behavior that is not defined as API or as 
JavaDoc. If for example the order of events (calls to SWT Listeners) 
changes in the Cocoa implementation, some things may no longer work.
Another issue is how to keep track with SWT updates, extensions, 
fixes etc. If our implementation differs too much, it will become 
very difficult to track changes.
<snip>