gouessej wrote
Coding against a private API subject to changes would be a waste of time and actually, there isn't an high demand of interoperability with JavaFX/OpenJFX yet.
It's easy to see why, it has such
potential though, but people have been saying that since before 2010 :))
gouessej wrote
JOGL was used by default in the past in LibGDX several years ago. A few L**** seemed to lead a FUD campaign against JOGL just after Oracle abandoned it, they claimed that JOGL was dead and it was used by a lot of developers to stop supporting it in their frameworks. However, some corporations came back and the great commitment of several people in our community has helped a lot to show that JogAmp is solid.
I did come across some that when I went to familiarize myself with the history. Glad that it's quieted down now. On a side note, I also read a post you contributed to in LibGDX. I think they said that be willing to put Jogamp on the same exposure level as the other backend, if contributions keep in pace with their releases, along with documentation. However, I know that your focus for Jogamp goes beyond the gaming applications, but I think that may be the reason why the other backend saw more exposure. Reading up on Jogamp, it's being used on numerous fields, if one looks up the other binding project, it's almost exclusively used in gaming, and these associations stuck.
gouessej wrote
You'll have to provide the native libraries :s
Yeah, confirmed it by looking at the verbose output for Prism. I'm about to start creating that jfxrt.jar specified in Aqd's instructions.
gouessej wrote
Try using the option that forces JavaFX/OpenJFX and Swing to use the same event dispatch thread. Set it very early when running your application, pass it to the JVM.
I tried that early on, but it had an undesired effect. FrameBuffer objects (I'm not sure if all) aren't displayed at all, e.g. Box2dLights objects don't show. I'm not sure if its related, but in the Spasi project, he had to put in a means to defer rendering, for things to sync up (he did it after Aqd forked for a Jogl attempt).
gouessej wrote
By the way, I'm fixing the class cast exception you mentioned and the rest...
Thanks :) I'm trying to get my current checkout of your LibGDX fork to work in my environment. For some reason, the Jogamp backend along with its tests, does not have the reference to the GDX project, everything else seems to be in order. I'll keep trying.
Edit 1:
Got ES2 to work, but, apparently, something must have changed since the last update of Aqd's project. There was an additional step (or 2) I had to make in order to get it running.
I couldn't work on Jogamp tests issue, I resolved the workspace errors by updating your fork to the latest Gdx snapshot, but the backend itself is now missing; I'm guessing since you're working on it? Unfortunately, the updating also took off the source files I was using, so I'll just wait till you're done, so I can test it with ES2.