Posted by Sven Gothel on Jun 21, 2012; 9:43am
URL: https://forum.jogamp.org/Issue-with-Java-3D-under-OpenJDK-7-Mac-OS-X-tp4025259p4025280.html

On 06/21/2012 11:15 AM, Manu [via jogamp] wrote:
>     gouessej wrote
>     would it be difficult for you to switch to NEWT on the long term?
>
> Sorry I don't know NEWT and I'm not the kind of person ready to jump on a new
> API each time a developer creates one.

NEWT is already quite mature, initiated around 2008.

> Until now, I'm quite happy with Java3D, and if I had to give it up, I'll
> probably jump to OpenGL or a thin API over OpenGL like JOGL.

Well, I guess the question was weather you use Java3D or JOGL directly,
but weather you would be OK to use a NEWT Window instead of an AWT
Canvas/GLCanvas _with_ Java3D.

This would require you to rewrite your event input handlers,
which is not a big task - since we use _same_ names and semantics.

> Can you give me more information about NEWT and why do you think about it?

https://jogamp.org/jogl/doc/NEWT-Overview.html

However, as mentioned previously, even if using NEWT,
in case the NEWT Window is attached to AWT (NewtCanvasAWT, Applets)
the offscreen issue remains - and needs to be solved.
So maybe switching to NEWT would not satisfy in this regard.

One reason for switching to NEWT is to benefit from
better input responsive, i.e. NEWT won't lag your user input (mouse/key/..).
This is described in the URL above. A few projects already using NEWT
in this regard.

~Sven