Posted by Wade Walker on Oct 19, 2010; 2:08am
URL: https://forum.jogamp.org/New-tutorial-for-JOGL-in-Eclipse-RCP-application-tp1670638p1729715.html

gouessej wrote

I see what you mean but I spoke to some members of the Eclipse Foundation and it is clear that the OpenGL binding of SWT is not actively maintained. I don't say that it has to be thrown into the tashbin but we have to be aware of this problem.

You're right, I looked at the SWT bug logs and I can see that not much work is done on SWT GLCanvas. If I run into problems, I will ask the JOGL community for advice and maybe switch to the JOGL GLCanvas at that point.

gouessej wrote

Wade Walker wrote

I can't claim that there'll never be a problem with the way I'm doing things in these tutorials. But I can say that I've used this way at work for about five years on a very complex engineering application, and I haven't run into an insurmountable problem so far

Did you measure the memory footprint?

Our engineering/science apps are not as graphically demanding as games are  We may have 2 million triangles per scene, but not many textures, so the graphics memory usage is only maybe ~50MB.

Our memory usage is almost all in the Java heap, and we run into the 32-bit limit there all the time because of our huge data sets. We use the Eclipse Memory Analyzer to do heap profiling, and it's been very helpful in shrinking our memory footprints.