Re: JOGL Error in Eclipse on MacOSX
Posted by
gouessej on
Nov 05, 2010; 9:59am
URL: https://forum.jogamp.org/JOGL-Error-in-Eclipse-on-MacOSX-tp1835239p1847287.html
Ric Wright wrote
Well, I guess I would dispute the "trivial" part. The background for this is that I am writing an Eclipse perspective that allows one to write Java-based modelling, kind of like VTK. This uses Java reflection to allow users to write a single (or multiple) module that performs some modelling effort and is automagically integrated into GMS. As you can see from the attached screenshots, this is not a simple app and integrates all sorts of SWT and WST functionality, uses Java reflection extensively and supports a complex JOGL based library that implements a pretty complete implementation of the PostScript APIs. The tempwave animation you see in the screenshot runs easily at 60 FPS on each system I have. Primary bandwidth problem is the tesselation in GLU since I have to tessellate the PostScript strokes.
I have this running on WinXP 32bit, Win7 64 bit and MacOSX. I don't have a Linux box these days so I don't know about that.
So I feel that this is pretty non-trivial. But it is currently based on JOGL 1.1.1. I thought it would be interesting to look at JOGL2, hence my experiments. But frankly, JOGL 1.1.1 and the SWT_AWT bridge is working for me, so I'll probably stick with it for now. My focus is getting GMS done and I don't want to fight the tools. But I appreciate the awesome jobs you and the rest of the JOGAMP team are doing and am looking forward to the release of JOGL 2.
Cheers, Ric
gms_overview.JPGgms_datasets.jpggms_views.jpggms_project_gms.jpg
Actually the first "problem" I evoked is platform-dependent (it happens only on Linux), you can reproduce it easily by creating an embedded composite and putting even a simple SashForm into it.
The second problem happens only when you enable the debug pipeline very early.
Therefore,
they do not bother you if you don't mind of Linux and if you never use the debug pipeline at the launch of your application. However, your tutorial is on the web, some Linux users might have the same problems than me (I'm permanently on Linux), it would be useful to update your tutorial in order to include my unfortunate "findings":
- use the workaround of the bug 6678385 on Linux to avoid some exceptions when creating an AWT frame with SWT_AWT or use the JDK 1.7
- create the GLAutoDrawable instance (GLCanvas or GLJPanel, start the animator, etc...) rather in a ComponentAdapter set on the frame and called once when the frame is resized for the first time (override componentResized(ComponentEvent e))
- call doLayout() on this frame after adding the GLAutoDrawable instance into it
If you prefer, I can write a small tutorial in which I refer to yours and I add these things.
I use VTK too.