[keinfarbton]

@svn rev. 331
After thinking again about the ClassInfo.find method, i realized, it can use it to make the initialization process dynamic, without importing the called modules.

Changes in application size (wizard)
Linux: 12.0 MB => 10.5 MB
Win32: 32 MB => 11 MB

Further application size down can be expected, as soon as DMD will get reflection for methods and fields.

Compilation was done without any special flags. Using -release -O, or using a "strip" tool, can probably reduce application size some more.

Other changes:
* I added the module swt.eclipse.swt.All

[bobef]

Nice. You are doing some really great work with this project.

[keinfarbton]

thx
i hope, the time will come, were ppl start to use it.

[bobef]

Oh the time will come very soon, don't have a doubt about it.

[gileadis]

I'm a couple months away from starting a project I want to use SWT on. I'm quite impressed at the amount of great work which has been done on Tioport and SWT, and I'm looking forward to working with it.

Besides other project considerations, I'm more or less waiting for the port to be more stable (more samples working) and the API to settle down (i.e. regarding strings, delegates, etc.).

Also, I may have some limited time to give to this project. If you have a particular place in the code (perhaps implementing particular Dejavu methods) you'd like to be worked on, I can take a look. I'm not a D wizard, but I can certainly work on hooking Dejavu methods to call Tango methods, etc.

[keinfarbton]

Hm, the examples are very time consuming for me. ATM I don't work on them. Most missing things are related to unimplemented dejavu methods.

So the bad thing, you will not get more "stable" examples.

The good thing, if you want to contribute, why not do the examples?
Good changes for you to collect some experience with SWT for your project, and to give me bug reports and feature requests.

The implementation of dejavu methods is independent of any changing API of SWT.

Frank