oracle decided to fuck us up once again, by implementing a good idea in a shitty way
Essentially the JFX integration currently works by emulating a swing context and abusing the abilities the JavaFXPanel has. Now with java9 we can no longer see&load the related classes because reasons. no the questions is what can be done?
I thought so far (but not tried)
Use openjfx selfcompiled as a basis
Make a swing to JME bridge, let JFX run in a JFXPanel
Stay with Java8 forever/ hope jigsaw dies
I personally like the idea of a swing to jme bridge. It will open up the use of swing within a JME application and still allow us to integrate our JFX code through a JFXPanel.
You launch jme context, javaFX context and swing context. Also, swing works on the layer of javaFX. It is horrible. You have a lot of overheads for this.
I agree the overhead is HUGE but this is the only way I can embed swing components into the JME application. I wish we had a JME to Swing bridge but we do not.
Nice, this did actually run under java9? without any classnotfounds (cause that were my main problems)?
How is the performance with all the reflection stuff compared to the one before? Noticeable worse, or around equal?
(Since I’m on a ingame ui trip currently, jfx is not that much use to it, but I still have ton’s of ui that I would like to keep, also alone the working webbrowser is a huge argument for javafx)
How is this in the terms of api compability with the former code? couls this be a dropin replacement, or is it necessary to rewrite some parts?