get rid of your redundant render-func? 😄

@reefersleep: can you directly render an atom ?

if not, how does rc/render know to re-update when the atom changes ?

I’m guessing not, but I’d test it for sure

rc/render needs some kind of hiccup structure to display anything, I bet

I don’t understand how your two questions are related

Can you deliberate on your logic? 🙂

I thought you were sugestnig (rc/render @gui-state app-div)

If I wanted to display my state atom, I’d just wrap it in a [:div] or [:pre]

Oh, sorry about that. I was kidding, actually. I see that you mean to refer to your let-binding in rc/render, but you managed to write two different symbol names 😉

render-func and render-state

I see, they should both be render-func .... that was a typo on my part (half refactoring)

Maybe just: (rc/render [:pre @gui-state] app-div) ?

not sure if you can use literal hiccup directly in rc/render

why would that update when gui-state changes ?

think I actually saw some issue related to it a while ago

hm, good point

Your code is pretty minimal already 🙂 Does it work without wrapping the dereffed state, though? I guess it’s indirectly wrapped in your app-div element

Without wrapping it in some dom element, I mean.

1. I'm no longer convinced my original question is working on anymore.

😄

2. the original problem was this: was streaming state from websocket from server to client

so the client was literally "get this hiccup from websocket, render it"

interesting!

and this 'atom' was just a layer of indirection to store the state; either way, I'm okay with keeping the render-func around

Yeah, that doesn’t seem superfluous to me

you’ve even scoped it as minimally as possible

yeah, I find the clj repl much nicer to work with than the cljs repl, so this way, I can write client side code in *.cljc, run the updates in clj/jvm, and have it send the hiccup to cljs, which just does a dumb render

huh

So it’s purely for development support?

right, latency would be too much in production

only works when browser + jvm are on same machine

Alright. Nice tool!

Maybe it makes sense to opensource it?

If others agree with your proclivities

don't want to deal with support + feature requests + .... for now 🙂

😄

Gotcha.

Did you get it working again?

yeah, all is working at the moment

brilliant :thumbsup:

I'm reading https://stackoverflow.com/questions/32367273/touch-left-touch-right-events-in-reagent -- and wondering -- is there sample reagent + touch event code somewhere ?