sandover
commented
11 years ago +1.
Just FYI, Joel, I now have a rough prototype working which uses your project to help make a Clojurescript language binding for the Greenhouse C++ SDK http://greenhouse.oblong.com. I'm one of the leads of that SDK project; it's intended for creating gestural and spatial interfaces, multi-machine applications, art installations, and other creative uses. As we've recently created a Javascript language binding for it, I've wanted to layer Clojurescript on top, and cljs-in-cljs provides the ideal way to do that. (Optimized and minified JS is not, for my purposes, as important as keeping things simple, straightforward, and pure JS.) So I'm rooting for the continuation of the project.
I'm feel I'm not deeply yet familiar enough with the intersection of Clojure, Java, Closure, and Javascript to make valuable patches, but if I'm wrong and there are simple (or merely localized) tasks I could in fact do to be useful here, let me know.
Brandon
The code base was forked from upstream ClojureScript several months ago and has not been merged with it since then.
One of the big features that is being added to upstream ClojureScript is source maps which would be a big benefit to cljs-in-cljs too.
Note that compiler.cljs and analyzer.cljs were copied from compile.clj and analyzer.clj so in addition to merging the .clj versions, the changes will need to also be ported to the .cljs versions of those files.