The Wescheme environment is meant to pair with the curriculum of the Bootstrap project (http://www.bootstrapworld.org/)
Here are some examples that highlight the features in WeScheme. Each includes both a runner and a live editor link to the source code.
A simple game:
http://www.wescheme.org/view?publicId=messy-humor-truck-adopt-outdo
A sierpenski triangle program: http://www.wescheme.org/view?publicId=pasty-brawl-frank-vomit-would
A more substantial demo of the image libraries: http://www.wescheme.org/view?publicId=haste-foggy-grief-hatch-gloom
A simple 1-tick-per-section counter that resets when you press the button: http://www.wescheme.org/view?publicId=queer-decay-slush-speck-stage
I'm in the middle of a rewrite of the underlying evaluator and libraries during this summer (http://hashcollision.org/whalesong), and hope to deliver in the next few weeks so that people can play with it.This lets me do scheme->js in the browser using moby, which is implemented in racket. So my code gets converted to js on the server hosting this site. Does this mean I can (require ...) other racket libraries as well?
Bookmarked for later.
moby documentation: http://planet.racket-lang.org/package-source/dyoo/moby.plt/3...
World: http://world.cs.brown.edu/1/htdw-v1.pdf
I'm playing now. Will post some code when I have it working.
You can read about the model here: http://www.cs.brown.edu/~sk/Publications/Papers/Published/ff... A fun exercise for hackers is to guess the consequences of this for running atop JavaScript.
Much of the credit goes to Danny Yoo for Moby -- http://github.com/dyoo
For someone who doesn't necessarily want to code scheme right away, log-in with their account, or put headphones in to watch a video - you've lost them immediately. Never to come back.
The option that is missing - let me read about it.
(js-big-bang 0 ;; initial world
(on-draw ;; the dom tree renderer
(lambda (w)
(list (js-p '(("id" "myPara")))
(list (js-text "hello world"))))
;; the css renderer
(lambda (w)
'(("myPara" ("font-size" "30"))))))http://steve-yegge.blogspot.com/2008/04/xemacs-is-dead-long-...
Truthfully, I don't know that it's going to kill conventional editor or editing habits (and by the time it does, I suspect that web-based IDEs will look significantly less like today's web-apps than they do today) and more that this technology will find a niche in code review, or version control interfaces, or something like that, but it's a nifty idea.