3 ms·
I wrote a parenscript wrapper for it. [edit] No time tonight to make it pretty and publish it, but here it is[1]. Usage is identical to my parenscriptx[2] (a
by aidenn0 11y ago
I wrote a parenscript wrapper for it.
[edit]
No time tonight to make it pretty and publish it, but here it is[1]. Usage is identical to my parenscriptx[2] (a React tool I wrote that I based this off of).
1: https://gist.github.com/jasom/4ab84354fda405a8f67a https://gist.github.com/jasom/4ab84354fda405a8f67a
2: https://github.com/jasom/parenscriptx https://github.com/jasom/parenscriptx
- qwertyuiop924 11y agoI was thinking more along the lines of lispyscript[1]. It's not as good as SPOCK[2], or clojurescript[3], but there's less overhead than clojurescript, and SPOCK is known to stretch your javascript implementation in odd ways. 1: http://lispyscript.com/ http://lispyscript.com/ 2: http://wiki.call-cc.org/eggref/4/spock http://wiki.call-cc.org/eggref/4/spock 3: https://github.com/clojure/clojurescript https://github.com/clojure/clojurescript
- aidenn0 11y agoparenscript is quite low overhead; it's approximately lispyscript with common-lisp macros instead of whatever lispyscript has (it looks like some kind of pattern-matching style; there's only one macro example on the lispyscript documentation and the link to an article about more details is dead). In any event if you know lispyscript you can probably translate my code; it took me only a couple of hours to write the initial react version, and another 45 minutes or so to translate to mithril.