Let the best decider of a GUI toolkit be based on pragmatism and design philosophy.
To that end Swing wins. Clojure runs on JVM and takes advantage of anything Java that it does not provide for in a Lispy way. Swing is just another one of those things automatically there, which can have a nice layer to make it more useful, interesting. Clojure does not include any extra libraries, except ASM, to operate. Won't need any extra ones by using a Swing-based layer. Clojure is completely cross-platform with supported OS for Java. A Swing layer will be also. Clojure can already create simple GUIs with Swing in a few lines of code. It can only get better with a dedicated layer. Swing is already a good selling point for Clojure. It actually is promoting Clojure to have read Swing support intrinsically. You cannot say these things about any other toolkit at this time. I am willing to do some work on the Swing layer, if it is wanted. If others want to work on SWT, Tk, etc. they can do that. That's what it comes down to, where the effort is put. I will step up to put some of mine behind the Swing-based one, anybody else? Voting and debating points are okay, but results are better. Swing is already a result, a layer is just furthering 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
