| Eclipse RCP [message #634781] |
Sat, 23 October 2010 09:57  |
Eclipse User |
|
|
|
Hi,
I am writing an application using Eclipse RCP. I am trying to avoid running running all my processing from the main UI thread as it "freezes" the GUI.
Therefore, I was wondering if its best to make use of the Jobs API rather than creating seperate threads for long running tasks ?
I have prototyoed using the Jobs api and I have to say its very easy to use.
Now Im just wondering whats the best approach for me to take (threads or jobs ) ?
Thanks for your time,
Jack.
|
|
|
| Re: Eclipse RCP [message #634914 is a reply to message #634781] |
Mon, 25 October 2010 02:49  |
| Eclipse User |
|
|
|
On 23.10.2010 15:57, Jack Higgins wrote:
> Hi,
>
> I am writing an application using Eclipse RCP. I am trying to avoid
> running running all my processing from the main UI thread as it
> "freezes" the GUI.
>
> Therefore, I was wondering if its best to make use of the Jobs API
> rather than creating seperate threads for long running tasks ?
>
> I have prototyoed using the Jobs api and I have to say its very easy to
> use.
> Now Im just wondering whats the best approach for me to take (threads or
> jobs ) ?
I think you should Jobs instead of Threads whenever you can. They
allow direct pooling via the Job manager and they are directly
integrated within the progress-reporting API of Eclipse RCP. You
will need to keep Threads, when your code is and should be independent
from Eclipse, though.
HTH & Greetings from Bremen,
Daniel Krügler
|
|
|
Powered by
FUDForum. Page generated in 0.12497 seconds
Home