Marionette has a base Marionette.View
type that other views extend from.
This base view provides some common and core functionality for
other views to take advantage of.
Note: The Marionette.View
type is not intended to be
used directly. It exists as a base view for other view types
to be extended from, and to provide a common location for
behaviors that are shared across all views.
Views can define a set of triggers
as a hash, which will
convert a DOM event in to a view.trigger
event.
The left side of the hash is a standard Backbone.View DOM event configuration, while the right side of the hash is the view event that you want to trigger from the view.
MyView = Backbone.Marionette.ItemView.extend({
// ...
triggers: {
"click .do-something": "something:do:it"
}
});
view = new MyView();
view.render();
view.on("something:do:it", function(){
alert("I DID IT!");
});
// "click" the 'do-something' DOM element to
// demonstrate the DOM event conversion
view.$(".do-something").trigger("click");
The result of this is an alert box that says, "I DID IT!"
You can also specify the triggers
as a function that
returns a hash of trigger configurations
Backbone.Marionette.CompositeView.extend({
triggers: function(){
return {
"click .that-thing": "that:i:sent:you"
};
}
});
Triggers work with all View types that extend from the base Marionette.View.
The serializeData
method will serialize a view's model or
collection - with precedence given to collections. That is,
if you have both a collection and a model in a view, calling
the serializeData
method will return the serialized
collection.
There are times when a view's template needs to have some logic in it, and the view engine itself will not provide an easy way to accomplish this. For example, Underscore templates do not provide a helper method mechanism while Handlebars templates do.
A templateHelpers
attribute can be applied to any View object
that uses the serializeData
method - including ItemViews,
Layouts and CompositeViews. When this attribute is present,
it's contents will be mixed in to the data object that comes
back from the serializeData
method for you. This will
allow you to create helper methods that can be called from
within your templates.
There may be some cases where you need to change the template that is
used for a view, based on some simple logic such as the value of a
specific attribute in the view's model. To do this, you can provide
a getTemplate
function on your views and use this to return the
template that you need.
MyView = Backbone.Marionette.ItemView.extend({
getTemplate: function(){
if (this.model.get("foo")){
return "#some-template";
} else {
return "#a-different-template";
}
}
});
This applies to all view types.
<script id="my-template" type="text/html"></script>
MyView = Backbone.Marionette.ItemView.extend({
template: "#my-template",
templateHelpers: {
showMessage: function(){
return this.name + " is the coolest!"
}
}
});
model = new Backbone.Model({name: "Backbone.Marionette"});
view = new MyView();
view.render(); //=> "I think that Backbone.Marionette is the coolest!";
In order to access data from within the helper methods, you
need to prefix the data you need with this
. Doing that will
give you all of the methods and attributes of the serialized
data object, including the other helper methods.
templateHelpers: {
something: function(){
return "Do stuff with " + this.name + " because it's awesome.";
}
}
templateHelpers
You can specify an object literal (as shown above), a reference
to an object literal, or a function as the templateHelpers
.
If you specify a function, the function will be invoked with the current view instance as the context of the function. The function must return an object that can be mixed in to the data for the view.
Backbone.Marionette.ItemView.extend({
templateHelpers: function(){
return {
foo: function(){ /* ... */ }
}
}
});