| Name : swing-worker
| |
| Version : 20050620
| Vendor : (none)
|
| Release : 0.oc2pus.1
| Date : 2006-01-17 17:23:20
|
| Group : Development/Libraries/Java
| Source RPM : swing-worker-20050620-0.oc2pus.1.src.rpm
|
| Size : 0.04 MB
| |
| Packager : oc2pus < oc2pus_arcor_de>
| |
| Summary : SwingWorker enables proper use of Event Dispatch Thread in Swing-classes
|
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.
The original SwingWorker version was published back in 1998 by Hans Muller
and Kathy Walrath. Since that time a number of modified SwingWorkers were
published. The last version we are aware of was published by Joseph Bowbeer.
Swing team got a number of request to include SwingWorker into the swing
package. In jdk1.6 javax.swing.SwingWorker was introduced.
|
RPM found in directory: /packages/linux-pbone/ftp.gwdg.de/pub/linux/misc/suser-oc2pus/suse100 |
