Is there anything that makes that unusable in our AWT implementation? Maybe
it'd be best, instead of using native calls, to just do a pure Java AWT that
talks to the GTK stuff to create windows and such.
Just a thought, I'm no AWT expert.
--John Keiser
> -----Original Message-----
> From: Paul Fisher [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Fisher
> Sent: Wednesday, October 07, 1998 4:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: more news on gtk + java
>
>
> Brian Jones <[EMAIL PROTECTED]> writes:
>
> > Anyway, the point being there is part of the job which is getting
> > the AWT peers in GTK+ and someone pointed out the classpath effort
> > and Chris Toshok's involvement here. If you need some help Chris or
> > want to coordinate with [EMAIL PROTECTED]
>
> Your message seems to imply that Oliver Gutknecht is doing AWT peers.
> He's not. He's doing a 1 to 1 mapping from GTK+ to Java. While it's
> certainly a good thing to do, this hardly applies to mapping GTK+ to
> the AWT.
>
> --
> Paul Fisher * [EMAIL PROTECTED]
>
>
