What do people think, should I release 0.8.0 as is or try to understand first if there are some problems still we could fix?

Proper release would probably encourage more to try this

There is probably problems with running this on Node, but I think this is caused by bug in Cljs

I would release a beta version

With an expectation for full release in a month

For some the risk of React 16 will be worth it. And they can help to identify problems.

React 16 support is not merged yet

But I could try fixing the problems with it, but keep the 15 as default

Sorry, i misunderstood

Made some progress with improving test runner just now, found some strange cases where some React things work differently UMD build vs. Node module and Browser vs. Node 😄

Trying to use reagent with React Native + Expo. Getting this error:

No such namespace: cljsjs.react, could not locate cljsjs/react.cljs, cljsjs/react.cljc, or JavaScript source providing "cljsjs.react" in file ..boot-expo/zbu/-d8mh6z/main.out/reagent/impl/util.cljs

[reagent "0.6.0-SNAPSHOT" :exclusions [cljsjs/react cljsjs/react-dom cljsjs/react-dom-server]]
[re-frame "0.7.0"]

package.json deps:

"dependencies": {
    "babel-preset-expo": "^4.0.0",
    "expo": "^21.0.0",
    "react": "16.0.0-alpha.12",
    "react-native": ""
  },

Been digging, cannot figure out how Reagent supports closures as callbacks, as in this component from the “simple” example:

(defn color-input []
  [:div.color-input
   "Time color: "
   [:input {:type "text"
            :value @time-color
            :on-change #(reset! time-color (-> % .-target .-value))}]])

Starting to think React is doing that since it has a custom event mechanism.

Anyone have a clue or pointer to some relevant doc?

what do you mean @hiskennyness - react doesn't have to do anything special to support closures as callbacks - they are just plain js functions

Thx, @mccraigmccraig. I was assuming the initial page got generated as a big wodge of string HTML. I thought I read that somewhere as being a performance win vs assembling the nodes in JS. But I think something interesting is going on: inspecting a React page in the debugger the only listeners I see are on the document. And the input element above does not show any event listener, just a ‘react_id” or sth.

uh, well you can render server-side... i've heard of some react/reagent users doing that - i've no idea if it's very common to do it though

but i'm seeing handlers on elements in my app - https://www.evernote.com/l/AD4rNLlwU7RPy4ukE-8thUq3AFexk3fi9b0

although the http://sentry.io client, raven.js, is rather obscuring their origin

OK, I’ll keep digging. Thx for the datapoints.

Looks like little if any advantage to building page initially by dumping a big string of HTML into innerHTML. That makes things easier.

@hiskennyness Yes, it is React that puts all listeners on the highest DOM level, not the lower levels in the DOM.