Bug 459926 - Review Request: swing-worker - Long running Swing GUI interacting tasks
Review Request: swing-worker - Long running Swing GUI interacting tasks
Product: Fedora
Classification: Fedora
Component: Package Review (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-08-24 12:00 EDT by Simon
Modified: 2008-10-12 11:35 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-12 11:35:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Simon 2008-08-24 12:00:02 EDT
Spec URL: http://cassmodiah.fedorapeople.org/swing-worker-1.2-1/swing-worker.spec
SRPM URL: http://cassmodiah.fedorapeople.org/swing-worker-1.2-1/swing-worker-1.2-1.fc9.src.rpm
When writing a multi-threaded application using Swing, 
there are two constraints to keep in mind: 
(refer to  How to Use Threads  for more details):

* Time-consuming tasks should not be run on the Event Dispatch Thread. 
  Otherwise the application becomes unresponsive.
* Swing components should be accessed on the Event Dispatch Thread only.

These constraints mean that a GUI application with time intensive computing 
needs at least two threads: 
1) a thread to perform the lengthy task and 
2) the Event Dispatch Thread (EDT) for all GUI-related activities. 
This involves inter-thread communication which can be tricky to implement.

SwingWorker is designed for situations where you need to have a long 
running task run in a background thread and provide updates to 
the UI either when done, or while processing.

This project is a backport of SwingWorker included into 1.6.

Note You need to log in before you can comment on or make changes to this bug.