Posted by gouessej on Nov 10, 2013; 4:54pm
URL: https://forum.jogamp.org/Onscreen-vs-offscreen-performances-tp4030556p4030565.html

JCanvas3D is a JPanel that uses both an internal Canvas3D and a BufferedImage. Canvas3D is an AWT Canvas that uses a GLCanvas (created by using a JAWTWindow and the native window factory) if onscreen otherwise it works a bit like JCanvas3D. Java3D uses JOGL windowing very poorly, any scenegraph using our canvases a lot more straightforwardly can get better performance, even Xith3D (but this one is almost no longer maintained or its activity is extremely low). Keep in mind that Java3D 1.5.2 had to support several "pipelines" including some of them not based on JOGL which leaded to poor design choices and when I started porting it to JOGL 2.0, it was already difficult to keep the public API unchanged, I couldn't rewrite Canvas3D and JCanvas3D from scratch.

If the JogAmp community could port PureSwing or something equivalent to JOGL 2.x, we could port Swing based applications to JOGL + NEWT.