Eclipse Community Forums: Eclipse Platform » IProgressService vs Jobs API

Help

Home

Home » Eclipse Projects » Eclipse Platform » IProgressService vs Jobs API

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

IProgressService vs Jobs API [message #890002]

Wed, 20 June 2012 14:24

Jan Krakora

Messages: 477
Registered: December 2009
Location: Prague

Senior Member

Hi,

could someone explain me what is the best way to run long running tasks?

There are few options:

the IProgressService with its:
- busyCursorWhile(IRunnableWithProgress runnable)
- run(boolean fork, boolean cancelable, IRunnableWithProgress runnable)
- showInDialog(Shell shell, Job job)
the IWorkbenchWindow.run(boolean fork, boolean cancelable, IRunnableWithProgress runnable)
the Jobs API with its own progress UI

I'm little confused what to select.

Report message to a moderator

Re: IProgressService vs Jobs API [message #890202 is a reply to message #890002]

Thu, 21 June 2012 12:41

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

I'd use the Job API for any long running operations, unless you have a reason not to. See http://www.eclipse.org/articles/Article-Concurrency/jobs-api.html

The IProgressService is used as the progress provider for the Jobs framework, so Job progress is managed the same way as using progress for org.eclipse.ui.progress.IProgressService.run(boolean, boolean, IRunnableWithProgress).

PW

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator