Class Ember.Application
publicAn instance of Ember.Application
is the starting point for every Ember
application. It helps to instantiate, initialize and coordinate the many
objects that make up your app.
Each Ember app has one and only one Ember.Application
object. In fact, the
very first thing you should do in your application is create the instance:
1 |
window.App = Ember.Application.create(); |
Typically, the application object is the only global variable. All other
classes in your app should be properties on the Ember.Application
instance,
which highlights its first role: a global namespace.
For example, if you define a view class, it might look like this:
1 |
App.MyView = Ember.View.extend(); |
By default, calling Ember.Application.create()
will automatically initialize
your application by calling the Ember.Application.initialize()
method. If
you need to delay initialization, you can call your app's deferReadiness()
method. When you are ready for your app to be initialized, call its
advanceReadiness()
method.
You can define a ready
method on the Ember.Application
instance, which
will be run by Ember when the application is initialized.
Because Ember.Application
inherits from Ember.Namespace
, any classes
you create will have useful string representations when calling toString()
.
See the Ember.Namespace
documentation for more information.
While you can think of your Ember.Application
as a container that holds the
other classes in your application, there are several other responsibilities
going on under-the-hood that you may want to understand.
Event Delegation
Ember uses a technique called event delegation. This allows the framework
to set up a global, shared event listener instead of requiring each view to
do it manually. For example, instead of each view registering its own
mousedown
listener on its associated element, Ember sets up a mousedown
listener on the body
.
If a mousedown
event occurs, Ember will look at the target of the event and
start walking up the DOM node tree, finding corresponding views and invoking
their mouseDown
method as it goes.
Ember.Application
has a number of default events that it listens for, as
well as a mapping from lowercase events to camel-cased view method names. For
example, the keypress
event causes the keyPress
method on the view to be
called, the dblclick
event causes doubleClick
to be called, and so on.
If there is a bubbling browser event that Ember does not listen for by
default, you can specify custom events and their corresponding view method
names by setting the application's customEvents
property:
1 2 3 4 5 6 |
let App = Ember.Application.create({ customEvents: { // add support for the paste event paste: 'paste' } }); |
To prevent Ember from setting up a listener for a default event,
specify the event name with a null
value in the customEvents
property:
1 2 3 4 5 6 7 |
let App = Ember.Application.create({ customEvents: { // prevent listeners for mouseenter/mouseleave events mouseenter: null, mouseleave: null } }); |
By default, the application sets up these event listeners on the document body. However, in cases where you are embedding an Ember application inside an existing page, you may want it to set up the listeners on an element inside the body.
For example, if only events inside a DOM element with the ID of ember-app
should be delegated, set your application's rootElement
property:
1 2 3 |
let App = Ember.Application.create({ rootElement: '#ember-app' }); |
The rootElement
can be either a DOM element or a jQuery-compatible selector
string. Note that views appended to the DOM outside the root element will
not receive events. If you specify a custom root element, make sure you only
append views inside it!
To learn more about the events Ember components use, see components/handling-events.
Initializers
Libraries on top of Ember can add initializers, like so:
1 2 3 4 5 6 7 |
Ember.Application.initializer({ name: 'api-adapter', initialize: function(application) { application.register('api-adapter:main', ApiAdapter); } }); |
Initializers provide an opportunity to access the internal registry, which organizes the different components of an Ember application. Additionally they provide a chance to access the instantiated application. Beyond being used for libraries, initializers are also a great way to organize dependency injection or setup in your own application.
Routing
In addition to creating your application's router, Ember.Application
is
also responsible for telling the router when to start routing. Transitions
between routes can be logged with the LOG_TRANSITIONS
flag, and more
detailed intra-transition logging can be logged with
the LOG_TRANSITIONS_INTERNAL
flag:
1 2 3 4 |
let App = Ember.Application.create({ LOG_TRANSITIONS: true, // basic logging of successful transitions LOG_TRANSITIONS_INTERNAL: true // detailed logging of all routing steps }); |
By default, the router will begin trying to translate the current URL into
application state once the browser emits the DOMContentReady
event. If you
need to defer routing, you can call the application's deferReadiness()
method. Once routing can begin, call the advanceReadiness()
method.
If there is any setup required before routing begins, you can implement a
ready()
method on your app that will be invoked immediately before routing
begins.
addObserver (key, target, method) public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:333
- key
- String
- The key to observer
- target
- Object
- The target object to invoke
- method
- String|Function
- The method to invoke.
Adds an observer on a property.
This is the core method used to register an observer for a property.
Once you call this method, any time the key's value is set, your observer will be notified. Note that the observers are triggered any time the value is set, regardless of whether it has actually changed. Your observer should be prepared to handle that.
You can also pass an optional context parameter to this method. The context will be passed to your observer method whenever it is triggered. Note that if you add the same target/method pair on a key multiple times with different context parameters, your observer will only be called once with the last context you passed.
Observer Methods
Observer methods you pass should generally have the following signature if
you do not pass a context
parameter:
1 |
fooDidChange: function(sender, key, value, rev) { }; |
The sender is the object that changed. The key is the property that changes. The value property is currently reserved and unused. The rev is the last property revision of the object when it changed, which you can use to detect if the key value has really changed or not.
If you pass a context
parameter, the context will be passed before the
revision like so:
1 |
fooDidChange: function(sender, key, value, context, rev) { }; |
Usually you will not need the value, context or revision parameters at the end. In this case, it is common to write observer methods that take only a sender and key value as parameters or, if you aren't interested in any of these values, to write an observer that has no parameters at all.
advanceReadiness public
Defined in packages/ember-application/lib/system/application.js:523
Call advanceReadiness
after any asynchronous setup logic has completed.
Each call to deferReadiness
must be matched by a call to advanceReadiness
or the application will never become ready and routing will not begin.
cacheFor (keyName) Object public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:490
- keyName
- String
- returns
- Object
- The cached value of the computed property, if any
Returns the cached value of a computed property, if it exists. This allows you to inspect the value of a computed property without accidentally invoking it if it is intended to be generated lazily.
create (arguments) public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:635
- arguments
Creates an instance of a class. Accepts either no arguments, or an object containing values to initialize the newly instantiated object with.
1 2 3 4 5 6 7 8 9 10 11 |
App.Person = Ember.Object.extend({ helloWorld: function() { alert("Hi, my name is " + this.get('name')); } }); var tom = App.Person.create({ name: 'Tom Dale' }); tom.helloWorld(); // alerts "Hi, my name is Tom Dale". |
create
will call the init
function if defined during
Ember.AnyObject.extend
If no arguments are passed to create
, it will not set values to the new
instance during initialization:
1 2 |
var noName = App.Person.create(); noName.helloWorld(); // alerts undefined |
NOTE: For performance reasons, you cannot declare methods or computed
properties during create
. You should instead declare methods and computed
properties when using extend
.
decrementProperty (keyName, decrement) Number public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:453
- keyName
- String
- The name of the property to decrement
- decrement
- Number
- The amount to decrement by. Defaults to 1
- returns
- Number
- The new property value
Set the value of a property to the current value minus some amount.
1 2 |
player.decrementProperty('lives'); orc.decrementProperty('health', 5); |
deferReadiness public
Defined in packages/ember-application/lib/system/application.js:491
Use this to defer readiness until some condition is true.
Example:
1 2 3 4 5 6 7 8 9 |
let App = Ember.Application.create(); App.deferReadiness(); // Ember.$ is a reference to the jQuery object/function Ember.$.getJSON('/auth-token', function(token) { App.token = token; App.advanceReadiness(); }); |
This allows you to perform asynchronous setup logic and defer booting your application until the setup has finished.
However, if the setup requires a loading UI, it might be better to use the router for this purpose.
destroy Ember.Object public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:417
- returns
- Ember.Object
- receiver
Destroys an object by setting the isDestroyed
flag and removing its
metadata, which effectively destroys observers and bindings.
If you try to set a property on a destroyed object, an exception will be raised.
Note that destruction is scheduled for the end of the run loop and does not happen immediately. It will set an isDestroying flag immediately.
extend (mixins, arguments) public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:527
- mixins
- Mixin
- One or more Mixin classes
- arguments
- Object
- Object containing values to use within the new class
Creates a new subclass.
1 2 3 4 5 |
App.Person = Ember.Object.extend({ say: function(thing) { alert(thing); } }); |
This defines a new subclass of Ember.Object: App.Person
. It contains one method: say()
.
You can also create a subclass from any existing class by calling its extend()
method.
For example, you might want to create a subclass of Ember's built-in Ember.View
class:
1 2 3 4 |
App.PersonView = Ember.View.extend({ tagName: 'li', classNameBindings: ['isAdministrator'] }); |
When defining a subclass, you can override methods but still access the
implementation of your parent class by calling the special _super()
method:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
App.Person = Ember.Object.extend({ say: function(thing) { var name = this.get('name'); alert(name + ' says: ' + thing); } }); App.Soldier = App.Person.extend({ say: function(thing) { this._super(thing + ", sir!"); }, march: function(numberOfHours) { alert(this.get('name') + ' marches for ' + numberOfHours + ' hours.'); } }); var yehuda = App.Soldier.create({ name: "Yehuda Katz" }); yehuda.say("Yes"); // alerts "Yehuda Katz says: Yes, sir!" |
The create()
on line #17 creates an instance of the App.Soldier
class.
The extend()
on line #8 creates a subclass of App.Person
. Any instance
of the App.Person
class will not have the march()
method.
You can also pass Mixin
classes to add additional properties to the subclass.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
App.Person = Ember.Object.extend({ say: function(thing) { alert(this.get('name') + ' says: ' + thing); } }); App.SingingMixin = Mixin.create({ sing: function(thing){ alert(this.get('name') + ' sings: la la la ' + thing); } }); App.BroadwayStar = App.Person.extend(App.SingingMixin, { dance: function() { alert(this.get('name') + ' dances: tap tap tap tap '); } }); |
The App.BroadwayStar
class contains three methods: say()
, sing()
, and dance()
.
get (keyName) Object public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:100
- keyName
- String
- The property to retrieve
- returns
- Object
- The property value or undefined.
Retrieves the value of a property from the object.
This method is usually similar to using object[keyName]
or object.keyName
,
however it supports both computed properties and the unknownProperty
handler.
Because get
unifies the syntax for accessing all these kinds
of properties, it can make many refactorings easier, such as replacing a
simple property with a computed property, or vice versa.
Computed Properties
Computed properties are methods defined with the property
modifier
declared at the end, such as:
1 2 3 |
fullName: function() { return this.get('firstName') + ' ' + this.get('lastName'); }.property('firstName', 'lastName') |
When you call get
on a computed property, the function will be
called and the return value will be returned instead of the function
itself.
Unknown Properties
Likewise, if you try to call get
on a property whose value is
undefined
, the unknownProperty()
method will be called on the object.
If this method returns any value other than undefined
, it will be returned
instead. This allows you to implement "virtual" properties that are
not defined upfront.
getProperties (list) Object public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:143
- list
- String...|Array
- of keys to get
- returns
- Object
To get the values of multiple properties at once, call getProperties
with a list of strings or an array:
1 2 |
record.getProperties('firstName', 'lastName', 'zipCode'); // { firstName: 'John', lastName: 'Doe', zipCode: '10011' } |
is equivalent to:
1 2 |
record.getProperties(['firstName', 'lastName', 'zipCode']); // { firstName: 'John', lastName: 'Doe', zipCode: '10011' } |
getWithDefault (keyName, defaultValue) Object public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:415
- keyName
- String
- The name of the property to retrieve
- defaultValue
- Object
- The value to return if the property value is undefined
- returns
- Object
- The property value or the defaultValue.
Retrieves the value of a property, or a default value in the case that the
property returns undefined
.
1 |
person.getWithDefault('lastName', 'Doe'); |
hasRegistration (fullName) Boolean public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:110
- fullName
- String
- returns
- Boolean
Check if a factory is registered.
incrementProperty (keyName, increment) Number public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:433
- keyName
- String
- The name of the property to increment
- increment
- Number
- The amount to increment by. Defaults to 1
- returns
- Number
- The new property value
Set the value of a property to the current value plus some amount.
1 2 |
person.incrementProperty('age'); team.incrementProperty('score', 2); |
init public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:217
An overridable method called when objects are instantiated. By default, does nothing unless it is overridden during class definition.
Example:
1 2 3 4 5 6 7 8 9 10 11 |
App.Person = Ember.Object.extend({ init: function() { alert('Name is ' + this.get('name')); } }); var steve = App.Person.create({ name: "Steve" }); // alerts 'Name is Steve'. |
NOTE: If you do override init
for a framework class like Ember.View
,
be sure to call this._super(...arguments)
in your
init
declaration! If you don't, Ember may not have an opportunity to
do important setup work, and you'll see strange behavior in your
application.
initializer (initializer) public
Inherited from Ember.Engine packages/ember-application/lib/system/engine.js:185
- initializer
- Object
The goal of initializers should be to register dependencies and injections. This phase runs once. Because these initializers may load code, they are allowed to defer application readiness and advance it. If you need to access the container or store you should use an InstanceInitializer that will be run after all initializers and therefore after all code is loaded and the app is ready.
Initializer receives an object which has the following attributes:
name
, before
, after
, initialize
. The only required attribute is
initialize
, all others are optional.
name
allows you to specify under which name the initializer is registered. This must be a unique name, as trying to register two initializers with the same name will result in an error.
1 2 3 4 5 6 7 |
Ember.Application.initializer({ name: 'namedInitializer', initialize: function(application) { Ember.debug('Running namedInitializer!'); } }); |
before
andafter
are used to ensure that this initializer is ran prior or after the one identified by the value. This value can be a single string or an array of strings, referencing thename
of other initializers.
An example of ordering initializers, we create an initializer named first
:
1 2 3 4 5 6 7 8 9 |
Ember.Application.initializer({ name: 'first', initialize: function(application) { Ember.debug('First initializer!'); } }); // DEBUG: First initializer! |
We add another initializer named second
, specifying that it should run
after the initializer named first
:
1 2 3 4 5 6 7 8 9 10 11 |
Ember.Application.initializer({ name: 'second', after: 'first', initialize: function(application) { Ember.debug('Second initializer!'); } }); // DEBUG: First initializer! // DEBUG: Second initializer! |
Afterwards we add a further initializer named pre
, this time specifying
that it should run before the initializer named first
:
1 2 3 4 5 6 7 8 9 10 11 12 |
Ember.Application.initializer({ name: 'pre', before: 'first', initialize: function(application) { Ember.debug('Pre initializer!'); } }); // DEBUG: Pre initializer! // DEBUG: First initializer! // DEBUG: Second initializer! |
Finally we add an initializer named post
, specifying it should run after
both the first
and the second
initializers:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
Ember.Application.initializer({ name: 'post', after: ['first', 'second'], initialize: function(application) { Ember.debug('Post initializer!'); } }); // DEBUG: Pre initializer! // DEBUG: First initializer! // DEBUG: Second initializer! // DEBUG: Post initializer! |
initialize
is a callback function that receives one argument,application
, on which you can operate.
Example of using application
to register an adapter:
1 2 3 4 5 6 7 |
Ember.Application.initializer({ name: 'api-adapter', initialize: function(application) { application.register('api-adapter:main', ApiAdapter); } }); |
inject (factoryNameOrType, property, injectionName) public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:203
- factoryNameOrType
- String
- property
- String
- injectionName
- String
Define a dependency injection onto a specific factory or all factories of a type.
When Ember instantiates a controller, view, or other framework component it can attach a dependency to that component. This is often used to provide services to a set of framework components.
An example of providing a session object to all controllers:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
let App = Ember.Application.create(); let Session = Ember.Object.extend({ isAuthenticated: false }); // A factory must be registered before it can be injected App.register('session:main', Session); // Inject 'session:main' onto all factories of the type 'controller' // with the name 'session' App.inject('controller', 'session', 'session:main'); App.IndexController = Ember.Controller.extend({ isLoggedIn: Ember.computed.alias('session.isAuthenticated') }); |
Injections can also be performed on specific factories.
1 2 3 |
App.inject(<full_name or type>, <property name>, <full_name>) App.inject('route', 'source', 'source:main') App.inject('route:application', 'email', 'model:email') |
It is important to note that injections can only be performed on
classes that are instantiated by Ember itself. Instantiating a class
directly (via create
or new
) bypasses the dependency injection
system.
Note: Ember-Data instantiates its models in a unique manner, and consequently
injections onto models (or all models) will not work as expected. Injections
on models can be enabled by setting EmberENV.MODEL_FACTORY_INJECTIONS
to true
.
instanceInitializer (instanceInitializer) public
Inherited from Ember.Engine packages/ember-application/lib/system/engine.js:305
- instanceInitializer
Instance initializers run after all initializers have run. Because instance initializers run after the app is fully set up. We have access to the store, container, and other items. However, these initializers run after code has loaded and are not allowed to defer readiness.
Instance initializer receives an object which has the following attributes:
name
, before
, after
, initialize
. The only required attribute is
initialize
, all others are optional.
name
allows you to specify under which name the instanceInitializer is registered. This must be a unique name, as trying to register two instanceInitializer with the same name will result in an error.
1 2 3 4 5 6 7 |
Ember.Application.instanceInitializer({ name: 'namedinstanceInitializer', initialize: function(application) { Ember.debug('Running namedInitializer!'); } }); |
before
andafter
are used to ensure that this initializer is ran prior or after the one identified by the value. This value can be a single string or an array of strings, referencing thename
of other initializers.See Ember.Application.initializer for discussion on the usage of before and after.
Example instanceInitializer to preload data into the store.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
Ember.Application.initializer({ name: 'preload-data', initialize: function(application) { var userConfig, userConfigEncoded, store; // We have a HTML escaped JSON representation of the user's basic // configuration generated server side and stored in the DOM of the main // index.html file. This allows the app to have access to a set of data // without making any additional remote calls. Good for basic data that is // needed for immediate rendering of the page. Keep in mind, this data, // like all local models and data can be manipulated by the user, so it // should not be relied upon for security or authorization. // // Grab the encoded data from the meta tag userConfigEncoded = Ember.$('head meta[name=app-user-config]').attr('content'); // Unescape the text, then parse the resulting JSON into a real object userConfig = JSON.parse(unescape(userConfigEncoded)); // Lookup the store store = application.lookup('service:store'); // Push the encoded JSON into the store store.pushPayload(userConfig); } }); |
notifyPropertyChange (keyName) Ember.Observable public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:318
- keyName
- String
- The property key to be notified about.
- returns
- Ember.Observable
Convenience method to call propertyWillChange
and propertyDidChange
in
succession.
register (fullName, factory, options) public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:29
- fullName
- String
- type:name (e.g., 'model:user')
- factory
- Function
- (e.g., App.Person)
- options
- Object
- (optional) disable instantiation or singleton usage
Registers a factory that can be used for dependency injection (with
inject
) or for service lookup. Each factory is registered with
a full name including two parts: type:name
.
A simple example:
1 2 3 4 |
let App = Ember.Application.create(); App.Orange = Ember.Object.extend(); App.register('fruit:favorite', App.Orange); |
Ember will resolve factories from the App
namespace automatically.
For example App.CarsController
will be discovered and returned if
an application requests controller:cars
.
An example of registering a controller with a non-standard name:
1 2 3 4 5 6 7 8 9 10 |
let App = Ember.Application.create(); let Session = Ember.Controller.extend(); App.register('controller:session', Session); // The Session controller can now be treated like a normal controller, // despite its non-standard name. App.ApplicationController = Ember.Controller.extend({ needs: ['session'] }); |
Registered factories are instantiated by having create
called on them. Additionally they are singletons, each time
they are looked up they return the same instance.
Some examples modifying that default behavior:
1 2 3 4 5 6 7 8 9 10 11 |
let App = Ember.Application.create(); App.Person = Ember.Object.extend(); App.Orange = Ember.Object.extend(); App.Email = Ember.Object.extend(); App.session = Ember.Object.create(); App.register('model:user', App.Person, { singleton: false }); App.register('fruit:favorite', App.Orange); App.register('communication:main', App.Email, { singleton: false }); App.register('session', App.session, { instantiate: false }); |
registerOption (fullName, optionName, options) public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:120
- fullName
- String
- optionName
- String
- options
- Object
Register an option for a particular factory.
registerOptions (fullName, options) public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:142
- fullName
- String
- options
- Object
Register options for a particular factory.
registerOptionsForType (type, options) public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:162
- type
- String
- options
- Object
Allow registering options for all factories of a type.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
let App = Ember.Application.create(); let appInstance = App.buildInstance(); // if all of type `connection` must not be singletons appInstance.optionsForType('connection', { singleton: false }); appInstance.register('connection:twitter', TwitterConnection); appInstance.register('connection:facebook', FacebookConnection); let twitter = appInstance.lookup('connection:twitter'); let twitter2 = appInstance.lookup('connection:twitter'); twitter === twitter2; // => false let facebook = appInstance.lookup('connection:facebook'); let facebook2 = appInstance.lookup('connection:facebook'); facebook === facebook2; // => false |
registeredOption (fullName, optionName) Object public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:131
- fullName
- String
- optionName
- String
- returns
- Object
- options
Return a specific registered option for a particular factory.
registeredOptions (fullName) Object public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:152
- fullName
- String
- returns
- Object
- options
Return registered options for a particular factory.
registeredOptionsForType (type) Object public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:193
- type
- String
- returns
- Object
- options
Return the registered options for all factories of a type.
removeObserver (key, target, method) public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:385
- key
- String
- The key to observer
- target
- Object
- The target object to invoke
- method
- String|Function
- The method to invoke.
Remove an observer you have previously registered on this object. Pass
the same key, target, and method you passed to addObserver()
and your
target will no longer receive notifications.
reopen public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:681
Augments a constructor's prototype with additional properties and functions:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
MyObject = Ember.Object.extend({ name: 'an object' }); o = MyObject.create(); o.get('name'); // 'an object' MyObject.reopen({ say: function(msg){ console.log(msg); } }) o2 = MyObject.create(); o2.say("hello"); // logs "hello" o.say("goodbye"); // logs "goodbye" |
To add functions and properties to the constructor itself,
see reopenClass
reopenClass public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:717
Augments a constructor's own properties and functions:
1 2 3 4 5 6 7 8 9 10 |
MyObject = Ember.Object.extend({ name: 'an object' }); MyObject.reopenClass({ canBuild: false }); MyObject.canBuild; // false o = MyObject.create(); |
In other words, this creates static properties and functions for the class. These are only available on the class and not on any instance of that class.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
App.Person = Ember.Object.extend({ name : "", sayHello : function() { alert("Hello. My name is " + this.get('name')); } }); App.Person.reopenClass({ species : "Homo sapiens", createPerson: function(newPersonsName){ return App.Person.create({ name:newPersonsName }); } }); var tom = App.Person.create({ name : "Tom Dale" }); var yehuda = App.Person.createPerson("Yehuda Katz"); tom.sayHello(); // "Hello. My name is Tom Dale" yehuda.sayHello(); // "Hello. My name is Yehuda Katz" alert(App.Person.species); // "Homo sapiens" |
Note that species
and createPerson
are not valid on the tom
and yehuda
variables. They are only valid on App.Person
.
To add functions and properties to instances of
a constructor by extending the constructor's prototype
see reopen
reset public
Defined in packages/ember-application/lib/system/application.js:609
Reset the application. This is typically used only in tests. It cleans up the application in the following order:
- Deactivate existing routes
- Destroy all objects in the container
- Create a new application container
- Re-route to the existing url
Typical Example:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
let App; run(function() { App = Ember.Application.create(); }); module('acceptance test', { setup: function() { App.reset(); } }); test('first test', function() { // App is freshly reset }); test('second test', function() { // App is again freshly reset }); |
Advanced Example:
Occasionally you may want to prevent the app from initializing during setup. This could enable extra configuration, or enable asserting prior to the app becoming ready.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
let App; run(function() { App = Ember.Application.create(); }); module('acceptance test', { setup: function() { run(function() { App.reset(); App.deferReadiness(); }); } }); test('first test', function() { ok(true, 'something before app is initialized'); run(function() { App.advanceReadiness(); }); ok(true, 'something after app is initialized'); }); |
resolveRegistration (fullName) Function public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:19
- fullName
- String
- returns
- Function
- fullName's factory
Given a fullName return the corresponding factory.
set (keyName, value) Object public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:168
- keyName
- String
- The property to set
- value
- Object
- The value to set or `null`.
- returns
- Object
- The passed value
Sets the provided key or path to the value.
This method is generally very similar to calling object[key] = value
or
object.key = value
, except that it provides support for computed
properties, the setUnknownProperty()
method and property observers.
Computed Properties
If you try to set a value on a key that has a computed property handler
defined (see the get()
method for an example), then set()
will call
that method, passing both the value and key instead of simply changing
the value itself. This is useful for those times when you need to
implement a property that is composed of one or more member
properties.
Unknown Properties
If you try to set a value on a key that is undefined in the target
object, then the setUnknownProperty()
handler will be called instead. This
gives you an opportunity to implement complex "virtual" properties that
are not predefined on the object. If setUnknownProperty()
returns
undefined, then set()
will simply set the value on the object.
Property Observers
In addition to changing the property, set()
will also register a property
change with the object. Unless you have placed this call inside of a
beginPropertyChanges()
and endPropertyChanges(),
any "local" observers
(i.e. observer methods declared on the same object), will be called
immediately. Any "remote" observers (i.e. observer methods declared on
another object) will be placed in a queue and called at a later time in a
coalesced manner.
setProperties (hash) Object public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:213
- hash
- Object
- the hash of keys and values to set
- returns
- Object
- The passed in hash
Sets a list of properties at once. These properties are set inside
a single beginPropertyChanges
and endPropertyChanges
batch, so
observers will be buffered.
1 |
record.setProperties({ firstName: 'Charles', lastName: 'Jolley' }); |
toString String public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:467
- returns
- String
- string representation
Returns a string representation which attempts to provide more information
than Javascript's toString
typically does, in a generic way for all Ember
objects.
1 2 3 |
App.Person = Em.Object.extend() person = App.Person.create() person.toString() //=> "<App.Person:ember1024>" |
If the object's class is not defined on an Ember namespace, it will indicate it is a subclass of the registered superclass:
1 2 3 |
Student = App.Person.extend() student = Student.create() student.toString() //=> "<(subclass of App.Person):ember1025>" |
If the method toStringExtension
is defined, its return value will be
included in the output.
1 2 3 4 5 6 7 |
App.Teacher = App.Person.extend({ toStringExtension: function() { return this.get('fullName'); } }); teacher = App.Teacher.create() teacher.toString(); //=> "<App.Teacher:ember1026:Tom Dale>" |
toggleProperty (keyName) Boolean public
Inherited from Ember.Observable packages/ember-runtime/lib/mixins/observable.js:473
- keyName
- String
- The name of the property to toggle
- returns
- Boolean
- The new property value
Set the value of a boolean property to the opposite of its current value.
1 |
starship.toggleProperty('warpDriveEngaged'); |
unregister (fullName) public
Inherited from RegistryProxyMixin packages/ember-runtime/lib/mixins/registry_proxy.js:90
- fullName
- String
Unregister a factory.
1 2 3 4 5 6 7 8 |
let App = Ember.Application.create(); let User = Ember.Object.extend(); App.register('model:user', User); App.resolveRegistration('model:user').create() instanceof User //=> true App.unregister('model:user') App.resolveRegistration('model:user') === undefined //=> true |
visit (url, options) Promise<Ember.ApplicationInstance, Error> public
Defined in packages/ember-application/lib/system/application.js:777
- url
- String
- The initial URL to navigate to
- options
- Ember.ApplicationInstance.BootOptions
- returns
- Promise<Ember.ApplicationInstance, Error>
Boot a new instance of Ember.ApplicationInstance
for the current
application and navigate it to the given url
. Returns a Promise
that
resolves with the instance when the initial routing and rendering is
complete, or rejects with any error that occured during the boot process.
When autoboot
is disabled, calling visit
would first cause the
application to boot, which runs the application initializers.
This method also takes a hash of boot-time configuration options for
customizing the instance's behavior. See the documentation on
Ember.ApplicationInstance.BootOptions
for details.
Ember.ApplicationInstance.BootOptions
is an interface class that exists
purely to document the available options; you do not need to construct it
manually. Simply pass a regular JavaScript object containing of the
desired options:
1 |
MyApp.visit("/", { location: "none", rootElement: "#container" }); |
Supported Scenarios
While the BootOptions
class exposes a large number of knobs, not all
combinations of them are valid; certain incompatible combinations might
result in unexpected behavior.
For example, booting the instance in the full browser environment
while specifying a foriegn document
object (e.g. { isBrowser: true,
document: iframe.contentDocument }
) does not work correctly today,
largely due to Ember's jQuery dependency.
Currently, there are three officially supported scenarios/configurations. Usages outside of these scenarios are not guaranteed to work, but please feel free to file bug reports documenting your experience and any issues you encountered to help expand support.
Browser Applications (Manual Boot)
The setup is largely similar to how Ember works out-of-the-box. Normally,
Ember will boot a default instance for your Application on "DOM ready".
However, you can customize this behavior by disabling autoboot
.
For example, this allows you to render a miniture demo of your application into a specific area on your marketing website:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
import MyApp from 'my-app'; $(function() { let App = MyApp.create({ autoboot: false }); let options = { // Override the router's location adapter to prevent it from updating // the URL in the address bar location: 'none', // Override the default `rootElement` on the app to render into a // specific `div` on the page rootElement: '#demo' }; // Start the app at the special demo URL App.visit('/demo', options); }); |
Or perhaps you might want to boot two instances of your app on the same page for a split-screen multiplayer experience:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
import MyApp from 'my-app'; $(function() { let App = MyApp.create({ autoboot: false }); let sessionId = MyApp.generateSessionID(); let player1 = App.visit(`/matches/join?name=Player+1&session=${sessionId}`, { rootElement: '#left', location: 'none' }); let player2 = App.visit(`/matches/join?name=Player+2&session=${sessionId}`, { rootElement: '#right', location: 'none' }); Promise.all([player1, player2]).then(() => { // Both apps have completed the initial render $('#loading').fadeOut(); }); }); |
Do note that each app instance maintains their own registry/container, so they will run in complete isolation by default.
Server-Side Rendering (also known as FastBoot)
This setup allows you to run your Ember app in a server environment using Node.js and render its content into static HTML for SEO purposes.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
const HTMLSerializer = new SimpleDOM.HTMLSerializer(SimpleDOM.voidMap); function renderURL(url) { let dom = new SimpleDOM.Document(); let rootElement = dom.body; let options = { isBrowser: false, document: dom, rootElement: rootElement }; return MyApp.visit(options).then(instance => { try { return HTMLSerializer.serialize(rootElement.firstChild); } finally { instance.destroy(); } }); } |
In this scenario, because Ember does not have access to a global document
object in the Node.js environment, you must provide one explicitly. In practice,
in the non-browser environment, the stand-in document
object only need to
implement a limited subset of the full DOM API. The SimpleDOM
library is known
to work.
Since there is no access to jQuery in the non-browser environment, you must also
specify a DOM Element
object in the same document
for the rootElement
option
(as opposed to a selector string like "body"
).
See the documentation on the isBrowser
, document
and rootElement
properties
on Ember.ApplicationInstance.BootOptions
for details.
Server-Side Resource Discovery
This setup allows you to run the routing layer of your Ember app in a server environment using Node.js and completely disable rendering. This allows you to simulate and discover the resources (i.e. AJAX requests) needed to fufill a given request and eagerly "push" these resources to the client.
service.js | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
import BrowserNetworkService from 'app/services/network/browser'; import NodeNetworkService from 'app/services/network/node'; // Inject a (hypothetical) service for abstracting all AJAX calls and use // the appropiate implementaion on the client/server. This also allows the // server to log all the AJAX calls made during a particular request and use // that for resource-discovery purpose. export function initialize(application) { if (window) { // browser application.register('service:network', BrowserNetworkService); } else { // node application.register('service:network', NodeNetworkService); } application.inject('route', 'network', 'service:network'); }; export default { name: 'network-service', initialize: initialize }; |
app/routes/post.js | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
import Ember from 'ember'; // An example of how the (hypothetical) service is used in routes. export default Ember.Route.extend({ model(params) { return this.network.fetch(`/api/posts/${params.post_id}.json`); }, afterModel(post) { if (post.isExternalContent) { return this.network.fetch(`/api/external/?url=${post.externalURL}`); } else { return post; } } }); |
1 2 3 4 5 6 7 8 |
// Finally, put all the pieces together function discoverResourcesFor(url) { return MyApp.visit(url, { isBrowser: false, shouldRender: false }).then(instance => { let networkService = instance.lookup('service:network'); return networkService.requests; // => { "/api/posts/123.json": "..." } }); } |
willDestroy public
Inherited from Ember.CoreObject packages/ember-runtime/lib/system/core_object.js:440
Override to implement teardown.