I've been working on this, and related permutations, for a few months. My thoughts on this (from a month ago) are at http://groups.google.com/group/clojure-tools/browse_thread/thread/f0ef25f5489b4554?pli=1
along with some commentary by others on related tools. Will try to get something sensible out this week. Would be happy to collaborate with others. On Mon, Mar 26, 2012 at 10:19 AM, David Nolen <dnolen.li...@gmail.com> wrote: > Martin, > > This sounds like a fantastic idea, and as Zack said very Mathematica like. > We have ClojureScript so building a very powerful cross-platform graphical > environment is very much in reach. It also seems that WebKit can integrate > easily with Java applications? > > While building a simple Bret Victor style editor is interesting and neat - I > think a rich extensible, graphical, interactive REPL a-la Mathematica that's > easy to integrate into existing projects would be a real asset to the > community. > > David > > > On Thu, Mar 22, 2012 at 6:23 AM, Martin Forsgren <martin.forsg...@gmail.com> > wrote: >> >> Hello! >> I am thinking of applying to GSoC and I found the proposal to continue >> working on Chris Grangers Clojure(script)-editor in "Bret Victor- >> style" really interesting. >> >> I have some ideas on features that I think would be nice to have, >> other than opening, saving and compiling files: >> >> Visualization of functions à la Bret Victor (Let the user give example >> input, then print the values of all local vars (and maybe return >> values of function calls) at the side of the function). Using >> clojure.tools.trace or CDT perhaps? >> Possibility to add the example input and the corresponding expected >> output as an unit test for the function. >> >> Pluggable ui-widgets (like the slider and colorpicker in Brets talk). >> Examples: slider, checkbox, colorpicker, filechooser, datepicker, >> mouse movement recorder, piano?, whatever. >> (predicate dispatch to determine what widget to choose? :) >> >> Pluggable widgets for visualising data(structures) could also be >> created.(Perhaps inline widgets? Although I think that most often >> would be more annoying than helpful.) >> >> Use kibit to highlight code that could be rewritten. >> >> Visualising the call-stack (as Chris suggested) >> >> Graphs of relations between namespaces. >> >> What do you think? Do you have other ideas? What features do you think >> one should focus on first ? Please give some feedback. >> >> -- >> 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 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 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
