ApplicationInstance encapsulates all of the stateful aspects of a running
At a high-level, we break application boot into two distinct phases:
- Definition time, where all of the classes, templates, and other dependencies are loaded (typically in the browser).
- Run time, where we begin executing the application once everything has loaded.
Definition time can be expensive and only needs to happen once since it is an idempotent operation. For example, between test runs and FastBoot requests, the application stays the same. It is only the state that we want to reset.
That state is what the
ApplicationInstance manages: it is responsible for creating the container that contains all application state, and disposing of it once the particular test run or FastBoot request has finished.
setupRegistry (registry, options) private
Application for which this is an instance.
The DOM events for which the event dispatcher should listen.
By default, the application's
Ember.EventDispatcher listens for a set of standard DOM events, such as
keyup, and delegates them to your application's
The root DOM element of the Application as an element or a jQuery-compatible selector string.
© 2017 Yehuda Katz, Tom Dale and Ember.js contributors
Licensed under the MIT License.