@shader, I too am interested in getElementById of a hiccup component. If you find anything, please share.

I mean I can use getElementById, but is there any way to get it at the render time to avoid DOM lookup?

@shader you can get dom node of your component using reagent/dom-node

so you could create a component like this:

(defn qr-component
 []
 (reagent/create-class
  {:reagent-render (fn [] [:div])
   :component-did-mount
   (fn [this]
    (let [element (reagent/dom-node this)]
     (js/QRCode. element "")))}))

@negaduck I guess this also answers your question?

you could also use a callback ref to initialize the component

(defn qr [] [:div {:ref (fn [node] (when node (js/QRCode. node ...)))))

didn't count the parentheses so YMMV 🙂

TIL!

yeah it's kind of neat

https://presumably.de/reagent-mysteries-part-3-manipulating-the-dom.html

awesome, thank you guys

Is it possible to use re-frame on the server? I would like to have there a single in memory db, too. Then I would like to somehow attach functions to subscriptions which get called whenever the subscription data changes. Could this work?

@witek perhaps you could use datascript to have the same effect?

there are events and subscriptions in datascript?

I like the "data flowing" idea in re-frame. I would like to build the server application the same way. But I am not sure if re-frame is the right tool for it. And I have no idea how to attach a function to a re-frame subscription, so that it gets called whenever the subscription data changes. I also would like to dispatch events instead of changing my state directly.

@witek re-frame subs are just atoms (`reagent/atom`s actually) you can add-watch them just like any other I believe.

IIRC datascript has listen which lets you attach fn handlers