That would be awesome if you could do that! In the mean time i’ll go dig into on-splitter and what would be required to upgrade to onsen v2.
How would one go about making an ons-navigator page stack that can use different .html pages interchangeably with the ability to pass data between them?
I have a a sliding menu with individual page stacks, ons-navigator, for each of the pages in the slide menu. Each stack, in the slide menu, has its own ons-navigator with some number of pages that can be navigated to in the stack, while passing data from one to the next (think list of items, then click on an item to view the detail of said item).
The problem is when i want to use the same .html template in different navigators (different slide menu items) without having to recreate for each use case and pass data between them. I currently am passing data by accessing the page’s navigator by name, and getting the data from the previous page. But since the page in question can be used in different slide menu items (with a different ons-navigator), calling the navigator by name in the controller is not exactly modular (it would be hard coded with some switch for each case).
This is a simplified example of course.