By bonlebon
via javaboutique.internet.com
Published: Apr 23 2007 / 04:01
Poorly-written Swing applications can appear to freeze when time-consuming code is executing. These applications frequently fail to provide their users with feedback on the code's execution state. In the worst case, end users will wonder if the application is working correctly.
-
Internet Explorer 9: CSS3 Support
-
Custom LoginModule in Tomcat
-
Write Your First Google Wave Robot in Java
-
Static Groovy and concurrency: type inference in action
-
How to handle Memory Leaks in Java/J2EE Applications ?
-
Illegal Argument interview with Reinier Zwitserloot and Roel Spilker from Project Lombok
Comments
Rob Lang replied ago:
SwingWorker is cool but hardly new. I used it in 2002 for my PhD software. I think this article should also be listed as Multithreading because that's what SwingWorker does in standard Comp Sci language.
caa replied ago:
Guess you didn't read the article, because it talks about the rewritten javax.swing.SwingWorker that was introduced in Java SE6.
Voters For This Link (15)
Voters Against This Link (0)