hi, i'm using Figwheel, my question is how using external library/JavaScript file in Figwheel? but i tried the key ':externs' but the repl/clojurescript not load the library, this is js file http://waveformjs.org/waveform.js and for create extern file, i used Extern Generators (http://jmmk.github.io/javascript-externs-generator/)

what is the fastest/easiest way to get a library like cljs-time running in a repl using node?

I don't need to watch/compile files

just a repl session, preferably using a script of just a few lines

I now have this in a script, which is already quite amazing: boot -d clj-time repl -e "(require '[clj-time.core :as t])", but I wonder if I can cut the startup time using node and clojurescript

promoted it into a SO question: http://stackoverflow.com/questions/38636492/repl-session-for-a-clojurescript-library-in-the-vein-of-lein-try

Probably Planck is what I need here

@borkdude: yeah, planck -c path-to-cljs-time.jar

@martinklepsch: trying to export the classpath with boot, see #C053K90BR 🙂

this works planck -c ~/.m2/repository/com/andrewmcveigh/cljs-time/0.4.0/cljs-time-0.4.0.jar

@borkdude: If you want to reduce startup time with Planck, add a -K, as in:

planck -Kc ~/.m2/repository/com/andrewmcveigh/cljs-time/0.4.0/cljs-time-0.4.0.jar -e "(require '[cljs-time.core :as t])" -e"(t/plus (t/today) (t/days 100))”

@martinklepsch: ah, that works indeed. I wonder why "planck -c boot -d com.andrewmcveigh/cljs-time:"0.4.0" show -c" doesn't work...

@borkdude See http://planck-repl.org/dependencies.html where an example using backticks is shown:

$ planck -c`boot show -c`

I used the backticks like this:

planck -c `boot -d com.andrewmcveigh/cljs-time:"0.4.0" show -c`

boot show -c has a bunch of boot stuff, not sure if that might mess with Planck

(You essentially want to run Boot, but if your goal is outright speed, see the caching portion on that page.) And @martinklepsch is right, minimizing the number of JARs on the classpath will result in Planck finding the deps faster.

Well, planck -c ~/.m2/repository/com/andrewmcveigh/cljs-time/0.4.0/cljs-time-0.4.0.jar -e "(require '[cljs-time.core :as t])" -r does exactly what I want, so thanks

@mfikes: an option akin to boot's --dependencies that expects jars in .m2 might be a nice affordability 🙂

(i.e. you pass coordinates instead of paths)

@martinklepsch: Yes, it is tempting to add that. (The key is to only expect the JARs to be there, without actually trying to download them, which is another whole project in and of itself.)

right, check if they exist otherwise throw an exception or something

so like planck -c com.andrewmcveigh.cljs-time and then just pick the newest?

well, more like planck -d com.andrewmcveighcljs-time:0.4.0 — picking newest might be unexpected because it can't download jars

yeah agreed

if cljs-time would have another dependency this wouldn't work right?

@martinklepsch: Added a ticket for it 🙂 https://github.com/mfikes/planck/issues/342

then going the boot show -c route and stripping out stuff would be the easiest?

@borkdude: there are alternative things for boot show -c around that just dump the jars of actual dependencies minus boot stuff

https://github.com/micha/boot-cp

@martinklepsch: I'm in awe.

This worked: boot -d org.clojars.micha/boot-cp -d com.andrewmcveigh/cljs-time:"0.4.0" with-cp -w --file .classpath

@mfikes: you might want to update the docs with this instead of the default boot show?

OK… will do

thanks!

@mfikes: don't know if the outputted clojure version is affecting planck

but for me it works as expected

@mfikes: if you update the docs, make sure you mention that the user then needs to pass the contents of the classpath file to the -c option @borkdude

I think I'll write short blog post about this. It's exciting 🙂

@borkdude: No. Planck will satisfy dependencies by first finding them in the Planck binary. So, you can’t inadvertently specify an alternative version of ClojureScript, for example. The only real danger would be in somehow obtaining a .clj macro dep from the Clojure JAR, but Planck should be taking care of that in the same way.

@martinklepsch: Yeah… it appears to be a good way of caching the classpath in one step. As opposed to using tee as is documented in this example:

if [ ! -f .classpath ]; then
  classpath=`lein classpath | tee .classpath`
else
  classpath=`cat .classpath`
fi

planck -c $classpath

@martinklepsch: can you explain how it's using caching when you're not writing it to a file?

@borkdude: uhm, I'm lost, can you elaborate?

@martinklepsch: well, calculating dependencies takes time, that is why it's being cached in the .classpath file

I’m guessing @borkdude that what might help is to point out there are two things that could be cached. (1) The result of building the classpath. (2) The results of compiling the dep.

@mfikes: how is (2) cached atm?

I'll try to push a boot update for the class path show -c bug today too

@micha as in make show -c only return the project classpath? (excl. any boot stuff)

By passing -K to planck, or, alternatively -k some/directory/to/write/cache. (`-K` creates and writes in .planck_cache)

@martinklepsch yep that one

@mfikes: thanks, was still using an older version of planck where -K didn't work. Now I tried it

Cool. Yeah, you should definitely see it speed up. And you should see a .planck_cache dir.

please check for errors 🙂

I'd suggest using expanded options for something educational

good point

Also just explaining what that boot invocation does might be good, looks kinda overwhelming if you don't know what's going on 🙂

> invocation I think the word "incantation" is more appropriate at this level 😉

well, if @micha is going to change show to what this does, it can be simplified

much better

about that with-cp -w: ¯\(ツ)/¯

I’ve created a ticket capturing stuff so I can go back in later and update the docs: https://github.com/mfikes/planck/issues/343

@dominicm: had too look that up but yeah, 😂

@mfikes: cool!

@mfikes: I found out that -K and --cache don't work nicely together, probably a warning would be good

I'm using this script now at the end of this gist: https://gist.github.com/borkdude/8d43941031518a0a85f9732c270b119a

@borkdude: Thanks: https://github.com/mfikes/planck/issues/344

@martinklepsch: done thanks

As I think this is cljs related more than om I ask here: after advanced compilation I'm not able to access value of text field by-id. I get Uncaught TypeError: Cannot read property 'Ub' of undefined, may add that these text-fields are generated in sequence, which I believe contributes to this issue. Any ideas for workaround?

@hlolli: the code might help, generally this seems like an externs issue

ok, but I must point out in the following code, it works in figwheel. And accessing text data in fn (since this is material-design text field), also works in figwheel dev-env.

ahh doesnt show the sequence, let me try again in a short cut version.

mapv #(material-ui/text-field :on-change 
(fn []
    (let [id (str "text-field-id-" %)
              input-text (str (.-value (gdom/getElement id)))
             valid? (tax-id-validator input-text)]
  ...etc....))
   (range (:text-field-count (om/get-state this)))

I'm getting an "undeclared Var" warning that seems to be coming from a macro. Is there a way to see the compiler's result after macroexpanding my code?

@peeja: There’s no direct way, but I’d try (macroexpand ‘(some-form))

I'm not clear where I can actually call that from…

Oh… try that in the REPL

Of course, you have to know which form is causing the problem

Shoot. I'm not actually sure how to get this code into a repl.

Ah, this is what I'm hitting: http://dev.clojure.org/jira/browse/CLJS-1607

It's an open Om bug.

So I’m new to clojure and functional programming in general. I feel like I’m creating a mess while attempting to manage state and I’m wondering if you folks have any suggestions for me. I’ll explain my situation in more detail...

I have a form, which has a message that displays information to the user depending on whether the form is valid, an error occurred during submission, submission succeeded etc

I’m using reagent, and I create a message atom when my component is initialized. In order to update the message I have to pass it through several layers of event handler functions

Is this “normal”? I feel like the number of arguments that my functions take is growing as the complexity of my app increases

so the atom gets passed to a submit function, and then the submit function passes that same atom to a handle-success function and so on

@danielpquinn: I'd recommend taking a look at re-frame

reagent alone doesn't really have a state management system

thanks, I’ve taken a brief look and do plan to use it in the future

I’m trying to get to grips with reagent first though

Does reframe have some convention for managing state at a component level? I feel like this becomes necessary when dealing with forms

vs the global state/redux way of doing things

yes, you have a centralized app-db that stores all of your state and you access it via subscriptions in your components where that state is needed

and modify it by dispatching actions that modify that state

So let’s say I have an input component which has a valid state. Does that state move into app-db?

without something like this, then yes you have to pass references to your state atoms to wherever they are needed

gotcha, thanks 🙂

yeah you'd define a section in the appdb to store it such as [:my-input :valid?]

and have a subscription that accesses it in the component that needs it

So I guess multiple instances of components gets tricky then

not sure if I’ll need to do that, just a thought

no

you can define something such as :form-path as a param if you want

and pass that in where you use an instance of a component with a unique path

Oh interesting, yeah that makes sense

thanks for your help

np

overall point tho is that reagent is pretty useless on its own, same with react

you need a flux/redux to accompany it basically

re-frame is a cljs analog to redux basically

okay nice, well sounds like I’ll be looking into re-frame sooner than I expected

@danielpquinn: I learned reagent through using re-frame and it really is a good way to start with it - I knew nothing about react or reagent and it was my first real project using clojure and clojurescript. If you go through the readme and the wiki (including the section on reagent) it should give you a really good start as well as a lot of good info on reagent. There is a #C073DKH9P channel on here as well that is very helpful for when you run into questions.

okay awesome, thanks for the tips

are there any downsides of re-frame subscriptions like

(register-sub
 :get
 (fn [db [_ key]]
   (reaction (getx @db key))))

?

@micha is there a ticket I can watch for this update? https://clojurians.slack.com/archives/clojurescript/p1469712478001202

@borkdude: i don't think there is an issue

if you would like to create one that would be awesome

otherwise i hope to have a patch release of boot which will notify in #C053K90BR here on slack and #boot_clj on IRC

@micha created it: https://github.com/boot-clj/boot/issues/485

I’m searching for a markdown parser, what do people use mostly?

I was looking at marked but it seems it hasn’t been maintained for 1 year

@anmonteiro: for cljs there is showdownjs

I was trying out showdown but I think it’s missing a feature I need

fenced code blocks with language don’t seem to be supported

oh

it is kind of robust I found

e.g.

‘’’clojure
(+ 1 2)
‘''

there is also markdown-clj IIRC

this gets rendered as

clojure (+ 1 2)

@richiardiandrea: that one seems promising, I wonder if it’ll be too much of a perf hit

we used showdownjs effectively, I don't remember that particular use case now, but you can have a look here: https://github.com/Lambda-X/cljs-repl-web/blob/devel/src/cljs/cljs_repl_web/markdown.cljs

it's clojurescript.io...I haven't used markdown-clj though

@anmonteiro: anymore I'd recommend MarkdownIt

it's actively maintained, easy to plugin, and provides access to the parser

...if you need that