@weltan: I know what you are referring to, the fact that scenes animate in transitions make for weird behavior, I have thought a bit about it. Since NavigationExperimental have been very unstable I’ve been hesitant to implement some advanced solution for now though and just let it do those weird switches. I’m not releasing my app yet. My initial idea of how to solve it was to experiment with :should-component-update and prevent scenes from updating if it was in transition. But your solution looks good. Btw, I think it would be good if we kept fragmentation in our small community as low as possible. And since you obviously have improved stuff I would be happy to merge those changes if you’d open a PR. Or is there some reason you want different repos?

👍 for collaboration

@weltan: This issue with animations screwing things up with re-frame is not only present in navigations but also in things like toggles. Ideally one would address all these issues at the same time… Needs some hammock time though.

@doglooksgood: I’ve been trying react-native-navigation recently, with boot-react-native, om.next, etc. and not getting very far.

somebody should write a blog post comparing the different Navigator options for RN (and BRN)

it's a jungle out there

yep… I’m looking thru re-navigate right now.

it’s the (.registerComponent …) that’s giving me an issue

@vikeri: what .registerComponent is that? the one from react-native-navigation?

I think that NavigationExperimental fits very well with re-frame and thus can be applied without too much abstractions as in re-navigate. I think that navigation sometimes is made more complicated than it is. I admit that the complexity of the UI of my app is not too high though. But generally the two features I think I will use are switching between different ”pages" in the app (with tabs) and going deeper into those pages with the normal nested navigation.

that would fit my needs

@boorad: It’s the normal AppRegistry.registerComponent

I’m trying to do this from cljs:

https://github.com/wix/react-native-navigation/blob/master/example/src/screens/index.ios.js#L15

with

(.registerComponent rr/Navigation name (fn [] component)))

Oh, I don’t know anything about react-native-navigation. re-navigate uses no libraries.

Navigation.registerComponent('example.FirstTabScreen', () => FirstTabScreen);

ah, got it… sry

You probably need r/reactify-component?

not using reagent 😞

guess I’ll pull it in

@boorad: Can’t help you then 😑, why not reagent?

no reason, it’s probably my issue

I’m newer than most at this stuff - old erlang guy coming into this new hipster JS stuff

Haha ok! But are you using om/om-next, other wrapper or just vanilla?

om-next

Ok, exciting! Works well? What storage do you use?

@boorad is boot-react-native working with om-next?

maybe you could contribute a starter example 🙂

yes, I’d love to after I get a couple of example scenes / screens working

manipulate a bit of state w/ om-next and send it over to you

🙂

IMHO - om-next is a bit rough for new comers, but very cool indeed 🙂

I really like re-frame but I’m a little worried about performance. Would om-next be better?

@artemyarulin: om-next makes a bunch of sense to me on state manipulation, as well as friendliness to CQRS

@boorad: Yeah, ideas in om-next are really powerful. What do you use (plan to use) on backend? Datomic?

possibly - or ArangoDB

datomic as graph or arango