The library has been deprecated, no longer supported for newer versions of java?

[HenriqueVS600]

I would like to see it updated because it is the best javafx library

[louhy]

Considering that I use parts of it right now within Java 17 I would not agree with that statement. However you will need to mess around with JVM parameters. There are some issues in this GitHub which talk about problems people have had, and some proposed solutions.

For example I need these in my case.

--add-exports=javafx.controls/com.sun.javafx.scene.control.behavior=ALL-UNNAMED
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED
--add-exports=javafx.base/com.sun.javafx.binding=ALL-UNNAMED
--add-exports=javafx.graphics/com.sun.javafx.stage=ALL-UNNAMED
--add-exports=javafx.base/com.sun.javafx.event=ALL-UNNAMED
--add-exports=javafx.controls/com.sun.javafx.scene.control=ALL-UNNAMED

But it'll vary depending on your needs, you need to examine the errors carefully.

Basically "Jigsaw" (Java 9+ Module System) and other later changes destroyed the simplicity of using JavaFX that we had with Java 8 and before, so now we need to jump through a ton of hoops, because [reasons].

[ctoabidmaqbool]

org.burningwave.core.assembler.StaticComponentContainer.Modules.exportAllToAll();

One can totally disable module system in java. Hence jFoenix will works as expected. With module system there are couple of issues exists which takes time and efforts to fix it!

[SkrrtNick]

I would like to see it updated because it is the best javafx library

It'd be great if it could updated for reliability - reverting to an older version of scenebuilder isn't ideal after all