I'd vote for swing and against anything that abstracts away the toolkit so that you can switch the backend.
Implementing a clojure wrapper for the apache pivot toolkit gave me a little insight on at least two GUI toolkits, namely swing and pivot. Despite their goal of displaying widgets on a 2 dimensional plane, their APIs differ in a lot of ways, like different listener types, totally different approaches to layout. I'd say that it would hardly possible to find a common API without implementing substancial parts of, say, the layout engine yourself so that its results look equal on every backend. My main issue, besides the deployment hurdle with SWT, is that you have to manage graphics resources manually in SWT (see http://www.otug.org/groups/javasig/richclient.pdf). Like, say you would like to have built a form where you have a lazy seq of checkboxes for displaying the contents of a map. Also, with swing, you can add a small gui to whatever program you are going to ship, without bothering about the additional complexity induced by including a gui. Erik -- 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
