The controller defines the behavior of the component. A controller is defined by a JavaScript class, using prototypical inheritance.

ANCHORController definition

Controller = function() {}

  • Controller The prototypical function for defining a component's behavior

Controller.prototype.init = function(ChildModel) {}

  • init The function called upon a component's instanciation. Data can be initialized on the component's scoped model. Note that the DOM is generally not available when init is called.

Controller.prototype.create = function(ChildModel, Dom) {}

  • create (optional) The function called on the client when a component is loaded and ready in the DOM. = 'name'

  • name The name will associate the component with a view. Controller.prototype.view = 'path/to/view

Controller.prototype.view = 'view'

  • view (optional) The relative path to a template file to load. If the view file is named index.html and in the same directory as the controller, the directory __dirname can be specified = 'path/to/style'

  • style (optional) The relative path to a style file to load. If the view file is named index.css and in the same directory as the controller, the directory __dirname can be specified

The following shows an example of implementing the controller class for a component.

MyComponent = function() {} = 'my-sweet-component';
MyComponent.prototype.view = __dirname; = __dirname;

MyComponent.prototype.init = function(model) {
  // data initialization
  model.setNull('foo', 'bar');
MyComponent.prototype.create = function(model) {
  // DOM related initialization
  var bars = this.chart.querySelectorAll('.bars')
} = function(evt) {
  // view function

ANCHORView definition

A component's view is typically defined in it's own file as such:

  <p> arbitrary html content </p>
  <div as="chart">
    <span class="bars" on-click="select($event)">

It is possible to associate a controller with any view as long as you follow the namespace rules.

ANCHORView functions

Functions defined on the component's prototype will be available in the scope of the component's view, as demonstrated by the select function in the above example. See the controller property lookup documentation.

ANCHORComponent usage

// or if you haven't defined the name in the prototype
// you can associate the controller with an arbitrary view
app.component('namespace:name', MyComponent);
<view is="my-sweet-component" foo="{{}}"></view>
Edit on GitHub