[Bug 459926] New: Review Request: swing-worker - Long running Swing GUI interacting tasks
bugzilla at redhat.com
bugzilla at redhat.com
Sun Aug 24 16:00:04 UTC 2008
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Review Request: swing-worker - Long running Swing GUI interacting tasks
https://bugzilla.redhat.com/show_bug.cgi?id=459926
Summary: Review Request: swing-worker - Long running Swing GUI
interacting tasks
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: Package Review
AssignedTo: nobody at fedoraproject.org
ReportedBy: cassmodiah at fedoraproject.org
QAContact: extras-qa at fedoraproject.org
CC: notting at redhat.com, fedora-package-review at redhat.com
Estimated Hours: 0.0
Classification: Fedora
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
Description:
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.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the package-review
mailing list