Posted by gouessej on Feb 10, 2018; 9:20am
URL: https://forum.jogamp.org/Independent-Textures-tp4038596p4038621.html

Maybe I misunderstood what you wrote. Do you absolutely need to share the textures on all those windows? If it's the case, you'll have to consider numerous limitations:
https://blog.gvnott.com/some-usefull-facts-about-multipul-opengl-contexts/

Otherwise, if you need separate parents but if you don't need to share the textures (i.e you'd need to load a texture on each canvas using it), it will be only a matter of using the frame handlers correctly and the example I quoted might be useful.

Keep in mind that using shared contexts can have a bad impact on performance and stability. What is already supported in JogAmp's Ardor3D Continuation is an acceptable compromise.

JogAmp's Ardor3D Continuation exposes its canvases and windows as JOGL canvases and windows, it helps to use this but there are some drivers that don't support shared contexts. That's why, if I were you, I would be very reluctant to heavily rely on context sharing in a general framework.

I encourage you to use a JDesktopPane like in the example, it's typically designed for this purpose, it's a container. Some CAD softwares use another "trick", they create an always hidden (J)Frame.