Re: SWT issue with current Mono

Steven Brown wrote:

> SharpWT on GTK needs to have the native glue library removed, one way or
> another.  It's vestigal from SWT I believe (JNI), and probably only
> exists as no one had gotten around to doing all the MarshalAs goo
> required to stub the more complicated functions, or it didn't work on
> Mono at the time.  I'd suspect it'd be a lot easier to finish C#-izing
> the remaining stubs in the glue library (and fixing things like missing
> uses of IntPtr) than changing it to use GTK#, as the GTK layer assumes a
> procedural GTK library, and going forward, merges in from SWT will be a
> lot easier if these assumptions aren't changed.
> 


Hi

It's true, the glue lib is only there because ShatpWT/GTK is a port of SWT.
I know there are some problems with unicode and gtk, but I don't think 
its the problem of the glue lib. The main part of the glue functions 
have nothing to do with strings (AFAIRC).

I think it would be nice to remove the need for the glue library, but, 
you can be shure, it's not as easy as it sounds. The problem is, that at 
  several places calls are used that results in precompiler macros. And 
you can't access precompiler macros as external functions from C# code.
If the macros only would have 2 or tree calls to other functions (!), it 
wouldn't be a problem to convert them. But some of them do calls to 
other macros and they call more macros.

I'm shure it would be possible to have this all in C# and it would be 
nice, but it have to happen in a seperate class (glue), or you will 
introduce many differences between the java source and the c# source.


regards
Dominik