Community
Participate
Working Groups
We should think about adding support for JavaFX wrapper components from "javafx.embed.*" for embedding of / in other UI toolkits.
There are multiple ways of - embedding JavaFX and its controls in other toolkits - SWT: FXCanvas [1] - Swing: JFXPanel [2] - and (vice versa) embedding Swing toolkit controls in JavaFX via: SwingNode [3] [1] http://docs.oracle.com/javase/8/javafx/api/javafx/embed/swt/FXCanvas.html [2] http://docs.oracle.com/javase/8/javafx/api/javafx/embed/swing/JFXPanel.html [3] http://docs.oracle.com/javase/8/javafx/api/javafx/embed/swing/SwingNode.html
It'd be good to know which of these toolkit wrapper components are commonly used to plan for support in upcoming versions of Jubula.
From one of the internal projects here that I asked, they don't use any of these. They use JavaFX with an e4 renderer.
Most common used method would be JFXPanel since the tendency is high swing projects moving to javafx by converting part of the views to javafx. This is common in large enterprise client GUIs when the whole project cannot be converted at once.
(In reply to Gayan Perera from comment #4) > Most common used method would be JFXPanel since the tendency is high swing > projects moving to javafx by converting part of the views to javafx. This is > common in large enterprise client GUIs when the whole project cannot be > converted at once. Thanks for letting us know! I've filed separate enhancements (with a dependency to this one) for each of the embeddable / embedding scenarios as each one is a bigger task / enhancement on its own. Please feel free to comment and vote on these individual bugs as well.