@viebel how would I get (doc map) to work in klipse? I have tried (clojure.repl/doc map) and (cljs.repl/doc map) but I get "Type Error - undefined" error messages.

doc is not yet supported in klipse

but you can workaround it with (:doc (meta #‘map)) See an example here: http://app.klipse.tech/?cljs_in=(%3Adoc%20(meta%20%23%27map))%0A&eval_only=1

@jr0cket ⬆️

Thanks. Hmm, that not something I would like to put in front of Clojure beginners though. For ClojureBridge content I'll just add a link the online docs at http://clojuredoc.org for specific functions, rather than in klipse for now. Its probably better they get used to looking at http://clojuredocs.org website as it has other examples too...

yep!

here

Your work looks wonderful!

thanks!

I gave it a try and basically, one can do a funny thing - run cljs_live inside klipse

Like this http://app.klipse.tech/?cljs_in=(require%20%27%5Bcljs-live.compiler%20%3Aas%20c%5D)%0A%0A%0A(println%20%22eval-str%3A%22%20(c%2Feval-str%20%22(map%20inc%20%5B1%202%203%5D)%22))%0A%0A(println%20%22eval%3A%22%20(c%2Feval%20%27(map%20inc%20%5B1%202%203%5D)))&external-libs=%5Bhttps%3A%2F%2Fraw.githubusercontent.com%2Fmhuebert%2Fcljs-live%2Fmaster%2Fsrc%2F%5D

(sorry for the long url)

hah, neat. so the external-libs option takes any src directory

yeap! not compiled

is there a way to automagically dig into clojars directories?

that would be great

but not for the moment

usually, I take code from github

The problem is that with the deps of the libs

For the moment, you have to add them manually into the external-libs parameter

Theoretically, I could read the project.clj and resolve deps

but I would need the repo of each dep - and it is not part of the project.clj

but maybe one could check in clojars what is the repo of the dep and solve all the deps

makes sense?

@mhuebert ⬆️

Sorry, my internet cut out

Hmm. It would be nice if there was just a mirror of the files in the jar, then versioning would be aligned

We just need the git commit of release tag!

I have to run to dinner now but let's chat more later

sure

I think you opened a lot of interesting doors with cljs-live

a mirror is also useful because there’s so much work that can be cached. like compilation. it’s really slow making the browser compile everything from source

of course it depends on use-case how important that is.

what do u mean by a mirror?

at first I just meant another server that would host a cljs-subset of Clojars, where the jars are expanded (since a jar is just a bunch of files compressed together), to use like you are using git.

but then in addition to just mirroring jarfiles as raw source directories, there is lots to do to make it convenient for grabbing clojurescript-compiler-friendly bundles of dependencies.

in one swift move you could pass the client everything they need to compile whatever namespace they requested. then, like in cljs-live.compiler, this stuff is put into a client-side cache so the load-fn doesn’t have to make any more http requests.

ok im signing out, speak later!