Re: [platform-swt-dev] SWT for MacOS X

[Mike_Wilson@xxxxxxx]

Just to clarify the point "only minimal changes to the SWT source code" isn't really the SWT philosophy, although it _really_does_ make sense to structure the code the way you have given the investigation phase you are in right now.

The final version of the port should, for example, have all of the "helper" methods that are currently in OS.java deleted and the code which is in them moved into the places where they are actually used.

The philosophy of SWT, such as it is, is to remove as many layers from the code as possible.

McQ.

Andre Weinand <weinand@xxxxxxx> Sent by: platform-swt-dev-admin@xxxxxxxxxxx 02/06/2002 06:14 PM Please respond to platform-swt-dev

To:        platform-swt-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-swt-dev] SWT for MacOS X

Hello,

Mike Wilson has just installed the latest drop of my 'SWT to MacOS X' port
on the SWT Development Resource page (thanks Mike!):

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-swt-home/dev.html

You can find it at the bottom of the page (In order to download the 
image I had to press the option key).

The archive contains a Project Builder project with almost all of the 
SWT sources, my Carbon/JNI files and a sample program. You can just 
press the Build & Run button in Project Builder and after two minutes 
a sample app called 'Eclipse' should appear.

The sample shows only the StyledText and the (emulated) Tree widget. 
I've picked these widgets because their implementation touches many 
important areas of the SWT implementation. In a future version of 
this port the Tree will be replaced by the native Carbon tree.

My SWT port to MacOS X tries to adhere to the SWT philosophy:

- almost no code and no logic in the C portion of the JNI implementation.

- only minimal changes to the SWT source code (of the Motif version).
   Otherwise keeping up-to-date with SWT would become a problem.
   In addition I didn't want to throw out code (and semantics) too early.
   If I didn't understood an implementation detail of the Motif implementation
   I commented it out so that I have a documentation of what is still missing.

- most of the port is confined to four classes in SWT's internal package.

- no introduction of an additional hierarchy of 'peers': SWT uses 
Carbon controls
   via handles.

OK, that's all for today...
--andre

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