Currently v11.17 pulls JavaFX 16 from maven repo.
Now that JavaFX 17 (OpenJFX 17) is out, it has quite a bit of fixes and has a newer webkit version. See 1 and 2.
Are there any roadblock in simply adopting JavaFX 17 (to be used with Java 11) ahead of time ? without having to sort out all those potential issues when transitioning from Java 11 to Java 17, which would be more time consuming.
btw, I use Eclipse and Maven as my platform for development and not Gradle. If I roll in JavaFX 17 as a maven artifact at the same time while using FXGL 11.17, Eclipse would complain as having two conflicting libraries and flag it as a problem and I would be unable to import either version of JavaFX (16 or 17) at all. So I can't make Eclipse to choose Java 17.
Even if I do, I suspect FXGL 11.17's intricate reliance on JavaFX 16 would probably break. I don't know how backward compatible JavaFX 17 is.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4
