I think you would probably have the most meaningful success if you focused on making things that let people teach themselves Clojurescript. Making the editor intuitive for beginners would be a major win. Allowing them to visualize data structures and algorithms that they have written in Clojurescript would be excellent. Look into maybe incorporating http://keminglabs.com/c2/ or just start up d3.
The ideal for beginners you would be working towards: http://reference.wolfram.com/mathematica/guide/Mathematica.html This is the best documentation I have ever seen. I taught myself not just Mathematica but vast swaths of math and statistics with this.* If you can make a set of examples that people can open up in their editor and evaluate and change right there in the browser, Clojurescript would win the internet. In fact, if you don't apply to GSoC with this idea, I will. -Zack *Full disclosure: I've been employed by Wolfram previously. Total fan boy here. On Thursday, March 22, 2012 8:23:53 AM UTC-2, Martin Forsgren 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
