Using JOGL with my favorite IDE (Eclipse)

OpenGL Development JOGL Development
#1

Hi!

I’m developing with JOGL using Eclipse. When I use the auto-completion of Eclipse I run into 2 problems:

1.) The Source for GL.java is not provided in the sources of JOGL. So, the auto-completion of Eclipse only gives me argument names like arg0, arg1, …, argN. So, I have to switch to the the documentation very often. To create the GL.java is a very complex build process and I think it is too much oberhead only for having right argument names. So, it would be better to provide the GL.java in the JOGL sources.

2.) Typing gl.gl in my source is most of the time really pain. Eclipse hangs for over a half minute until it shows me a list with all methods of the GL class. Is this an Eclipse problem only? Is the auto-completion of NetBeans more performant on classes with very much methods all starting with the same 2 letters?

I’m very happy about the JOGL project, but these 2 things make it very unconfortable to work with it in Eclipse. Is there somebody who ran into the same problems and has solutions for this?

Thanks
olli73

#2

Hi,

I don’t use eclipse (and i hope I won’t have to) but that’s a matter of taste… But I can anwser you on the Netbeans part.

  1. You have to link javadocs to the librairy ( in fact it must be the same in Eclipse so you’ll have more explicit arguments for the methods.

  2. The completion is quite fast (not as fast as a completion on a class with two methods but only 1 or 2 secs).

#3

I use JOGL with Eclipse as well, and experience the same issues as you do olli73. Although I wouldn’t really call the first thing an issue as there is no GL.java source file. The auto-completion thing is a bit of a pain though: hella slow after typing gl.gl. Only way around it so far is to get to know the naming convention of OpenGL functions, and type faster than auto-completion can react ::slight_smile:

#4

Same thing happens to me, agree it is a real pain espessially with gl.glXXXX - on my (not to powerfull) PC Eclipse will hang up for couple of minutes :-\

I can confirm that linking javadoc etc… will not help with autocompletion (on Eclipse at least), argument/parameters would read properly though but only that…

#5

I experienced the same auto-completion problem in Eclipse for the GL class and the solution I had was to change the delay for completion dialog to a higher value such as 700 ms. It’s far from perferct but at least eclipse doensn’t hang up.

#6

Please file an RFE using the Issue Tracker on the JOGL home page and we’ll give this some more thought in an upcoming release. In general I don’t want to get in the habit of keeping around autogenerated source files, but this has come up several times and maybe we should ship a “generated/” subdirectory in some of our bundles (the format of which will be changing) to make things easier.

#7

A long time ago (well no more than one year and a half maybe) I remember that some issue were sent to Netbeans because autocompletion with jogl could lead to hang ups … The netbeans guys took the issue into account and the problem disappeared. So maybe I can be useful to fill a bug or a RFE into Eclipse too…

PS : I don’t want to launch an IDE war here, that’s not my point.

#8

I don’t have such a major problem, but my machine is quite fast.
Eclipse 3.2 is noticably faster than earlier versions for me, so I suspect that might help.
I suspect you are short of RAM more than raw CPU power, but I could be wrong.
I have seen Eclipse slow down when I was short of RAM.

#9

Great, it works! When the javadocs are linked to the library, a task with the name “Computing additional info” starts when using the auto-completion the first time after starting Eclipse. The task runs a few (more) seconds. When it is done, the next time you use the auto-completion Eclipse provides the correct argument names. The first time I tried this I didn´t notice that and gave up too soon. But I still think it is the better way to provide the source of GL.java, so I will open a RFE at the JOGL project pages.

I did some more research on the hang-up problem. I noticed that the hang-up appears when typing the first letter after the auto-completion shows the list of the possible methods. The list with the methods comes up very fast. I think it is an Eclipse problem. I will report a bug there and forward the response to this forum.

Greeting
olli73