Whatever you chose, you probably ought to show its source with an IDE (whichever you chose: NetBeans. Eclipse, IntelliJ) but should probably forget about emacs: many (most?) Java developers won't even consider anything that isn't at least partially integrated within some IDE.
Not sure how much work is involved with the existing inspector, but showing how you can impose another hierarchy via multimethods on top of the existing JComponent subclasses (JTree & JTable) and assorted models was really something that blew me away. Also, adding DnD support to that inspector window such that you could drag and drop some moderately complex XML file, and show it leaves appear as maps (within maps)* in the JTree would also be really cool. My 2p :) --~--~---------~--~----~------------~-------~--~----~ 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 clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
