From 7f04eeab780fff5de85f7b7256e38bf70f14c386 Mon Sep 17 00:00:00 2001 From: Derick Bailey Date: Wed, 22 Aug 2012 21:18:23 -0500 Subject: [PATCH] minor doc corrections and a link to a wiki page for the event binder --- docs/marionette.application.md | 4 ++-- docs/marionette.eventbinder.md | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/marionette.application.md b/docs/marionette.application.md index d25a961..2334325 100644 --- a/docs/marionette.application.md +++ b/docs/marionette.application.md @@ -62,11 +62,11 @@ The events that are currently triggered, are: * **"start"**: fires after all initializers and after the initializer events ```js -MyApp.bind("initialize:before", function(options){ +MyApp.on("initialize:before", function(options){ options.moreData = "Yo dawg, I heard you like options so I put some options in your options!" }); -MyApp.bind("initialize:after", function(options){ +MyApp.on("initialize:after", function(options){ if (Backbone.history){ Backbone.history.start(); } diff --git a/docs/marionette.eventbinder.md b/docs/marionette.eventbinder.md index 1a76782..a7f1867 100644 --- a/docs/marionette.eventbinder.md +++ b/docs/marionette.eventbinder.md @@ -51,4 +51,6 @@ binder.unbindAll(); This even works with in-line callback functions. +## When To Use EventBinder vs `on` Handlers +See the wiki: [When to use the EventBinder](https://github.com/derickbailey/backbone.marionette/wiki/When-to-use-the-EventBinder)