Does the removal of JavaFX (or movement into a sta...

# tornadofx

[jo]

Does the removal of JavaFX (or movement into a standalone install) mean that AWT and Swing are getting moved, too?

[jo]

Not really TornadoFX specific, but I figured this group would be well in the know about JFX and GUI matters

[edvin]

According to Oracle: Swing and AWT will continue to be supported on Java SE 8 through at least March 2025 and on Java SE 11 (18.9 LTS) through at least September 2026.

[edvin]

What happens in JDK12 I'm not sure

[jo]

Is there an end date on JavaFX?

[jo]

Perhaps I'm thinking too far ahead. If anything I do is still relevant in 8 years I'll count my fortunes.

[jo]

Thank you.

[Ruckus]

What do you mean by "end date on JavaFX"?

[jo]

@Ruckus Was just curious if there was also a deprecation date on JavaFX like there is on Swing/AWT. Right now I'm using Swift, but I'm hitting some cases where I need to use AWT still.

[Ruckus]

There are no plans to deprecate JavaFX, and it wouldn't exactly be up to Oracle to do so now that it's a community project.

[carlw]

I think joeseph means the date javafx is removed from the JDK district. 11 is the first version that will not have javafx. Remember that even when oracle was working and promoting javafx, it was a separate download. It was only added in JDK 8.

[edvin]

Adding JavaFX to the JDK was a huge mistake IMO. It has resulted in less innovation and slower pace of new features. Decoupling is the best result for us 🙂

[carlw]

At the time, I think it was ok. I had to juggle a product that supported both JavaFX 2.2 (Java 6 + 7) and JavaFX 8 (Java 8 ). It was convenient having everything packaged together without build references to jfxrt.jar or including different classpaths for different Javas. Now, with modules, being able to control what goes into your app, separate is better.

[jo]

I'd forgotten JFX started as a separate feature.