@Fran-Diox Thanks Fran. Yea, I had some old code in there that I had forgotten about. Thanks for the quick response.

@Fran-Diox Hey, thanks for the answer and I’ll take a look into the new tabbar.

@sherscher never tried to use react-flip-move itself but you can better control the rendering of lists if you do something like this: <List> {this.state.listItems.map(function(data, i){ return <ListItem>{{data}}</ListItem> })} </List> Hope it helps.

@Fran-Diox Think you’re right. I’ll just park the tab bar at the bottom on Android. Little strange, but probably not as strange as what I was originally envisioning. Thanks for the help!

@Fran-Diox I’m hitting some (maybe basic) issue. You mentioned before that the the Splitter should be the parent of Navigator for this to work. But then, how can I pass the APP Navigator instance to the Page within the SplitterSide component? Am I missing something simple? J.

@cyclops24: you might consider a more flexible alternative. By that I mean that you manage state via a parent component that automatically gets rerendered whenever you click a new menu item: https://community.onsen.io/topic/821/splitterside/3

The answer from here worked for me to solve this exact warning: https://github.com/OnsenUI/react-onsenui/issues/107 You need to add the key property to both content and tab, like this: { content: <MyTab title="Settings" key={2} />, tab: <Ons.Tab label="Settings" key={2} /> } This solved the warning for me.

Does it mean you can use Polymer Webcomponents as well?

@coolman monaca preview is for development and loads everything in memory for faster debugging. If you want to test your app in real devices I’d recommend you using Monaca Debugger (and just run monaca debug in the CLI). That will put all the transpiled files in the device and refresh the app whenever you modify your code. Otherwise, just run monaca transpile to perform an actual transpilation of your coed and generate files.

@Fran-Diox work like a charm! Thank you. ^_^

@ephraimt Thanks :)