One thing I think that's needed with JavaFX is integrations with DI frameworks! I started a project called DiFx that does exactly that: https://github.com/exabrial/DiFx
This makes state and shared data management in JavaFX much nicer, as you offload those concerns to a container. CDI also provides extensive capabilities with portable extensions and scope management, as well as a sync and async eventing framework.
The problem is that I don't have a "real life" project to try this out on, so development kinda slumped off.
Thanks for writing this up! It still assumes a lot of prior knowledge, but it's a good starting point to approaching these problems. How JavaFX works on different platforms really looks like dark magic from the outside. I wrote an app in Clojure using cljfx. I can jpackage it and run it Linux/Windows/macOS .. it's quite easy to get working. But once you step outside of the standard platforms it gets complicated really fast. Trying to get it to Android or a native build and suddenly you have to be an expert in several build systems and JVM internals.
Apparently JavaFX didnt die as we all thought back when Oracle spit it out of the JDK, they will happily offer support for it now, but who wants to be in bed with Oracle.
That looks really sleek. One thing JavaFX got right was CSS support.
I don't think this is an accurate assessment. Oracle has its flaws and closet full of dead bodies/skeletons, but they've been good stewards of the JDK and JavaFX overall. Gluon and Oracle have done tremendous amount of work with JavaFX.
Splitting it off the JDK was definitely the correct call. It's a Desktop UI framework, it should not be bound to JDK releases.
Oh hmm, I'm honestly not super sure then. I know Gluon is the one that's seemingly has a business providing JavaFX support, while Oracle.. as far as I know doesn't offer a license or anything services in that direction? But I could be wrong. Gluon is mentioned in the article.. they have a very Qt-style confusing licensing situation where it's probably all free.. but you're never quite sure :)
The whole space is a lot more icky than one would like it to be.. Which is unfortunate b/c while it doesn't have a billion features, it's a nice composable reactive framework to use (at least from cljfx/clojure)
This makes state and shared data management in JavaFX much nicer, as you offload those concerns to a container. CDI also provides extensive capabilities with portable extensions and scope management, as well as a sync and async eventing framework.
The problem is that I don't have a "real life" project to try this out on, so development kinda slumped off.
That looks really sleek. One thing JavaFX got right was CSS support.
Splitting it off the JDK was definitely the correct call. It's a Desktop UI framework, it should not be bound to JDK releases.
https://insights.linuxfoundation.org/project/openjdk-jdk/con...
The whole space is a lot more icky than one would like it to be.. Which is unfortunate b/c while it doesn't have a billion features, it's a nice composable reactive framework to use (at least from cljfx/clojure)