[ClojureScript] Reagent/Om Native

[Wei Hsu]

Now that React Native is open source, who's working on porting our ClojureScript interfaces to mobile?

I have some preliminary attempts but would love to join a more concerted effort.

[Mike Haney]

I know David has had access to react native since January, and based on his tweets I suspect he has a version of Om ready to go.

Reagent is my wrapper of choice, so I would be happy to help in any way I can with a reagent-native port.

[David Nolen]

Not "ready to go". Mike Fikes has made various attempts some which have
worked and some which have stopped working as React Native is pretty
churn-y for the obvious reasons. React Native also has a custom build setup
which we either need to work around or subvert.

So not there yet. But probably less far off than you think. Mike Fikes has
poured a ton of effort into Ambly which I think will be essential if people
want to have a productive Clojure-y workflow on iOS.

David

Post by Mike Haney
I know David has had access to react native since January, and based on
his tweets I suspect he has a version of Om ready to go.
Reagent is my wrapper of choice, so I would be happy to help in any way I
can with a reagent-native port.
--
Note that posts from new members are moderated - please be patient with your first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/clojurescript.

[Mike Fikes]

The two primary challenges, as I currently see them:

1. The custom React Native build setup David referred to also involves CommonJS dependencies.
2. The need to revise existing React ClojureScript libraries in order to work with React Native.

For item #1, I was simply cheating for now, and using a dump of the React Native "packager" output. CLJS-1044 and/or CLJS-1092 could potentially help in that area in the long run.

For item #2, I was primary experimenting with Om, and had partial success in that Om appeared to be initializing and was properly setting a text attribute on an Objective-C React Native component, but things were not rendering properly for me.

And yes, React Native has itself been evolving. (In fact, with the React Native release, there appears to be an issue that causes ClojureScript's JavaScript and React Native's JavaScript to be in two distinct JavaScriptCore instances—the underlying problem has already been reported as issue #288.) But, now that it is released, we can fork it, fix things for ourselves temporarily as needed and share those fixes with each other, etc. And, the Facebook team is very responsive.

Ambly itself is in good shape, having had a month or two to mature. Most of the kinks have been worked out of it so it can serve as a stable REPL for exploring React Native on iOS.