Posted by Sven Gothel on Mar 21, 2011; 5:23pm
URL: https://forum.jogamp.org/Application-AWT-NEWT-tp2707118p2710848.html

On Sunday, March 20, 2011 21:48:20 Itun [via jogamp] wrote:
>
> Much time I wasted  for graphics implementation and now I need a complete
> application with GUI.
> I use AWT/GLCanvas methods of rendering, but I` ve heard that it is bad. And
> NEWT is a native good variant. I look through internet and don`t find
> something  distinct about NEWT, only it is the best variant. May be there is
> books about NEWT or something certain?

sorry, but we have our unit tests and javadoc api.

NEWT is a good alternative for a windowing system,
but it does not tackle UI rendering.

> Because I have not time to look
> through all JAVADOC and write my own windows with GUI elements by hands (I
> think for this major moment must exist an editor, doesn`t it?).

yes, it's a common problem, sure.

UI is: rendering (output) and input event handling,
probably within an convenient API.

Right now we only offer the very basics, no UI API / tool yet.

However, there are many teams working on UI support right now,
starting with curve and font rendering.
But it will take a while until this becomes production stable.

> And an other one question, how to create two treads: one for GL rendering
> and one for windows handling?

NEWT does the window handling, input/window event/action thread already implicit.
You would only need to take care of your GL rendering thread.

> Thank you!

~Sven