Hey guys, has anyone encountered this error message using reagent or re-frame?

Load failed: Jsloader error (code #1): Timeout reached for loading script /js/main.out/tomaton/components/dashboard.js?zx=kgscuwybhheb

It looks like a problem with the Google Closure Compiler. Maybe the host it is trying to fetch is not answering the request for the dashboard script on time

is normal that I have to refresh my page when I change hiccup code to see it appear ?

i'm using boot-cljs

@yenda: depends on what task ou have running. https://github.com/magomimmo/modern-cljs/blob/master/doc/second-edition/tutorial-01.md this guide explains the tasks well.

sooheon: I already have an immediate feedback loop, for instance when I change a handler, I don't have to refresh

however when I change a component it doesn't rerender

I thought it was boot-reload which took care of that. So you have that running?

yes

This is my core.cljs

if I do a mount-root in the repl it refreshes the components like I would expect them

I havent used the system task, but I’m curious if it should come later in the task? Not sure.

just thinking out loud with you

calling (reagent/force-update-all) works as well

I think it is not the tooling but rather a thing with reagent/react

since everything is effectively updated except for the components

and (reagent/force-update-all) does the job

ah then it may be the way you wrote the components can I see it?

@yenda: r u using figwheel?

I had a similar issue, and it was that I was using form-2 functions and not passing args to the inner fn

@shaym no boot-cljs

for figwheel i had to add a reload hook , you might need the same

@yenda: ^

@sooheon: even simple components like

hmmm does boot-cljs even does hot loading?

@shaym: yes, like I said the components are not updated but the handlers and subscriptions are

@shaym: how did you hook your function ?

and wouldnt it work just as well with (reagent/force-update-all) ?

@yenda: figwheel triggers the on-js-reload event whenever a file is saved, i believe that force update is "heavier" then a render

@yenda: i believe that render does a diff , where force update recalculates the whole virtual DOM

I suppose I should be searching for a hook in boot-reload then to seek the same behavior

i suspect so

(reload :on-jsload 'app.core/main)

I wonder how boot could differenciate the cljs and clj core files

it works

cool

@jakemcc: i have considered FB , but i also need to hook up a db to the server , which is not easy to with FB

does anybody know how to use the :on-set attrib in reagent's make-reaction function? I set a function for it like (fn [oldv newv] (println "on-set")) and it never prints

@mpdairy: it looks like on-set is only called during reset!, which doesn't make much sense in a Reaction. However, this example will trigger it:

(def num (r/atom 5))

(def doubled (reagent.ratom/make-reaction #(* 2 @num) :on-set (fn [oldv newv] (println "onset" oldv newv))))

(println "num:" @num "doubled:" @doubled)
;=>num: 5 doubled: 10

(reset! num 7)

(println "num:" @num "doubled:" @doubled)
;=> num: 7 doubled: 14

(reset! doubled 11)
;=> onset 14 11

(println "num:" @num "doubled:" @doubled)
;=>num: 7 doubled: 14

reset!-ing a Reaction will trigger the function, but then when it gets deref-ed again, it re-evaluates to the normal value (14)

Ah, thanks @sashton, you are right

Ok, now I can't get on-dispose to do anything but give me an error. I'm doing :on-dispose (fn [] (do (println "GOODBYE") true)) in make-reaction