问题
In my app I have a requirement for a functional area to open in an overlay such that it sits on top of the current route which could be almost any other route in the app.
This functional area will have it's own routes as it contains at least a master-detail view.
What is the current best practice for dealing with this situation?
Is it possible to have top-level routes that don't tear down the current route/views when entering them? If not and it's necessary to have the ApplicationController (or similar) handle the globally accessible overlay, what's the best way to achieve router-like functionality for that area?
回答1:
I think you got confused by open in overlay requirement and you are trying to solve non-existing problem.
Opening messaging functionality in another page in your app or opening it as overlay on top of the app is just a design thing that should be handled by CSS and existing app router. Just create messaging route, controller, etc.
You didn't say that, but in case you want to boot separate application there, the best approach is to open it in the iframe. New app, new lifecycle, etc. Again, how you display it inside another app is just matter of CSS.
来源：https://stackoverflow.com/questions/16415686/multiple-routers-in-ember-js