Ember.js - where should interface state be stored?
Is there an official story for where interface state (as opposed to persisted model state) should live in an Ember.js app? In the "Responding to User-initiated Events" part of the Router docs , there's an example of delegating click events to a photo's "showPhoto" method, but having a model "show" itself seems like an undesirable mixing of concerns. I understand that in many cases state should be stored in the router so that the interface state is represented in the URL and is restored if you refresh the page or send the url to someone. But what about non-hierarchical state, such as the list