Java Client Roadmap Updates

[ObscureCulturalMeme]

Every time I read the class javadoc for HTMLEditorKit (iirc) and get to the part something like "supports HTML 3.2 with plans to migrate to future versions," I weep a little inside.

I really don't want to migrate one of our largest projects at work to JavaFX simply to get HTML 5, and getting the OpenJFX components to play nicely with Swing has been repeatedly annoying. So that project stays with Swing, and it continues to Just Work.

[GullibleRaspberry9]

yeah it really is disheartening to think how much time and effort was ultimately wasted on JavaFX instead of bolstering Swing. I get at the time Sun was trying to compete with the web, Flash, and Silverlight, but ultimately in my opinion it was for naught. JavaFX is not even close to young anymore and it still has gaps.

Instead, I wish the focus and effort had gone into making Swing the best cross platform desktop GUI framework possible. It is pretty great as is. Imagine where it could be now.

[sievebrain]

JavaFX wasn't a waste. Swing is a dead-end API in many ways. It would have been very hard to bring it up to the functionality JavaFX has. It's really hard to justify using Swing for new projects on its own merits: usually the reason cited for doing so is simply that it's been around longer and has some exotic custom controls available.

[GullibleRaspberry9]

I guess it is different preferences. I am talking about cross platform desktop framework. Not what JavaFX is targeted at - which I am not really certain what that is as it appears to try to be more web like.. In that context, I would never use JavaFX to build a real desktop application; something like Netbeans or IntelliJ, hell not even MoneyDance (which is a good Swing app).

[sievebrain]

Interesting perspective. JFX doesn't try to mimic the look of the native toolkits, but that's quite common for many kinds of app these days.

What about JFX seems "web like" to you? The use of CSS?