@ejelome what kind?

https://facebook.github.io/react-native/docs/using-navigators.html#pushing-scenes-onto-the-stack

I'm literally confused how to actually do the this.props.onForward (and .onBack)

I can display the text, e.g. [touchable-highlight {:on-press <no-idea-here>} [text "Tap me to load the next scene"]], but I have no idea how can I actually call that function via this.props.onForward or this.props.onBack

@ejelome the code in onForward is all about pushing a new route onto stack.

the navigation object should contain information on what current route you’re in, and that helps you decide what view to show, given the route index or key.

I would recommend you use navigationExperimental though, because that’s the future, and they’ve said this is what they’re going to support in the future.

it’s also highly compatible with om.next

hey, thanks @levitanong, will look on that navigationExperimental, although for the meantime, I would like to do a 1:1 version of the samples, this is the last one afaik, I've tried this: core.cljs:

[navigator {:initialRoute {:title "My Initial Scene"
                           :index 0}
            :renderScene (fn [route, navigator_]
                           [my-scene {:title (.-title route)
                                      :onForward (fn []
                                                   (.push navigator {:title "Scene" (.-index route)
                                                                     :index (inc (.-index route))}))
                                      :onBack (fn []
                                                (if (pos? (.-index route))
                                                  (.pop navigator_)))}])}]

(def my-scene [props]
  [view
   [text "Current Scene: " (.-title props)]
   [touchable-highlight {:onPress (.-onForward props)}
    [text "Tap me to load the next scene"]]
   [touchable-highlight {:onPress (.-onBack props)}
    [text "Tap me to go back"]]])

😞

unfortunately, it doesn't work

you probably need to pass a js data structure to .push

not a cljs data strcuture

@ejelome i concur with @pesterhazy

thanks for the hint, and can I also know what's the proper way of calling props?

I feel like the above code is wrong, not just the data structure

i don’t think there’s anything wrong with (.push navigator)

esp. the way I accessed onForward and onBack

yeah you're strangely passing onForward to your own component (?)

my scene receives a javascript prop object

somehow

ah that's a translation of the example in the fb docs

but he’s passing a cljs object to my-scene

and accessing it like js

inside my-scene

right, that's just a 1:1 conversion from the docs

an attempt if I may add

well the problem is just in calling a reagent component

have you looked into reagent's documentation yet?

here are some resources: https://github.com/reagent-project/reagent/wiki/Links-and-Resources

tbh, I just scratched the surface of reagent, then dove straight to re-natal

I will look on these things once I'm in my machine 🙂

so you don't need to pass on-forward etc at all

you need to make the navigator available to the component

one more problem

you need (r/as-element [my-scene ...]) in the render-scene fn

RN doesn't know how to do anything with clojurescript PersistenVectors

oh, I have that on my machine, forgot to type it again here XD, yes, I did that, but my main confusion was accessing the props

I'll back read all of these once I get back to my machine

thanks @levitanong and @pesterhazy, very helpful, appreciate it 🙂

you're welcome

It'd be great if you could add some docs on how to use the navigator here: https://github.com/mjmeintjes/boot-react-native/wiki/Using-React-Components

maybe even add your 1-1 translation of the navigator example in the RN docs?

that'd be super helpful to newcomers

oh, sure, I'd be happy to add info there 🙂

great

I'm trying to compile to run a re-natal/om-net project on an iOS device and I'm getting:

om-1.0.0-alpha41.jar!/om/externs.js:4: WARNING - name React is not defined in the externs.

you may not need to care about externs

personally I'm not convinced adv compilation makes much sense with react native

Looks like there was a breaking change from .39 to .40 w/r/t native modules? https://medium.com/@thisismissem/how-to-upgrade-react-native-modules-in-a-backwards-compatible-manner-a5b5c48d590c#.6cy9nzepv

How on earth anyone thought renaming a header file was ever a good idea, I don't know honestly