Window, frame, display, these are can be fairly generic terms. I mean separate, floatable JFrames on a users desktop, each with a unique GLCavnas, and each canvas with unique (one or more) textures (mesh and image), that are unique themselves from the textures in the other JFrames. I don't care about sharing the image data or the mesh points between JFrames, in fact I don't want to. Here's one of our applications, it's not sexy like a game, but leverages texture mapping for fast, efficient rendering of high resolution of satellite remote sensing imagery:
Here there are three separate JFrames on the desktop. We have other applications with full, interactive 3D views, visualizing numerical weather prediction model output for example.
I may have misunderstood an earlier post, but I was assuming this would be okay, and one of the main reasons we decided not to go with JMonkeyEngine.
Are you saying there needs to be some coordination between the FrameHandlers? I have on per Canvas, should there be only one per application which updates the canvases together?