@Taymindis Regarding ons-splitter-side, it supports two modes: collapsed and split. When it’s in collapsed mode it will be hidden from view and can be displayed when the user swipes the screen or taps a button. In split mode the element is always shown. It can be configured to automatically switch between the two modes depending on the screen size.
So when the mode changes, that event is fired. Referencing the docs here:
Prior to Onsen, my favorite drag and drop would have been Ionic Builder except for all the limitations I encountered. After that it has been Monaca Cloud IDE with Onsen. I know its not D&D, but with the Onsen framework and the real-time preview, I am able to work like it is PLUS no limitations.
Not entirely certain on this one, I don’t know if you mean Onsen or a project I have done.
6 on my team, but regarding mobile / hybrid, its just me!
I lost them a long time ago!
I’ve already answered in the issue but I will paste the answer here as well:
I was trying to integrate the Navigator component with react-router but the code was very hacky.
Maybe I will make another attempt and see if it’s possible to create a wrapper component that you can use together with react-router.
In the end we will probably create a new component with an API that better integrates with things like react-router and Redux. Right now the component has methods like pushPage() and popPage() that makes things hard. A better option would be to make it possible to navigate using props.
So basically it’s possible to integrate it but the current API makes it a bit cumbersome.
@mishoboss For this specific scenario (and there may be a better method using Onsen), I would just push and pop pages so only one was actually stored. Push the page name to an array, have a backbutton event listener where you can use FILO principle to display the appropriate page.