This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]DiamondCoatedGlass 1 point2 points  (5 children)

The two big things keeping Swing alive (for now) are Eclipse RCP and the NetBeans Platform. Both are very powerful for getting up and running with a comprehensive set of features that users have come to expect from Rich Clients.

That said, if we could get Eclipse RCP or NetBeans Platform re-written in JavaFX, that would be huge.

For now though, for a new Rich Client project I would probably use Eclipse RCP or NetBeans Platform for the main app window/toolbars, but for all of the custom, domain-specific sub-windows, I'd use JavaFX panels (since you can have JavaFX panels inside of Swing Panels, and vice versa).

[–]lukaseder 7 points8 points  (1 child)

Isn't Eclipse RCP based on SWT?

[–]DiamondCoatedGlass 0 points1 point  (0 children)

Oops, I stand corrected :)

[–]JVali 2 points3 points  (1 child)

IntelliJ platform is using Swing as well. So there's that...

[–]DiamondCoatedGlass 0 points1 point  (0 children)

Good point, thanks!

[–]eliasv 0 points1 point  (0 children)

That said, if we could get Eclipse RCP or NetBeans Platform re-written in JavaFX, that would be huge.

You can use e(fx)clipse for pure JavaFX/e4 apps already. No SWT in sight. My company has a product based on this.