I still don't really see why a multi-threaded UI framework is important. You can have a multiple threads use Swing's invokeLater(Runnable r) api to submit UI work. And since Clojure fns implement Runnable, you can just post fns into Swing to do your UI updates. I don't think you even *want* a multi-threaded UI framework considering the threading bugs and performance problems it probably has (inherent to implementing complex concurrency with old school locking semantics).
On Fri, Oct 10, 2008 at 3:20 PM, Ande Turner <[EMAIL PROTECTED]> wrote: > Apologies Colin... I'll just say I was a victim of Trolltech marketing, > that wasn't the impression I got. > > 2008/10/11 Colin Walters <[EMAIL PROTECTED]> >> >> On Oct 10, 4:42 pm, "Ande Turner" <[EMAIL PROTECTED]> wrote: >> > David, >> > Thank you very much for such an expansive response. Currently a >> > thread-safe >> > Swing alternative is using the Jambi bindings for Qt. I neglected to >> > provide >> >> Hmm? Qt isn't really any more threadsafe than Swing is, or than GTK+ >> is: >> >> http://doc.trolltech.com/4.0/threads.html : >> "Although QObject is reentrant, the GUI classes, notably QWidget and >> all its subclasses, are not reentrant. They can only be used from the >> main thread." >> >> GUI programs by their very nature have a large amount of state, and >> the object-oriented paradigm makes a lot of sense. So back to the >> original question - probably what makes the most sense with Clojure is >> to write nontrivial GUI components in Java, and the interact with your >> GUI code via Clojure's Java integration. >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
