| Summary: | The presentation layer of Swing-based applications mainly consists of event-handling logic, layout properties, and graphical user interface (GUI) components. While such code should be easy to program because of the Swing programming model's single-threaded nature, more complicated concurrent constructs such as SwingWorker are often needed to perform time-consuming tasks while preserving screen liveliness. In this article, Yexin Chen discusses some negative consequences caused by SwingWorker usage and illustrates how to customize SwingWorker to achieve additional architectural design goals. (2,900 words; June 6, 2003)
|
