John Resig (of jQuery fame) has ported the Serving visualization language to JavaScript.
The examples are singular, suss out them out (but check out the browser issues John talks about).
John has a little confession :
The first portion of the project was droping a line a parser to dynamically convert code written in the Serving language, to JavaScript. This demands a lot of gnarled veritable expressions manducating up the code, sprinkling it out in a format that the browser reads.
It acts “fairly good” (in that it’s able-bodied to deal anything that the processing.org web site throws at it) but I’m certain its full scope is restrained (until a right parser is postulated). I found big about tackling this applying even expressions until I felt out that the original Working on code base did it in the same manner (they at present utilize a existent parser, course).
In reality that’s quite nerveless in itself (yet if angels weep at this parsing code, I reckon we on LtU shouldn’t redacted the first stone). DSLs should be easy built up and played with. Striping up the implementation follows later, if at all.
Purists may not only object to the unconstipated expression parsing, but likewise to the key line of code which attachs things unitedly, videlicet: eval(parse(code, p)). But and so, DSL lovers are not the sort of people to object to eval…
In the old days of LtU we on a regular basis staked links to chill little interpreters that people could play with. Some of the more diverting ones were javascript free-based, and the page checked a REPL form (Luke, I am talking to you!). It is a shame we don'’t post more stuff like this, in between the more highbrow discussions…
Relating Posts:
Linksys WAP11 + Radio == no work
Growing bitboards from possible moves into sound moves, pawn displaces, and conditional rules.
Presentations…
If the news is of import it will regain me
A web site is not an RSS feed…nor the reverse.
If the news is of import it will regain me