This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
You can also create your own javafx Swing classes by either wrapping the JComponent using
the javafx.ext.swing.SwingComponent.wrap() function as in:
var myComponent = SwingComponent.wrap(myJComponent);
Another way is to have your JavaFX class extend SwingComponent and implement
the abstract funciton, protected abstract createJComponent() : javax.swing.JComponent.
Personally, I try to shy away from the Swing classes and use the javafx.scene.control classes. That way my application
can run on all three platforms.
Joined: Jun 15, 2009
JavaFX is single threaded similar to Swing and you can only update JavaFX objects
on the main JavaFX thread. In the JavaFX language there is no support for creating
threads or doing synchronization semantics.
Usually, the only reason you have to get on to the main JavaFX thread is you
have java code that is running in its own thread and you need to communicate
back to the JavaFX environment.
From java, there is a class:
If you want to do something like the Swing invokeLater call from JavaFX,
there is a function in javafx.lang.FX called deferAction. It works like this:
If you want to do an asynchronous task you need to use the javafx.async classes. I have done a write up
on this at my blog: http://blogs.sun.com/clarkeman/