Matt Pavlovich wrote:a multi-threaded environment such as this project
My client is not multi-threaded, my server is. If I would perform a major time-consuming task and I want not to freeze my GUI I would use the SwingUtilities.invokeLater(), but in this project I don't see any advantages.
Roel De Nijs wrote:If I would perform a major time-consuming task and I want not to freeze my GUI I would use the SwingUtilities.invokeLater()
They invented SwingWorker for that . If you use invokeLater() for time consuming tasks, the GUI would freeze anyway.
It's true you'll probably won't absolutely need to use invokeLater() to construct your GUI, but as I understand it, it is a good practice to do so anyway. The Swing documentation does not say you should only use invokeLater() in a multi-threaded application, it just says you should use it when constructing your GUI (http://download.oracle.com/javase/6/docs/api/javax/swing/package-summary.html).
But you must do what you feel is right, of course...