From 3cbd7909f1415b3512b69e41405bcd97ebf78533 Mon Sep 17 00:00:00 2001 From: Jeremy Ashkenas Date: Wed, 11 Jan 2012 15:46:45 -0500 Subject: [PATCH] clarifying paragraph for #843 --- index.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index b3db0708..de304f73 100644 --- a/index.html +++ b/index.html @@ -411,8 +411,9 @@ Models, which can be created, validated, destroyed, and saved to the server. Whenever a UI action causes an attribute of a model to change, the model triggers a "change" event; all - the Views that display the model's data are notified of the - event, causing them to re-render. You don't have to write the glue + the Views that display the model's state can be notified of the + change, so that they are able to respond accordingly, re-rendering themselves with + the new information. In a finished Backbone app, you don't have to write the glue code that looks into the DOM to find an element with a specific id, and update the HTML manually — when the model changes, the views simply update themselves.