Re: [platform-swt-dev] GTK in CVS

[Steve_Northover@xxxxxxx]

Yup, we'd add custom code as a last resort.  The idea though is to
develop, port and debug in only one language.  We could probably
write a new GTK widget in Java by malloc'ing things in the OS with
the correct shape and registering in a few places.  It's not like QT
that requires a preprocessor.

The current approach to a platform binding is customized for Eclipse
and has pretty low overhead. Motif seems chuggy because Motif is
chuggy, but Eclipse does drive SWT pretty hard - all the more reason
for us to be as thin as possible - give the cycles to the app and all that.

Is fixed "fixed" in 2.0?  Looking at the GTK 2.0 API causes me to drool.
Many things that are half implemented and hacked in the SWT GTK
port on 1.2 seem to be directly supported by GTK 2.0.

Steve

Havoc Pennington <hp@xxxxxxxxxx> Sent by: platform-swt-dev-admin@xxxxxxxxxxx 12/06/01 05:42 PM Please respond to platform-swt-dev

To:        platform-swt-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-swt-dev] GTK in CVS

Steve_Northover@xxxxxxx writes:
> > I'll try to check these out in the examples. The Sun guy doing the GTK
> > AWT peers ended up writing a simple custom widget that was a variant
> > of fixed, so he could get the desired behavior exactly right.
> 
> I was hoping that we wouldn't have to do this.  SWT contains no custom C 
> code, only wrappers
> for operating system calls.

Right. Well, it can probably be done with only wrappers, but most
likely that would involve enough weird hacks that the resulting mess
wouldn't be worth making just to stick to the "no custom C code"
guideline. The custom C code here should be really simple and
straightforward.

There was some discussion of java-gnome earlier - I'm not sure if
java-gnome supports deriving new widgets in Java; the Python and C++
bindings do support that, but it's a bit complicated to implement on
the language binding side in a reliable fashion.

A java/gtk binding that does allow it will involve some custom C code
(in the binding library) and add some extra overhead vs. your current
approach, however. Language binding overhead usually isn't a big deal
but might be for something as large as Eclipse; the Motif port seems
to be chuggy just because of the sheer number of widgets involved.

I guess we still don't know if a custom widget is required though; I
don't have a good handle on what the current resize issues are, yet.
Also, as usual, GTK 1.2 vs. GTK 2 is going to make a difference.

Havoc


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