I am trying to understand whether States in Ember.js are only designed/assumed to be defined in a route manager, and whether routes are integral to Ember. Pretty much all of the guides I've seen seem to assume you want states and routes exactly matching.
I want to create states that are not dependent on routes, but just on the state of the application. For example, in an email client, I might have a state "userHasSpecifiedRecipient." Only if this state is true might I enable the message box of the form. But obviously I don't want the url to be:
myEmailClient.com#composingMessage_userHasSpecifiedRecipient_userIs...
etc.
Are there examples of this?
Second question: Can I mix states that are coupled with routes and states that are not?
Finally: I saw some advice that recommended people use Ember's sproutcore-statechart addon if they want things like concurrent states. Is this still true?