ModuloM · March 26, 2013 16:42 · Mar 18, 2013 · Mar 17, 2013 · Mar 17, 2013 · Mar 17, 2013
diff --git a/mediatorExample.md b/mediatorExample.md
@@ -1,4 +1,4 @@
-Using the Mediator pattern is an effective way to avoid tightly coupling your views. In the latest version of Backbone, the `Backbone` object itself can be used as a mediator without the need of a seperate helper.
+The Mediator pattern enables communication (mediation) between views using a mediator object.In the latest version of Backbone, the `Backbone` object itself can be used as a mediator without the need of a seperate helper.
 
 In the following example, `triggerSomething` in our `ToolbarView` uses the global event-bus on the `Backbone` object to broadcast an application wide event `somethingHappened` with data.
 

diff --git a/mediatorExample.md b/mediatorExample.md
@@ -19,7 +19,7 @@ var ToolbarView = Backbone.View.extend({
 });
 ```
 
-In our second view `TableView`, we subscribe to the global `somethingHappened` event in our view initialization using `Backbone.on()`, executing some behavior whenever we are notified of a change. We are able to similarly unsubscribe in our view destruction using `Backbone.off()`:
+In `TableView`, we then subscribe to the global `somethingHappened` event in our view initialization using `Backbone.on()`, executing some behavior whenever we are notified of a change. We are able to similarly unsubscribe in our view destruction using `Backbone.off()`:
 
 ```javascript
 // Second view

diff --git a/mediatorExample.md b/mediatorExample.md
@@ -1,4 +1,4 @@
-Using the Mediator pattern is an effective way to avoid tightly coupling your views. In the latest version of Backbone, the `Backbone` object itself can be used as a mediator without the need for any additional code.
+Using the Mediator pattern is an effective way to avoid tightly coupling your views. In the latest version of Backbone, the `Backbone` object itself can be used as a mediator without the need of a seperate helper.
 
 In the following example, `triggerSomething` in our `ToolbarView` uses the global event-bus on the `Backbone` object to broadcast an application wide event `somethingHappened` with data.
 

diff --git a/mediatorExample.md b/mediatorExample.md
@@ -1,4 +1,4 @@
-Using the Mediator pattern is a good way to avoid tightly coupling your views. In the latest version of Backbone, the `Backbone` object itself can be used as a mediator without the need for any additional code.
+Using the Mediator pattern is an effective way to avoid tightly coupling your views. In the latest version of Backbone, the `Backbone` object itself can be used as a mediator without the need for any additional code.
 
 In the following example, `triggerSomething` in our `ToolbarView` uses the global event-bus on the `Backbone` object to broadcast an application wide event `somethingHappened` with data.
 

diff --git a/mediatorExample.md b/mediatorExample.md
@@ -19,11 +19,11 @@ var ToolbarView = Backbone.View.extend({
 });
 ```
 
-In our second view, we subscribe to the global `somethingHappened` event in our view initialization using `Backbone.on()`, executing some behavior whenever we are notified of a change. We are able to similarly unsubscribe in our view destruction using `Backbone.off()`:
+In our second view `TableView`, we subscribe to the global `somethingHappened` event in our view initialization using `Backbone.on()`, executing some behavior whenever we are notified of a change. We are able to similarly unsubscribe in our view destruction using `Backbone.off()`:
 
 ```javascript
 // Second view
-var tableView = Backbone.View.extend({
+var TableView = Backbone.View.extend({
 
     initialize: function () {
         Backbone.on('somethingHappened', onSomething);

diff --git a/mediatorExample.md b/mediatorExample.md
@@ -5,7 +5,6 @@ In the following example, `triggerSomething` in our `ToolbarView` uses the globa
 ```javascript
 // First view
 var ToolbarView = Backbone.View.extend({
-
   className: ".toolbar",
   events: {
     "click .button":   "triggerSomething"
@@ -20,7 +19,7 @@ var ToolbarView = Backbone.View.extend({
 });
 ```
 
-In our second view, we subscribe to the global `somethingHappened` event in our view initialization using `Backbone.on()`, executing some behavior whenever we are notified of a change. We are able to similarly unsubscribe in our view destruction using `
+In our second view, we subscribe to the global `somethingHappened` event in our view initialization using `Backbone.on()`, executing some behavior whenever we are notified of a change. We are able to similarly unsubscribe in our view destruction using `Backbone.off()`:
 
 ```javascript
 // Second view

diff --git a/mediatorExample.js → mediatorExample.md b/mediatorExample.js → mediatorExample.md
diff --git a/mediatorExample.js b/mediatorExample.js
@@ -0,0 +1,48 @@
+Using the Mediator pattern is a good way to avoid tightly coupling your views. In the latest version of Backbone, the `Backbone` object itself can be used as a mediator without the need for any additional code.
+
+In the following example, `triggerSomething` in our `ToolbarView` uses the global event-bus on the `Backbone` object to broadcast an application wide event `somethingHappened` with data.
+
+```javascript
+// First view
+var ToolbarView = Backbone.View.extend({
+
+  className: ".toolbar",
+  events: {
+    "click .button":   "triggerSomething"
+  },
+  
+  triggerSomething: function(){
+    Backbone.trigger('somethingHappened', { id: 2 });  
+  },
+  render: function() {
+    ...
+  }
+});
+```
+
+In our second view, we subscribe to the global `somethingHappened` event in our view initialization using `Backbone.on()`, executing some behavior whenever we are notified of a change. We are able to similarly unsubscribe in our view destruction using `
+
+```javascript
+// Second view
+var tableView = Backbone.View.extend({
+
+    initialize: function () {
+        Backbone.on('somethingHappened', onSomething);
+    },
+
+    render: function(){
+      // ...  
+    },
+    destroy: function () {
+        Backbone.off('somethingHappened', onSomething);
+    },
+
+    // Action when something happens.
+    onSomething: function (data) {
+        console.log('Received:' + data.id);
+    }
+});
+
+```
+
+The more recent `listenTo` method may also be used for the same purpose.
No results found