You might get a more accurate or precise answer from the seesaw-clj group. In indirect & partial answer to one-third of your questions: As I recall, in Swing, just about every bit of intense or blocking work (even reading files) belongs on a background thread. You can make and manage the background thread or threads in any way you like. There is a SwingWorker, but you're not limited to it. The key thing is that the background threads should not touch Swing, except via SwingUtilities.invokeLater. As for the foreground, Swing won't know which parts to disable, so there is no shortcut for that. Another option is to put up a modal progress dialog, as long as people can Cancel it (which, in Java, might be unable to kill the background thread, but could at least cut it loose) in case the fuse blows and the lights go out right after they press your XSLT button and they do not want to spend battery power on it.
-- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
