"John Keiser" <[EMAIL PROTECTED]> writes:
> Is there anything that makes that unusable in our AWT
> implementation?
The better question is -- What makes it usable in our AWT
implementation? It mixes GTK and Java, but in an entirely different
fashion than what is needed to get AWT peers up and running using GTK.
> 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.
If you mean writing Java code to call Oliver Gutknecht's library,
that's probably not a good idea. Calls to GTK need to be batched
together, and done quickly, in C code -- this is mainly due to
threads, and the fact that one AWT call often maps to many GTK calls.
Going out to native land and returning multiple times for one AWT call
wouldn't be efficient -- especially when you consider all the mutex
locks required.
--
Paul Fisher * [EMAIL PROTECTED]
