Posted by adam_law on Jul 13, 2015; 4:06pm
URL: https://forum.jogamp.org/GLJPanel-for-LibGDX-JOGL-backend-tp4034741p4034887.html

gouessej wrote

Oracle will implement an equivalent of JAWT for JavaFX/OpenJFX in Java 1.9, it will help us to provide an equivalent of GLJPanel for JavaFX/OpenJFX. In the meantime, it's a waste of time to me. The JavaFX 3D API seems to be a bit better than Java3D but it has the same caveats than its older versions...

Ah. Very good indeed. September 2016 is a bit far off and I think any real work based off it will start to come out in 2017. But you're right, and I think everyone else in this part of the industry feels the same way (which explains all those "I haven't bothered with JavaFX yet." replies I got haha).

gouessej wrote

The difference is that their AWT support is worse and they have no equivalent of GLJPanel actually. They call their classes "Swing*whatever" but they use only AWT classes under the hood.

I was just about to say most of the very same things :)) Especially the GLJPanel part. I'm just wondering, because I don't know anyone working in the LibGDX team personally, is it because there're LWJGL members there that LWJGL is the de facto standard there? Just curious.

gouessej wrote

You should look at all tips in the bug report about JavaFX/OpenJFX and JOGL, I probably forget some of them. Aqd's advices at the very end is very important under Windows.

Yeah, I figured as much. I went back to that article before coming back here to right this. I was tracing the process where the GLCaps were being set, and it does fail on setting ES2 (I set it to try for ES2 before failing to GL2).

gouessej wrote

As you wish. The solutions based on other APIs have some performance problems too anyway.

I did post on the ticket I opened on Git, though it was already closed when I got there.

I didn't want to add more to your plate, but you might want to know about an error that pops up every now and then during our tests.

http://pastebin.com/K4TJi6Sg

Thanks.