Eclipse Community Forums: e(fx)clipse » Executing background tasks

Home » Eclipse Projects » e(fx)clipse » Executing background tasks(Use javafx.concurrent.Servce or jface.operation.IRunnableWithProgress)

Show: Today's Messages :: Show Polls :: Message Navigator

Executing background tasks [message #1772702]

Thu, 14 September 2017 07:01

Alexander Kerner

Messages: 25
Registered: January 2015

Junior Member

Hi,

what is the recommended way to do some tasks in the background? Do it the 'SWT way'

final ProgressMonitorDialog monitor = new ProgressMonitorDialog(UtilSWT.getShell());
monitor.run(true, true, runnable);

Or the FX way?

new javafx.concurrent.Service(){[..]}.start()

Probably both should work? Are there any pitfalls I should be aware of?

E.g., does it make a difference if the Service/ ProgressMonitorDialog will update an FX component or an SWT component once done?

Report message to a moderator

Re: Executing background tasks [message #1772761 is a reply to message #1772702]

Thu, 14 September 2017 21:43

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

1. First of all I think you are embedding JavaFX into an SWT-UI, right? I would stick with the SWT/Platform way.
2. You can call JavaFX from the SWT-Display-Thread and SWT from the JavaFX-Event-Thread because they are the same!

Report message to a moderator

Re: Executing background tasks [message #1772765 is a reply to message #1772761]

Thu, 14 September 2017 22:10

Alexander Kerner

Messages: 25
Registered: January 2015

Junior Member

Yes, embedded FX UI..
I thought, since I am anyways working mainly with FX UI elements, I could be more consequent and do this kind of stuff the FX way as well. I will give it a try, thanks a lot!

Report message to a moderator

Re: Executing background tasks [message #1772778 is a reply to message #1772765]

Fri, 15 September 2017 07:02

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

well let me put it this way: You should not directly reference this stuff in FX but eg hide it behind a Service-API so that you don't introduce SWT-Dependencies into your own code.

Report message to a moderator

Previous Topic:	java.lang.NoClassDefFoundError only on Mac OS
Next Topic:	Headless testing with FX-Test

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Jan 14 06:18:27 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter