Ember.TextArea Class packages/ember-views/lib/views/text_area.js:8

Given a property name, returns a dasherized version of that property name if the property evaluates to a non-falsy value.

For example, if the view has property isUrgent that evaluates to true, passing isUrgent to this method will return "is-urgent".

If a value that affects template rendering changes, the view should be re-rendered to reflect the new value.

When the view's isVisible property changes, toggle the visibility element of the actual DOM element.

Returns a hash of property names and container names that injected properties will lookup on the container lazily.

Provides lookup-time type validation for injected properties.

Registers the view in the view registry, keyed on the view's elementId. This is used by the EventDispatcher to locate the view in response to events.

This method should only be called once the view has been inserted into the DOM.

Invoked by the run loop to actually destroy the object. This is scheduled for execution by the destroy method.

Removes the view from the view registry. This should be called when the view is removed from DOM.

Appends the view's element to the document body. If the view does not have an HTML representation yet the element will be generated automatically.

If your application uses the rootElement property, you must append the view within that element. Rendering views outside of the rootElement is not supported.

Note that this method just schedules the view to be appended; the DOM element will not be appended to the document body until all bindings have finished synchronizing.

Appends the view's element to the specified parent element.

If the view does not have an HTML representation yet, createElement() will be called automatically.

Note that this method just schedules the view to be appended; the DOM element will not be appended to the given element until all bindings have finished synchronizing.

This is not typically a function that you will need to call directly when building your application. You might consider using Ember.ContainerView instead. If you do need to use appendTo, be sure that the target element you are providing is associated with an Ember.Application and does not have an ancestor element that is associated with an Ember view.

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.

Allows you to specify a controller action to invoke when the escape button is pressed. To use this method, give your field an escape-press attribute. The value of that attribute should be the name of the action in your controller that you wish to invoke.

For an example on how to use the escape-press attribute, please reference the example near the top of this file.

Instantiates a view to be added to the childViews array during view initialization. You generally will not call this method directly unless you are overriding createChildViews(). Note that this method will automatically configure the correct settings on the new view instance to act as a child of the parent.

Creates a DOM representation of the view and all of its child views by recursively calling the render() method. Once the element is created, it sets the element property of the view to the rendered element.

After the element has been inserted into the DOM, didInsertElement will be called on this view and all of its child views.

You must call destroy on a view to destroy the view (and all of its child views). This will remove the view from any parent node, then make sure that the DOM element managed by the view can be released by the memory manager.

Destroys any existing element along with the element for any child views as well. If the view does not currently have a element, then this method will do nothing.

If you implement willDestroyElement() on your view, then this method will be invoked on your view before your element is destroyed to give you a chance to clean up any event handlers, etc.

If you write a willDestroyElement() handler, you can assume that your didInsertElement() handler was called earlier for the same element.

You should not call or override this method yourself, but you may want to implement the above callbacks.

Iterate over each computed property for the class, passing its name and any associated metadata (see metaForProperty) to the callback.

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.

Attempts to discover the element in the parent element. The default implementation looks for an element with an ID of elementId (or the view's guid if elementId is null). You can override this method to provide your own form of lookup. For example, if you want to discover your element using a CSS class name instead of an ID.

Allows you to specify a controller action to invoke when a field receives focus. To use this method, give your field a focus-in attribute. The value of that attribute should be the name of the action in your controller that you wish to invoke.

For an example on how to use the focus-in attribute, please reference the example near the top of this file.

Allows you to specify a controller action to invoke when a field loses focus. To use this method, give your field a focus-out attribute. The value of that attribute should be the name of the action in your controller that you wish to invoke.

For an example on how to use the focus-out attribute, please reference the example near the top of this file.

Handle events from Ember.EventDispatcher

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.

Setup a view, but do not finish waking it up.

• configure childViews
• register the view with the global views hash, which is used for event dispatch

Allows you to specify a controller action to invoke when either the enter key is pressed or, in the case of the field being a textarea, when a newline is inserted. To use this method, give your field an insert-newline attribute. The value of that attribute should be the name of the action in your controller that you wish to invoke.

For an example on how to use the insert-newline attribute, please reference the example near the top of this file.

Allows you to specify a controller action to invoke when a key-down event is fired. To use this method, give your field a key-down attribute. The value of that attribute should be the name of the action in your controller that you wish to invoke.

For an example on how to use the key-down attribute, please reference the example near the top of this file.

Allows you to specify a controller action to invoke when a key is pressed. To use this method, give your field a key-press attribute. The value of that attribute should be the name of the action in your controller you that wish to invoke.

For an example on how to use the key-press attribute, please reference the example near the top of this file.

Allows you to specify a controller action to invoke when a key-up event is fired. To use this method, give your field a key-up attribute. The value of that attribute should be the name of the action in your controller that you wish to invoke.

For an example on how to use the key-up attribute, please reference the example near the top of this file.

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().

Return the nearest ancestor that is an instance of the provided class or mixin.

Return the nearest ancestor that has a given property.

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.

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.

Removes the view's element from the element to which it is attached.

Removes all children from the parentView.

Removes the child view from the parent view.

Removes the view from its parentView, if one is found. Otherwise does nothing.

Called on your view when it should push strings of HTML into a Ember.RenderBuffer. Most users will want to override the template or templateName properties instead of this method.

By default, Ember.View will look for a function in the template property and invoke it with the value of context. The value of context will be the view's controller unless you override it.

Replaces the content of the specified parent element with this view's element. If the view does not have an HTML representation yet, the element will be generated automatically.

Note that this method just schedules the view to be appended; the DOM element will not be appended to the given element until all bindings have finished synchronizing

Override the default event firing from Ember.Evented to also call methods with the given name.

Send an action with an actionContext to a target. The action, actionContext and target will be retrieved from properties of the object. For example:

1
2
3
4
5
6
7
8
9

App.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {
  target: Ember.computed.alias('controller'),
  action: 'save',
  actionContext: Ember.computed.alias('context'),
  click: function() {
    this.triggerAction(); // Sends the `save` action, along with the current context
                          // to the current controller
  }
});

The target, action, and actionContext can be provided as properties of an optional object argument to triggerAction as well.

1
2
3
4
5
6
7
8
9
10

App.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {
  click: function() {
    this.triggerAction({
      action: 'save',
      target: this.get('controller'),
      actionContext: this.get('context')
    }); // Sends the `save` action, along with the current context
        // to the current controller
  }
});

The actionContext defaults to the object you are mixing TargetActionSupport into. But target and action must be specified either as properties or with the argument to triggerAction, or a combination:

1
2
3
4
5
6
7
8
9

App.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {
  target: Ember.computed.alias('controller'),
  click: function() {
    this.triggerAction({
      action: 'save'
    }); // Sends the `save` action, along with a reference to `this`,
        // to the current controller
  }
});