Ember.Application Class packages/ember-application/lib/system/application.js:28
Extends: Ember.Namespace
Defined in: packages/ember-application/lib/system/application.js:28
Module: ember-application
An 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 |
App = Ember.Application.create({ customEvents: { // add support for the paste event 'paste: "paste" } }); |
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 |
window.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 advantages of event delegation and the Ember view layer, and a list of the event listeners that are setup by default, visit the Ember View Layer guide.
Initializers
Libraries on top of Ember can register additional initializers, like so:
1 2 3 4 5 6 7 |
Ember.Application.initializer({ name: "store", initialize: function(container, application) { container.register('store:main', application.Store); } }); |
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 |
window.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.
```
Methods
- _initialize
- _scheduledDestroy
- addObserver
- advanceReadiness
- beginPropertyChanges
- buildContainer
- cacheFor
- create
- createWithMixins
- decrementProperty
- defaultRouter
- deferReadiness
- destroy
- didBecomeReady
- eachComputedProperty
- endPropertyChanges
- extend
- get
- getProperties
- getWithDefault
- hasObserverFor
- incrementProperty
- init
- initialize
- inject
- metaForProperty
- notifyPropertyChange
- propertyDidChange
- propertyWillChange
- register
- removeObserver
- reopen
- reopenClass
- reset
- resolverFor
- runInitializers
- scheduleInitialize
- set
- setProperties
- setupEventDispatcher
- toString
- toggleProperty
- willDestroy
Properties
- concatenatedProperties
- customEvents
- eventDispatcher
- isDestroyed
- isDestroying
- resolver
- rootElement
- router
Events
_initialize
private
_scheduledDestroy
private
addObserver
(key, target, method)
Ember.Object
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.
Parameters:
- key String
- The key to observer
- target Object
- The target object to invoke
- method String|Function
- The method to invoke.
Returns:
- Ember.Object
- self
advanceReadiness
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.
beginPropertyChanges
Ember.Observable
Begins a grouping of property changes.
You can use this method to group property changes so that notifications
will not be sent until the changes are finished. If you plan to make a
large number of changes to an object at one time, you should call this
method at the beginning of the changes to begin deferring change
notifications. When you are done making changes, call
endPropertyChanges()
to deliver the deferred change notifications and end
deferring.
Returns:
buildContainer
(namespace)
Ember.Container
private
static
Parameters:
- namespace Ember.Application
- the application to build the container for.
Returns:
- Ember.Container
- the built container
cacheFor
(keyName)
Object
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.
Parameters:
- keyName String
Returns:
- Object
- The cached value of the computed property, if any
create
(arguments)
static
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
or use the createWithMixins
shorthand.
Parameters:
- arguments
createWithMixins
(arguments)
static
Equivalent to doing extend(arguments).create()
.
If possible use the normal create
method instead.
Parameters:
- arguments
decrementProperty
(keyName, decrement)
Number
Set the value of a property to the current value minus some amount.
1 2 |
player.decrementProperty('lives'); orc.decrementProperty('health', 5); |
Parameters:
- 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
deferReadiness
Use this to defer readiness until some condition is true.
Example:
1 2 3 4 5 6 7 |
App = Ember.Application.create(); App.deferReadiness(); jQuery.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
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.
Returns:
- Ember.Object
- receiver
didBecomeReady
private
eachComputedProperty
(callback, binding)
Iterate over each computed property for the class, passing its name
and any associated metadata (see metaForProperty
) to the callback.
Parameters:
- callback Function
- binding Object
endPropertyChanges
Ember.Observable
Ends a grouping of property changes.
You can use this method to group property changes so that notifications
will not be sent until the changes are finished. If you plan to make a
large number of changes to an object at one time, you should call
beginPropertyChanges()
at the beginning of the changes to defer change
notifications. When you are done making changes, call this method to
deliver the deferred change notifications and end deferring.
Returns:
extend
(mixins, arguments)
static
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 Ember.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 = Ember.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()
.
Parameters:
- mixins Ember.Mixin
- One or more Ember.Mixin classes
- arguments Object
- Object containing values to use within the new class
get
(keyName)
Object
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.
Parameters:
- keyName String
- The property to retrieve
Returns:
- Object
- The property value or undefined.
getProperties
(list)
Hash
To get multiple properties at once, call getProperties
with a list of strings or an array:
1 |
record.getProperties('firstName', 'lastName', 'zipCode'); // { firstName: 'John', lastName: 'Doe', zipCode: '10011' } |
is equivalent to:
1 |
record.getProperties(['firstName', 'lastName', 'zipCode']); // { firstName: 'John', lastName: 'Doe', zipCode: '10011' } |
Parameters:
- list String...|Array
- of keys to get
Returns:
- Hash
getWithDefault
(keyName, defaultValue)
Object
Retrieves the value of a property, or a default value in the case that the
property returns undefined
.
1 |
person.getWithDefault('lastName', 'Doe'); |
Parameters:
- 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.
hasObserverFor
(key)
Boolean
Returns true
if the object currently has observers registered for a
particular key. You can use this method to potentially defer performing
an expensive action until someone begins observing a particular property
on the object.
Parameters:
- key String
- Key to check
Returns:
- Boolean
incrementProperty
(keyName, increment)
Number
Set the value of a property to the current value plus some amount.
1 2 |
person.incrementProperty('age'); team.incrementProperty('score', 2); |
Parameters:
- 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
init
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
or
Ember.ArrayController
, be sure to call this._super()
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.
initialize
deprecated
private
inject
(factoryNameOrType, property, injectionName)
defines an injection or typeInjection
Example:
1 2 3 |
App.inject(<full_name or type>, <property name>, <full_name>) App.inject('model:user', 'email', 'model:email') App.inject('model', 'source', 'source:main') |
metaForProperty
(key)
In some cases, you may want to annotate computed properties with additional metadata about how they function or what values they operate on. For example, computed property functions may close over variables that are then no longer available for introspection.
You can pass a hash of these values to a computed property like this:
1 2 3 4 |
person: function() { var personId = this.get('personId'); return App.Person.create({ id: personId }); }.property().meta({ type: App.Person }) |
Once you've done this, you can retrieve the values saved to the computed property from your class like this:
1 |
MyClass.metaForProperty('person');
|
This will return the original hash that was passed to meta()
.
Parameters:
- key String
- property name
notifyPropertyChange
(keyName)
Ember.Observable
Convenience method to call propertyWillChange
and propertyDidChange
in
succession.
Parameters:
- keyName String
- The property key to be notified about.
Returns:
propertyDidChange
(keyName)
Ember.Observable
Notify the observer system that a property has just changed.
Sometimes you need to change a value directly or indirectly without
actually calling get()
or set()
on it. In this case, you can use this
method and propertyWillChange()
instead. Calling these two methods
together will notify all observers that the property has potentially
changed value.
Note that you must always call propertyWillChange
and propertyDidChange
as a pair. If you do not, it may get the property change groups out of
order and cause notifications to be delivered more often than you would
like.
Parameters:
- keyName String
- The property key that has just changed.
Returns:
propertyWillChange
(keyName)
Ember.Observable
Notify the observer system that a property is about to change.
Sometimes you need to change a value directly or indirectly without
actually calling get()
or set()
on it. In this case, you can use this
method and propertyDidChange()
instead. Calling these two methods
together will notify all observers that the property has potentially
changed value.
Note that you must always call propertyWillChange
and propertyDidChange
as a pair. If you do not, it may get the property change groups out of
order and cause notifications to be delivered more often than you would
like.
Parameters:
- keyName String
- The property key that is about to change.
Returns:
register
(fullName, factory, options)
registers a factory for later injection
Example:
1 2 3 4 5 6 7 8 9 10 11 |
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}); |
removeObserver
(key, target, method)
Ember.Observable
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.
Parameters:
- key String
- The key to observer
- target Object
- The target object to invoke
- method String|Function
- The method to invoke.
Returns:
- Ember.Observable
- receiver
reopen
Augments a constructor's prototype with additional
properties and functions:
javascript
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
Augments a constructor's own properties and functions:
1 2 3 4 5 6 7 8 9 10 11 |
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
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 20 |
var App; Ember.run(function() { App = Ember.Application.create(); }); module("acceptance test", { setup: function() { App.reset(); } }); test("first test", function() { // App is freshly reset }); test("first 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 |
var App; Ember.run(function() { App = Ember.Application.create(); }); module("acceptance test", { setup: function() { Ember.run(function() { App.reset(); App.deferReadiness(); }); } }); test("first test", function() { ok(true, 'something before app is initialized'); Ember.run(function() { App.advanceReadiness(); }); ok(true, 'something after app is initialized'); }); |
resolverFor
(namespace)
*
private
Parameters:
- namespace Ember.Namespace
- the namespace to look for classes
Returns:
- *
- the resolved value for a given lookup
runInitializers
private
scheduleInitialize
private
set
(keyName, value)
Ember.Observable
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.
Chaining
In addition to property changes, set()
returns the value of the object
itself so you can do chaining like this:
1 |
record.set('firstName', 'Charles').set('lastName', 'Jolley'); |
Parameters:
- keyName String
- The property to set
- value Object
- The value to set or `null`.
Returns:
setProperties
(hash)
Ember.Observable
To set multiple properties at once, call setProperties
with a Hash:
1 |
record.setProperties({ firstName: 'Charles', lastName: 'Jolley' }); |
Parameters:
- hash Hash
- the hash of keys and values to set
Returns:
setupEventDispatcher
private
toString
String
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>" |
Returns:
- String
- string representation
toggleProperty
(keyName)
Object
Set the value of a boolean property to the opposite of it's current value.
1 |
starship.toggleProperty('warpDriveEngaged');
|
Parameters:
- keyName String
- The name of the property to toggle
Returns:
- Object
- The new property value
willDestroy
Override to implement teardown.
concatenatedProperties
Array
Defines the properties that will be concatenated from the superclass (instead of overridden).
By default, when you extend an Ember class a property defined in
the subclass overrides a property with the same name that is defined
in the superclass. However, there are some cases where it is preferable
to build up a property's value by combining the superclass' property
value with the subclass' value. An example of this in use within Ember
is the classNames
property of Ember.View
.
Here is some sample code showing the difference between a concatenated property and a normal one:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
App.BarView = Ember.View.extend({ someNonConcatenatedProperty: ['bar'], classNames: ['bar'] }); App.FooBarView = App.BarView.extend({ someNonConcatenatedProperty: ['foo'], classNames: ['foo'], }); var fooBarView = App.FooBarView.create(); fooBarView.get('someNonConcatenatedProperty'); // ['foo'] fooBarView.get('classNames'); // ['ember-view', 'bar', 'foo'] |
This behavior extends to object creation as well. Continuing the above example:
1 2 3 4 5 6 |
var view = App.FooBarView.create({ someNonConcatenatedProperty: ['baz'], classNames: ['baz'] }) view.get('someNonConcatenatedProperty'); // ['baz'] view.get('classNames'); // ['ember-view', 'bar', 'foo', 'baz'] |
Adding a single property that is not an array will just add it in the array:
1 2 3 4 |
var view = App.FooBarView.create({ classNames: 'baz' }) view.get('classNames'); // ['ember-view', 'bar', 'foo', 'baz'] |
Using the concatenatedProperties
property, we can tell to Ember that mix
the content of the properties.
In Ember.View
the classNameBindings
and attributeBindings
properties
are also concatenated, in addition to classNames
.
This feature is available for you to use throughout the Ember object model, although typical app developers are likely to use it infrequently. Since it changes expectations about behavior of properties, you should properly document its usage in each individual concatenated property (to not mislead your users to think they can override the property in a subclass).
Default: null
customEvents
Object
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 mousedown
and
keyup
, and delegates them to your application's Ember.View
instances.
If you would like additional bubbling events to be delegated to your
views, set your Ember.Application
's customEvents
property
to a hash containing the DOM event name as the key and the
corresponding view method name as the value. For example:
1 2 3 4 5 6 |
App = Ember.Application.create({ customEvents: { // add support for the paste event 'paste: "paste" } }); |
Default: null
eventDispatcher
Ember.EventDispatcher
The Ember.EventDispatcher
responsible for delegating events to this
application's views.
The event dispatcher is created by the application at initialization time
and sets up event listeners on the DOM element described by the
application's rootElement
property.
See the documentation for Ember.EventDispatcher
for more information.
Default: null
isDestroyed
Destroyed object property flag.
if this property is true
the observers and bindings were already
removed by the effect of calling the destroy()
method.
Default: false
isDestroying
Destruction scheduled flag. The destroy()
method has been called.
The object stays intact until the end of the run loop at which point
the isDestroyed
flag is set.
Default: false
resolver
Set this to provide an alternate class to Ember.DefaultResolver
rootElement
DOMElement
The root DOM element of the Application. This can be specified as an element or a jQuery-compatible selector string.
This is the element that will be passed to the Application's,
eventDispatcher
, which sets up the listeners for event delegation. Every
view in your application should be a child of the element you specify here.
Default: 'body'
ready
Called when the Application has become ready. The call will be delayed until the DOM has become ready.