PageRenderTime 99ms CodeModel.GetById 12ms RepoModel.GetById 1ms app.codeStats 1ms

/bower_components/backbone/index.html

https://github.com/robertd/benm
HTML | 4544 lines | 3989 code | 555 blank | 0 comment | 0 complexity | 44a43547d1d83ee3ef1618de22d972bc MD5 | raw file
    

  1. <!DOCTYPE HTML>
    2. 

  2. <html>
    3. 

  3. <head>
    4. 

  4.   <meta http-equiv="content-type" content="text/html;charset=UTF-8" />
    5. 

  5.   <meta http-equiv="X-UA-Compatible" content="chrome=1" />
    6. 

  6.   <meta name="viewport" content="width=device-width">
    7. 

  7.   <link rel="canonical" href="http://backbonejs.org" />
    8. 

  8.   <link rel="icon" href="docs/images/favicon.ico" />
    9. 

  9.   <title>Backbone.js</title>
    10. 

  10.   <style>
    11. 

  11.     body {
    12. 

  12.       font-size: 14px;
    13. 

  13.       line-height: 22px;
    14. 

  14.       font-family: Helvetica Neue, Helvetica, Arial;
    15. 

  15.       background: #f4f4f4 url(docs/images/background.png);
    16. 

  16.     }
    17. 

  17.     .interface {
    18. 

  18.       font-family: "Lucida Grande", "Lucida Sans Unicode", Helvetica, Arial, sans-serif !important;
    19. 

  19.     }
    20. 

  20.     div#sidebar {
    21. 

  21.       background: #fff;
    22. 

  22.       position: fixed;
    23. 

  23.       z-index: 10;
    24. 

  24.       top: 0; left: 0; bottom: 0;
    25. 

  25.       width: 200px;
    26. 

  26.       overflow-y: auto;
    27. 

  27.       overflow-x: hidden;
    28. 

  28.       -webkit-overflow-scrolling: touch;
    29. 

  29.       padding: 15px 0 30px 30px;
    30. 

  30.       border-right: 1px solid #bbb;
    31. 

  31.       box-shadow: 0 0 20px #ccc; -webkit-box-shadow: 0 0 20px #ccc; -moz-box-shadow: 0 0 20px #ccc;
    32. 

  32.     }
    33. 

  33.       a.toc_title, a.toc_title:visited {
    34. 

  34.         display: block;
    35. 

  35.         color: black;
    36. 

  36.         font-weight: bold;
    37. 

  37.         margin-top: 15px;
    38. 

  38.       }
    39. 

  39.         a.toc_title:hover {
    40. 

  40.           text-decoration: underline;
    41. 

  41.         }
    42. 

  42.         #sidebar .version {
    43. 

  43.           font-size: 10px;
    44. 

  44.           font-weight: normal;
    45. 

  45.         }
    46. 

  46.       ul.toc_section {
    47. 

  47.         font-size: 11px;
    48. 

  48.         line-height: 14px;
    49. 

  49.         margin: 5px 0 0 0;
    50. 

  50.         padding-left: 0px;
    51. 

  51.         list-style-type: none;
    52. 

  52.         font-family: Lucida Grande;
    53. 

  53.       }
    54. 

  54.         .toc_section li {
    55. 

  55.           cursor: pointer;
    56. 

  56.           margin: 0 0 3px 0;
    57. 

  57.         }
    58. 

  58.           .toc_section li a {
    59. 

  59.             text-decoration: none;
    60. 

  60.             color: black;
    61. 

  61.           }
    62. 

  62.             .toc_section li a:hover {
    63. 

  63.               text-decoration: underline;
    64. 

  64.             }
    65. 

  65.     div.container {
    66. 

  66.       position: relative;
    67. 

  67.       width: 550px;
    68. 

  68.       margin: 40px 0 50px 260px;
    69. 

  69.     }
    70. 

  70.     img#logo {
    71. 

  71.       width: 450px;
    72. 

  72.       height: 80px;
    73. 

  73.     }
    74. 

  74.     div.run {
    75. 

  75.       position: absolute;
    76. 

  76.       right: 15px;
    77. 

  77.       width: 26px; height: 18px;
    78. 

  78.       background: url('docs/images/arrows.png') no-repeat -26px 0;
    79. 

  79.     }
    80. 

  80.       div.run:active {
    81. 

  81.         background-position: -51px 0;
    82. 

  82.       }
    83. 

  83.     p, div.container ul {
    84. 

  84.       margin: 25px 0;
    85. 

  85.       width: 550px;
    86. 

  86.     }
    87. 

  87.       p.warning {
    88. 

  88.         font-size: 12px;
    89. 

  89.         line-height: 18px;
    90. 

  90.         font-style: italic;
    91. 

  91.       }
    92. 

  92.       div.container ul {
    93. 

  93.         list-style: circle;
    94. 

  94.         padding-left: 15px;
    95. 

  95.         font-size: 13px;
    96. 

  96.         line-height: 18px;
    97. 

  97.       }
    98. 

  98.         div.container ul li {
    99. 

  99.           margin-bottom: 10px;
    100. 

  100.         }
    101. 

  101.         div.container ul.small {
    102. 

  102.           font-size: 12px;
    103. 

  103.         }
    104. 

  104.     a, a:visited {
    105. 

  105.       color: #444;
    106. 

  106.     }
    107. 

  107.     a:active, a:hover {
    108. 

  108.       color: #000;
    109. 

  109.     }
    110. 

  110.     a.punch {
    111. 

  111.       display: inline-block;
    112. 

  112.       background: #4162a8;
    113. 

  113.       border-top: 1px solid #38538c;
    114. 

  114.       border-right: 1px solid #1f2d4d;
    115. 

  115.       border-bottom: 1px solid #151e33;
    116. 

  116.       border-left: 1px solid #1f2d4d;
    117. 

  117.       -webkit-border-radius: 4px;
    118. 

  118.       -moz-border-radius: 4px;
    119. 

  119.       -ms-border-radius: 4px;
    120. 

  120.       -o-border-radius: 4px;
    121. 

  121.       border-radius: 4px;
    122. 

  122.       -webkit-box-shadow: inset 0 1px 10px 1px #5c8bee, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    123. 

  123.       -moz-box-shadow: inset 0 1px 10px 1px #5c8bee, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    124. 

  124.       -ms-box-shadow: inset 0 1px 10px 1px #5c8bee, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    125. 

  125.       -o-box-shadow: inset 0 1px 10px 1px #5c8bee, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    126. 

  126.       box-shadow: inset 0 1px 10px 1px #5c8bee, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    127. 

  127.       color: #fff;
    128. 

  128.       font: bold 14px "helvetica neue", helvetica, arial, sans-serif;
    129. 

  129.       line-height: 1;
    130. 

  130.       margin-bottom: 15px;
    131. 

  131.       padding: 8px 0 10px 0;
    132. 

  132.       text-align: center;
    133. 

  133.       text-shadow: 0px -1px 1px #1e2d4d;
    134. 

  134.       text-decoration: none;
    135. 

  135.       width: 225px;
    136. 

  136.       -webkit-background-clip: padding-box; }
    137. 

  137.       a.punch:hover {
    138. 

  138.         -webkit-box-shadow: inset 0 0px 20px 1px #87adff, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    139. 

  139.         -moz-box-shadow: inset 0 0px 20px 1px #87adff, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    140. 

  140.         -ms-box-shadow: inset 0 0px 20px 1px #87adff, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    141. 

  141.         -o-box-shadow: inset 0 0px 20px 1px #87adff, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    142. 

  142.         box-shadow: inset 0 0px 20px 1px #87adff, 0px 1px 0 #1d2c4d, 0 6px 0px #1f3053, 0 8px 4px 1px #111111;
    143. 

  143.         cursor: pointer; }
    144. 

  144.       a.punch:active {
    145. 

  145.         -webkit-box-shadow: inset 0 1px 10px 1px #5c8bee, 0 1px 0 #1d2c4d, 0 2px 0 #1f3053, 0 4px 3px 0 #111111;
    146. 

  146.         -moz-box-shadow: inset 0 1px 10px 1px #5c8bee, 0 1px 0 #1d2c4d, 0 2px 0 #1f3053, 0 4px 3px 0 #111111;
    147. 

  147.         -ms-box-shadow: inset 0 1px 10px 1px #5c8bee, 0 1px 0 #1d2c4d, 0 2px 0 #1f3053, 0 4px 3px 0 #111111;
    148. 

  148.         -o-box-shadow: inset 0 1px 10px 1px #5c8bee, 0 1px 0 #1d2c4d, 0 2px 0 #1f3053, 0 4px 3px 0 #111111;
    149. 

  149.         box-shadow: inset 0 1px 10px 1px #5c8bee, 0 1px 0 #1d2c4d, 0 2px 0 #1f3053, 0 4px 3px 0 #111111;
    150. 

  150.         margin-top: 5px; margin-bottom: 10px }
    151. 

  151.     a img {
    152. 

  152.       border: 0;
    153. 

  153.     }
    154. 

  154.     a.travis-badge {
    155. 

  155.       display: block;
    156. 

  156.     }
    157. 

  157.     h1, h2, h3, h4, h5, h6 {
    158. 

  158.       padding-top: 20px;
    159. 

  159.     }
    160. 

  160.       h2 {
    161. 

  161.         font-size: 22px;
    162. 

  162.       }
    163. 

  163.     b.header {
    164. 

  164.       font-size: 18px;
    165. 

  165.       line-height: 35px;
    166. 

  166.     }
    167. 

  167.     span.alias {
    168. 

  168.       font-size: 14px;
    169. 

  169.       font-style: italic;
    170. 

  170.       margin-left: 20px;
    171. 

  171.     }
    172. 

  172.     table {
    173. 

  173.       margin: 15px 0 0; padding: 0;
    174. 

  174.     }
    175. 

  175.       tr, td {
    176. 

  176.         margin: 0; padding: 0;
    177. 

  177.       }
    178. 

  178.         td {
    179. 

  179.           padding: 0px 15px 5px 0;
    180. 

  180.         }
    181. 

  181.         table .rule {
    182. 

  182.           height: 1px;
    183. 

  183.           background: #ccc;
    184. 

  184.           margin: 5px 0;
    185. 

  185.         }
    186. 

  186.     code, pre, tt {
    187. 

  187.       font-family: Monaco, Consolas, "Lucida Console", monospace;
    188. 

  188.       font-size: 12px;
    189. 

  189.       line-height: 18px;
    190. 

  190.       font-style: normal;
    191. 

  191.     }
    192. 

  192.       tt {
    193. 

  193.         padding: 0px 3px;
    194. 

  194.         background: #fff;
    195. 

  195.         border: 1px solid #ddd;
    196. 

  196.         zoom: 1;
    197. 

  197.       }
    198. 

  198.       code {
    199. 

  199.         margin-left: 20px;
    200. 

  200.       }
    201. 

  201.       pre {
    202. 

  202.         font-size: 12px;
    203. 

  203.         padding: 2px 0 2px 15px;
    204. 

  204.         border: 4px solid #bbb; border-top: 0; border-bottom: 0;
    205. 

  205.         margin: 0px 0 25px;
    206. 

  206.       }
    207. 

  207.       img.example_image {
    208. 

  208.         margin: 0px auto;
    209. 

  209.       }
    210. 

  210.         img.example_retina {
    211. 

  211.           margin: 20px;
    212. 

  212.           box-shadow: 0 8px 15px rgba(0,0,0,0.4);
    213. 

  213.         }
    214. 

  214.     @media only screen and (-webkit-max-device-pixel-ratio: 1) and (max-width: 600px),
    215. 

  215.            only screen and (max--moz-device-pixel-ratio: 1) and (max-width: 600px) {
    216. 

  216.       div#sidebar {
    217. 

  217.         display: none;
    218. 

  218.       }
    219. 

  219.       img#logo {
    220. 

  220.         max-width: 450px;
    221. 

  221.         width: 100%;
    222. 

  222.         height: auto;
    223. 

  223.       }
    224. 

  224.       div.container {
    225. 

  225.         width: auto;
    226. 

  226.         margin-left: 15px;
    227. 

  227.         margin-right: 15px;
    228. 

  228.       }
    229. 

  229.         p, div.container ul {
    230. 

  230.           width: auto;
    231. 

  231.         }
    232. 

  232.     }
    233. 

  233.     @media only screen and (-webkit-min-device-pixel-ratio: 1.5) and (max-width: 640px),
    234. 

  234.           only screen and (-o-min-device-pixel-ratio: 3/2) and (max-width: 640px),
    235. 

  235.           only screen and (min-device-pixel-ratio: 1.5) and (max-width: 640px) {
    236. 

  236.       img {
    237. 

  237.         max-width: 100%;
    238. 

  238.         height: auto;
    239. 

  239.       }
    240. 

  240.       div#sidebar {
    241. 

  241.         -webkit-overflow-scrolling: initial;
    242. 

  242.         position: relative;
    243. 

  243.         width: 90%;
    244. 

  244.         height: 120px;
    245. 

  245.         left: 0;
    246. 

  246.         top: -7px;
    247. 

  247.         padding: 10px 0 10px 30px;
    248. 

  248.         border: 0;
    249. 

  249.       }
    250. 

  250.       img#logo {
    251. 

  251.         width: auto;
    252. 

  252.         height: auto;
    253. 

  253.       }
    254. 

  254.       div.container {
    255. 

  255.         margin: 0;
    256. 

  256.         width: 100%;
    257. 

  257.       }
    258. 

  258.       p, div.container ul {
    259. 

  259.         max-width: 98%;
    260. 

  260.         overflow-x: scroll;
    261. 

  261.       }
    262. 

  262.       table {
    263. 

  263.         position: relative;
    264. 

  264.       }
    265. 

  265.         tr:first-child td {
    266. 

  266.           padding-bottom: 25px;
    267. 

  267.         }
    268. 

  268.         td.text {
    269. 

  269.           line-height: 12px;
    270. 

  270.           padding: 0;
    271. 

  271.           position: absolute;
    272. 

  272.           left: 0;
    273. 

  273.           top: 48px;
    274. 

  274.         }
    275. 

  275.         tr:last-child td.text {
    276. 

  276.           top: 122px;
    277. 

  277.         }
    278. 

  278.       pre {
    279. 

  279.         overflow: scroll;
    280. 

  280.       }
    281. 

  281.     }
    282. 

  282.   </style>
    283. 

  283. </head>
    284. 

  284. <body>
    285. 

  285. 

  286.   <div id="sidebar" class="interface">
    287. 

  287. 

  288.     <a class="toc_title" href="#">
    289. 

  289.       Backbone.js <span class="version">(1.1.0)</span>
    290. 

  290.     </a>
    291. 

  291.     <ul class="toc_section">
    292. 

  292.       <li>&raquo; <a href="http://github.com/jashkenas/backbone">GitHub Repository</a></li>
    293. 

  293.       <li>&raquo; <a href="docs/backbone.html">Annotated Source</a></li>
    294. 

  294.     </ul>
    295. 

  295. 

  296.     <a class="toc_title" href="#introduction">
    297. 

  297.       Introduction
    298. 

  298.     </a>
    299. 

  299. 

  300.     <a class="toc_title" href="#upgrading">
    301. 

  301.       Upgrading
    302. 

  302.     </a>
    303. 

  303. 

  304.     <a class="toc_title" href="#Events">
    305. 

  305.       Events
    306. 

  306.     </a>
    307. 

  307.     <ul class="toc_section">
    308. 

  308.       <li>– <a href="#Events-on">on</a></li>
    309. 

  309.       <li>– <a href="#Events-off">off</a></li>
    310. 

  310.       <li>– <a href="#Events-trigger">trigger</a></li>
    311. 

  311.       <li>– <a href="#Events-once">once</a></li>
    312. 

  312.       <li>– <a href="#Events-listenTo">listenTo</a></li>
    313. 

  313.       <li>– <a href="#Events-stopListening">stopListening</a></li>
    314. 

  314.       <li>– <a href="#Events-listenToOnce">listenToOnce</a></li>
    315. 

  315.       <li>- <a href="#Events-catalog"><b>Catalog of Built-in Events</b></a></li>
    316. 

  316.     </ul>
    317. 

  317. 

  318.     <a class="toc_title" href="#Model">
    319. 

  319.       Model
    320. 

  320.     </a>
    321. 

  321.     <ul class="toc_section">
    322. 

  322.       <li>– <a href="#Model-extend">extend</a></li>
    323. 

  323.       <li>– <a href="#Model-constructor">constructor / initialize</a></li>
    324. 

  324.       <li>– <a href="#Model-get">get</a></li>
    325. 

  325.       <li>– <a href="#Model-set">set</a></li>
    326. 

  326.       <li>– <a href="#Model-escape">escape</a></li>
    327. 

  327.       <li>– <a href="#Model-has">has</a></li>
    328. 

  328.       <li>– <a href="#Model-unset">unset</a></li>
    329. 

  329.       <li>– <a href="#Model-clear">clear</a></li>
    330. 

  330.       <li>– <a href="#Model-id">id</a></li>
    331. 

  331.       <li>– <a href="#Model-idAttribute">idAttribute</a></li>
    332. 

  332.       <li>– <a href="#Model-cid">cid</a></li>
    333. 

  333.       <li>– <a href="#Model-attributes">attributes</a></li>
    334. 

  334.       <li>– <a href="#Model-changed">changed</a></li>
    335. 

  335.       <li>– <a href="#Model-defaults">defaults</a></li>
    336. 

  336.       <li>– <a href="#Model-toJSON">toJSON</a></li>
    337. 

  337.       <li>– <a href="#Model-sync">sync</a></li>
    338. 

  338.       <li>– <a href="#Model-fetch">fetch</a></li>
    339. 

  339.       <li>– <a href="#Model-save">save</a></li>
    340. 

  340.       <li>– <a href="#Model-destroy">destroy</a></li>
    341. 

  341.       <li>– <a href="#Model-Underscore-Methods"><b>Underscore Methods (6)</b></a></li>
    342. 

  342.       <li>– <a href="#Model-validate">validate</a></li>
    343. 

  343.       <li>– <a href="#Model-validationError">validationError</a></li>
    344. 

  344.       <li>– <a href="#Model-isValid">isValid</a></li>
    345. 

  345.       <li>– <a href="#Model-url">url</a></li>
    346. 

  346.       <li>– <a href="#Model-urlRoot">urlRoot</a></li>
    347. 

  347.       <li>– <a href="#Model-parse">parse</a></li>
    348. 

  348.       <li>– <a href="#Model-clone">clone</a></li>
    349. 

  349.       <li>– <a href="#Model-isNew">isNew</a></li>
    350. 

  350.       <li>– <a href="#Model-hasChanged">hasChanged</a></li>
    351. 

  351.       <li>– <a href="#Model-changedAttributes">changedAttributes</a></li>
    352. 

  352.       <li>– <a href="#Model-previous">previous</a></li>
    353. 

  353.       <li>– <a href="#Model-previousAttributes">previousAttributes</a></li>
    354. 

  354.     </ul>
    355. 

  355. 

  356.     <a class="toc_title" href="#Collection">
    357. 

  357.       Collection
    358. 

  358.     </a>
    359. 

  359.     <ul class="toc_section">
    360. 

  360.       <li>– <a href="#Collection-extend">extend</a></li>
    361. 

  361.       <li>– <a href="#Collection-model">model</a></li>
    362. 

  362.       <li>– <a href="#Collection-constructor">constructor / initialize</a></li>
    363. 

  363.       <li>– <a href="#Collection-models">models</a></li>
    364. 

  364.       <li>– <a href="#Collection-toJSON">toJSON</a></li>
    365. 

  365.       <li>– <a href="#Collection-sync">sync</a></li>
    366. 

  366.       <li>– <a href="#Collection-Underscore-Methods"><b>Underscore Methods (28)</b></a></li>
    367. 

  367.       <li>– <a href="#Collection-add">add</a></li>
    368. 

  368.       <li>– <a href="#Collection-remove">remove</a></li>
    369. 

  369.       <li>– <a href="#Collection-reset">reset</a></li>
    370. 

  370.       <li>– <a href="#Collection-set">set</a></li>
    371. 

  371.       <li>– <a href="#Collection-get">get</a></li>
    372. 

  372.       <li>– <a href="#Collection-at">at</a></li>
    373. 

  373.       <li>– <a href="#Collection-push">push</a></li>
    374. 

  374.       <li>– <a href="#Collection-pop">pop</a></li>
    375. 

  375.       <li>– <a href="#Collection-unshift">unshift</a></li>
    376. 

  376.       <li>– <a href="#Collection-shift">shift</a></li>
    377. 

  377.       <li>– <a href="#Collection-slice">slice</a></li>
    378. 

  378.       <li>– <a href="#Collection-length">length</a></li>
    379. 

  379.       <li>– <a href="#Collection-comparator">comparator</a></li>
    380. 

  380.       <li>– <a href="#Collection-sort">sort</a></li>
    381. 

  381.       <li>– <a href="#Collection-pluck">pluck</a></li>
    382. 

  382.       <li>– <a href="#Collection-where">where</a></li>
    383. 

  383.       <li>– <a href="#Collection-findWhere">findWhere</a></li>
    384. 

  384.       <li>– <a href="#Collection-url">url</a></li>
    385. 

  385.       <li>– <a href="#Collection-parse">parse</a></li>
    386. 

  386.       <li>– <a href="#Collection-clone">clone</a></li>
    387. 

  387.       <li>– <a href="#Collection-fetch">fetch</a></li>
    388. 

  388.       <li>– <a href="#Collection-create">create</a></li>
    389. 

  389.     </ul>
    390. 

  390. 

  391.     <a class="toc_title" href="#Router">
    392. 

  392.       Router
    393. 

  393.     </a>
    394. 

  394.     <ul class="toc_section">
    395. 

  395.       <li>– <a href="#Router-extend">extend</a></li>
    396. 

  396.       <li>– <a href="#Router-routes">routes</a></li>
    397. 

  397.       <li>– <a href="#Router-constructor">constructor / initialize</a></li>
    398. 

  398.       <li>– <a href="#Router-route">route</a></li>
    399. 

  399.       <li>– <a href="#Router-navigate">navigate</a></li>
    400. 

  400.     </ul>
    401. 

  401. 

  402.     <a class="toc_title" href="#History">
    403. 

  403.       History
    404. 

  404.     </a>
    405. 

  405.     <ul class="toc_section">
    406. 

  406.       <li>– <a href="#History-start">start</a></li>
    407. 

  407.     </ul>
    408. 

  408. 

  409.     <a class="toc_title" href="#Sync">
    410. 

  410.       Sync
    411. 

  411.     </a>
    412. 

  412.     <ul class="toc_section">
    413. 

  413.       <li>– <a href="#Sync">Backbone.sync</a></li>
    414. 

  414.       <li>– <a href="#Sync-ajax">Backbone.ajax</a></li>
    415. 

  415.       <li>– <a href="#Sync-emulateHTTP">Backbone.emulateHTTP</a></li>
    416. 

  416.       <li>– <a href="#Sync-emulateJSON">Backbone.emulateJSON</a></li>
    417. 

  417.     </ul>
    418. 

  418. 

  419.     <a class="toc_title" href="#View">
    420. 

  420.       View
    421. 

  421.     </a>
    422. 

  422.     <ul class="toc_section">
    423. 

  423.       <li>– <a href="#View-extend">extend</a></li>
    424. 

  424.       <li>– <a href="#View-constructor">constructor / initialize</a></li>
    425. 

  425.       <li>– <a href="#View-el">el</a></li>
    426. 

  426.       <li>– <a href="#View-$el">$el</a></li>
    427. 

  427.       <li>– <a href="#View-setElement">setElement</a></li>
    428. 

  428.       <li>– <a href="#View-attributes">attributes</a></li>
    429. 

  429.       <li>– <a href="#View-dollar">$ (jQuery)</a></li>
    430. 

  430.       <li>– <a href="#View-template">template</a></li>
    431. 

  431.       <li>– <a href="#View-render">render</a></li>
    432. 

  432.       <li>– <a href="#View-remove">remove</a></li>
    433. 

  433.       <li>– <a href="#View-delegateEvents">delegateEvents</a></li>
    434. 

  434.       <li>– <a href="#View-undelegateEvents">undelegateEvents</a></li>
    435. 

  435.     </ul>
    436. 

  436. 

  437.     <a class="toc_title" href="#Utility">
    438. 

  438.       Utility
    439. 

  439.     </a>
    440. 

  440.     <ul class="toc_section">
    441. 

  441.       <li>– <a href="#Utility-Backbone-noConflict">Backbone.noConflict</a></li>
    442. 

  442.       <li>– <a href="#Utility-Backbone-$">Backbone.$</a></li>
    443. 

  443.     </ul>
    444. 

  444. 

  445.     <a class="toc_title" href="#examples">
    446. 

  446.       Examples
    447. 

  447.     </a>
    448. 

  448.     <ul class="toc_section">
    449. 

  449.       <li>– <a href="#examples-todos">Todos</a></li>
    450. 

  450.       <li>– <a href="#examples-documentcloud">DocumentCloud</a></li>
    451. 

  451.       <li>– <a href="#examples-usa-today">USA Today</a></li>
    452. 

  452.       <li>– <a href="#examples-rdio">Rdio</a></li>
    453. 

  453.       <li>– <a href="#examples-hulu">Hulu</a></li>
    454. 

  454.       <li>– <a href="#examples-quartz">Quartz</a></li>
    455. 

  455.       <li>– <a href="#examples-gawker">Gawker Media</a></li>
    456. 

  456.       <li>– <a href="#examples-flow">Flow</a></li>
    457. 

  457.       <li>– <a href="#examples-gilt">Gilt Groupe</a></li>
    458. 

  458.       <li>– <a href="#examples-newsblur">NewsBlur</a></li>
    459. 

  459.       <li>– <a href="#examples-wordpress">WordPress.com</a></li>
    460. 

  460.       <li>– <a href="#examples-foursquare">Foursquare</a></li>
    461. 

  461.       <li>– <a href="#examples-bitbucket">Bitbucket</a></li>
    462. 

  462.       <li>– <a href="#examples-disqus">Disqus</a></li>
    463. 

  463.       <li>– <a href="#examples-khan-academy">Khan Academy</a></li>
    464. 

  464.       <li>– <a href="#examples-elife-lens">eLife Lens</a></li>
    465. 

  465.       <li>– <a href="#examples-do">Do</a></li>
    466. 

  466.       <li>– <a href="#examples-irccloud">IRCCloud</a></li>
    467. 

  467.       <li>– <a href="#examples-pitchfork">Pitchfork</a></li>
    468. 

  468.       <li>– <a href="#examples-spin">Spin</a></li>
    469. 

  469.       <li>– <a href="#examples-zocdoc">ZocDoc</a></li>
    470. 

  470.       <li>– <a href="#examples-walmart">Walmart Mobile</a></li>
    471. 

  471.       <li>– <a href="#examples-groupon">Groupon Now!</a></li>
    472. 

  472.       <li>– <a href="#examples-basecamp">Basecamp</a></li>
    473. 

  473.       <li>– <a href="#examples-slavery-footprint">Slavery Footprint</a></li>
    474. 

  474.       <li>– <a href="#examples-stripe">Stripe</a></li>
    475. 

  475.       <li>– <a href="#examples-airbnb">Airbnb</a></li>
    476. 

  476.       <li>– <a href="#examples-diaspora">Diaspora</a></li>
    477. 

  477.       <li>– <a href="#examples-soundcloud">SoundCloud Mobile</a></li>
    478. 

  478.       <li>- <a href="#examples-artsy">Art.sy</a></li>
    479. 

  479.       <li>– <a href="#examples-pandora">Pandora</a></li>
    480. 

  480.       <li>– <a href="#examples-inkling">Inkling</a></li>
    481. 

  481.       <li>– <a href="#examples-code-school">Code School</a></li>
    482. 

  482.       <li>– <a href="#examples-cloudapp">CloudApp</a></li>
    483. 

  483.       <li>– <a href="#examples-seatgeek">SeatGeek</a></li>
    484. 

  484.       <li>– <a href="#examples-easel">Easel</a></li>
    485. 

  485.       <li>- <a href="#examples-jolicloud">Jolicloud</a></li>
    486. 

  486.       <li>– <a href="#examples-syllabus">Syllabus</a></li>
    487. 

  487.       <li>– <a href="#examples-salon">Salon.io</a></li>
    488. 

  488.       <li>– <a href="#examples-tilemill">TileMill</a></li>
    489. 

  489.       <li>– <a href="#examples-blossom">Blossom</a></li>
    490. 

  490.       <li>– <a href="#examples-trello">Trello</a></li>
    491. 

  491.       <li>– <a href="#examples-tzigla">Tzigla</a></li>
    492. 

  492.     </ul>
    493. 

  493. 

  494.     <a class="toc_title" href="#faq">
    495. 

  495.       F.A.Q.
    496. 

  496.     </a>
    497. 

  497.     <ul class="toc_section">
    498. 

  498.       <li>– <a href="#FAQ-why-backbone">Why Backbone?</a></li>
    499. 

  499.       <li>– <a href="#FAQ-tim-toady">More Than One Way To Do It</a></li>
    500. 

  500.       <li>– <a href="#FAQ-nested">Nested Models &amp; Collections</a></li>
    501. 

  501.       <li>– <a href="#FAQ-bootstrap">Loading Bootstrapped Models</a></li>
    502. 

  502.       <li>– <a href="#FAQ-extending">Extending Backbone</a></li>
    503. 

  503.       <li>– <a href="#FAQ-mvc">Traditional MVC</a></li>
    504. 

  504.       <li>– <a href="#FAQ-this">Binding "this"</a></li>
    505. 

  505.       <li>– <a href="#FAQ-rails">Working with Rails</a></li>
    506. 

  506.     </ul>
    507. 

  507. 

  508.     <a class="toc_title" href="#changelog">
    509. 

  509.       Change Log
    510. 

  510.     </a>
    511. 

  511. 

  512.   </div>
    513. 

  513. 

  514.   <div class="container">
    515. 

  515. 

  516.     <p>
    517. 

  517.       <img id="logo" src="docs/images/backbone.png" alt="Backbone.js" />
    518. 

  518.     </p>
    519. 

  519. 

  520.     <p>
    521. 

  521.       Backbone.js gives structure to web applications
    522. 

  522.       by providing <b>models</b> with key-value binding and custom events,
    523. 

  523.       <b>collections</b> with a rich API of enumerable functions,
    524. 

  524.       <b>views</b> with declarative event handling, and connects it all to your
    525. 

  525.       existing API over a RESTful JSON interface.
    526. 

  526.     </p>
    527. 

  527. 

  528.     <p>
    529. 

  529.       The project is <a href="http://github.com/jashkenas/backbone/">hosted on GitHub</a>,
    530. 

  530.       and the <a href="docs/backbone.html">annotated source code</a> is available,
    531. 

  531.       as well as an online <a href="test/">test suite</a>,
    532. 

  532.       an <a href="examples/todos/index.html">example application</a>,
    533. 

  533.       a <a href="https://github.com/jashkenas/backbone/wiki/Tutorials%2C-blog-posts-and-example-sites">list of tutorials</a>
    534. 

  534.       and a <a href="#examples">long list of real-world projects</a> that use Backbone.
    535. 

  535.       Backbone is available for use under the <a href="http://github.com/jashkenas/backbone/blob/master/LICENSE">MIT software license</a>.
    536. 

  536.     </p>
    537. 

  537. 

  538.     <p>
    539. 

  539.       You can report bugs and discuss features on the
    540. 

  540.       <a href="http://github.com/jashkenas/backbone/issues">GitHub issues page</a>,
    541. 

  541.       on Freenode IRC in the <tt>#documentcloud</tt> channel, post questions to the
    542. 

  542.       <a href="https://groups.google.com/forum/#!forum/backbonejs">Google Group</a>,
    543. 

  543.       add pages to the <a href="https://github.com/jashkenas/backbone/wiki">wiki</a>
    544. 

  544.       or send tweets to <a href="http://twitter.com/documentcloud">@documentcloud</a>.
    545. 

  545.     </p>
    546. 

  546. 

  547.     <p>
    548. 

  548.       <i>
    549. 

  549.         Backbone is an open-source component of
    550. 

  550.         <a href="http://documentcloud.org/">DocumentCloud</a>.
    551. 

  551.       </i>
    552. 

  552.     </p>
    553. 

  553. 

  554.     <h2 id="downloads">
    555. 

  555.       Downloads &amp; Dependencies
    556. 

  556.       <span style="padding-left: 7px; font-size:11px; font-weight: normal;" class="interface">(Right-click, and use "Save As")</span>
    557. 

  557.     </h2>
    558. 

  558. 

  559.     <table>
    560. 

  560.       <tr>
    561. 

  561.         <td><a class="punch" href="backbone.js">Development Version (1.1.0)</a></td>
    562. 

  562.         <td class="text"><i>59kb, Full source, tons of comments</i></td>
    563. 

  563.       </tr>
    564. 

  564.       <tr>
    565. 

  565.         <td><a class="punch" href="backbone-min.js">Production Version (1.1.0)</a></td>
    566. 

  566.         <td class="text" style="line-height: 16px;">
    567. 

  567.           <i>6.4kb, Packed and gzipped</i><br />
    568. 

  568.           <small>(<a href="backbone-min.map">Source Map</a>)</small>
    569. 

  569.         </td>
    570. 

  570.       </tr>
    571. 

  571.       <tr>
    572. 

  572.         <td><a class="punch" href="https://raw.github.com/jashkenas/backbone/master/backbone.js">Edge Version (master)</a></td>
    573. 

  573.         <td>
    574. 

  574.           <i>Unreleased, use at your own risk</i>
    575. 

  575.           <a class="travis-badge" href="https://travis-ci.org/jashkenas/backbone">
    576. 

  576.             <img src="https://travis-ci.org/jashkenas/backbone.png" />
    577. 

  577.           </a>
    578. 

  578.         </td>
    579. 

  579.       </tr>
    580. 

  580.     </table>
    581. 

  581. 

  582.     <p>
    583. 

  583.       Backbone's only hard dependency is
    584. 

  584.       <b><a href="http://underscorejs.org/">Underscore.js</a></b>.
    585. 

  585.       For RESTful persistence, history support via <a href="#Router">Backbone.Router</a>
    586. 

  586.       and DOM manipulation with <a href="#View">Backbone.View</a>, include
    587. 

  587.       <b><a href="http://jquery.com">jQuery</a></b>, and
    588. 

  588.       <b><a href="https://github.com/douglascrockford/JSON-js">json2.js</a></b> for older
    589. 

  589.       Internet Explorer support.
    590. 

  590.       <i>(Mimics of the Underscore and jQuery APIs, such as
    591. 

  591.       <a href="http://lodash.com">Lo-Dash</a> and
    592. 

  592.       <a href="http://zeptojs.com">Zepto</a>, will
    593. 

  593.       also tend to work, with varying degrees of compatibility.)</i>
    594. 

  594.     </p>
    595. 

  595. 

  596.     <h2 id="introduction">Introduction</h2>
    597. 

  597. 

  598.     <p>
    599. 

  599.       When working on a web application that involves a lot of JavaScript, one
    600. 

  600.       of the first things you learn is to stop tying your data to the DOM. It's all
    601. 

  601.       too easy to create JavaScript applications that end up as tangled piles of
    602. 

  602.       jQuery selectors and callbacks, all trying frantically to keep data in
    603. 

  603.       sync between the HTML UI, your JavaScript logic, and the database on your
    604. 

  604.       server. For rich client-side applications, a more structured approach
    605. 

  605.       is often helpful.
    606. 

  606.     </p>
    607. 

  607. 

  608.     <p>
    609. 

  609.       With Backbone, you represent your data as
    610. 

  610.       <a href="#Model">Models</a>, which can be created, validated, destroyed,
    611. 

  611.       and saved to the server. Whenever a UI action causes an attribute of
    612. 

  612.       a model to change, the model triggers a <i>"change"</i> event; all
    613. 

  613.       the <a href="#View">Views</a> that display the model's state can be notified of the
    614. 

  614.       change, so that they are able to respond accordingly, re-rendering themselves with
    615. 

  615.       the new information. In a finished Backbone app, you don't have to write the glue
    616. 

  616.       code that looks into the DOM to find an element with a specific <i>id</i>,
    617. 

  617.       and update the HTML manually
    618. 

  618.       &mdash; when the model changes, the views simply update themselves.
    619. 

  619.     </p>
    620. 

  620. 

  621.     <p>
    622. 

  622.       Philosophically, Backbone is an attempt to discover the minimal set
    623. 

  623.       of data-structuring (models and collections) and user interface (views
    624. 

  624.       and URLs) primitives that are generally useful when building web applications with
    625. 

  625.       JavaScript. In an ecosystem where overarching, decides-everything-for-you
    626. 

  626.       frameworks are commonplace, and many libraries require your site to be 
    627. 

  627.       reorganized to suit their look, feel, and default behavior — Backbone should
    628. 

  628.       continue to be a tool that gives you the <i>freedom</i> to design the full
    629. 

  629.       experience of your web application.
    630. 

  630.     </p>
    631. 

  631. 

  632.     <p>
    633. 

  633.       If you're new here, and aren't yet quite sure what Backbone is for, start by
    634. 

  634.       browsing the <a href="#examples">list of Backbone-based projects</a>.
    635. 

  635.     </p>
    636. 

  636. 

  637.     <p>
    638. 

  638.       Many of the examples that follow are runnable. Click the <i>play</i> button
    639. 

  639.       to execute them.
    640. 

  640.     </p>
    641. 

  641. 

  642.     <h2 id="upgrading">Upgrading to 1.0</h2>
    643. 

  643. 

  644.     <p>
    645. 

  645.       Backbone <b>1.0</b> should be a fairly painless upgrade from the <b>0.9</b>
    646. 

  646.       series. If you're upgrading from an older version, be sure to check out the
    647. 

  647.       <a href="#changelog">change log</a>. In brief, a few of the larger breaking
    648. 

  648.       changes are:
    649. 

  649.     </p>
    650. 

  650. 

  651.     <ul>
    652. 

  652.       <li>
    653. 

  653.         If you want to smartly update the contents of a Collection,
    654. 

  654.         adding new models, removing missing ones, and merging those already present,
    655. 

  655.         you now call <a href="#Collection-set">set</a> (previously named "update"),
    656. 

  656.         a similar operation to calling <tt>set</tt> on a Model. This is now the
    657. 

  657.         default when you call <a href="#Collection-fetch">fetch</a> on a collection.
    658. 

  658.         To get the old behavior, pass <tt>{reset: true}</tt>.
    659. 

  659.       </li>
    660. 

  660.       <li>
    661. 

  661.         If you have characters in your URL segments that require URL encoding,
    662. 

  662.         Backbone will now decode them for you (normalizing the behavior
    663. 

  663.         cross-browser) before your route handlers receive them as arguments.
    664. 

  664.       </li>
    665. 

  665.       <li>
    666. 

  666.         In <b>0.9.x</b>, Backbone events gained two new methods:
    667. 

  667.         <a href="#Events-listenTo">listenTo</a> and
    668. 

  668.         <a href="#Events-stopListening">stopListening</a>, which make it easier
    669. 

  669.         to create Views that have all of their observers unbound when you
    670. 

  670.         want to <a href="#View-remove">remove</a> the view.
    671. 

  671.       </li>
    672. 

  672.       <li>
    673. 

  673.         Model validation is now only enforced by default in
    674. 

  674.         <a href="#Model-save">save</a> &mdash; not in
    675. 

  675.         <a href="#Model-set">set</a> unless the <tt>{validate:true}</tt>
    676. 

  676.         option is passed. Model validation now fires an <tt>"invalid"</tt> event instead of
    677. 

  677.         <tt>"error"</tt>.
    678. 

  678.       </li>
    679. 

  679.     </ul>
    680. 

  680. 

  681.     <h2 id="Events">Backbone.Events</h2>
    682. 

  682. 

  683.     <p>
    684. 

  684.       <b>Events</b> is a module that can be mixed in to any object, giving the
    685. 

  685.       object the ability to bind and trigger custom named events. Events do not
    686. 

  686.       have to be declared before they are bound, and may take passed arguments.
    687. 

  687.       For example:
    688. 

  688.     </p>
    689. 

  689. 

  690. <pre class="runnable">
    691. 

  691. var object = {};
    692. 

  692. 

  693. _.extend(object, Backbone.Events);
    694. 

  694. 

  695. object.on("alert", function(msg) {
    696. 

  696.   alert("Triggered " + msg);
    697. 

  697. });
    698. 

  698. 

  699. object.trigger("alert", "an event");
    700. 

  700. </pre>
    701. 

  701. 

  702.     <p>
    703. 

  703.       For example, to make a handy event dispatcher that can coordinate events
    704. 

  704.       among different areas of your application: <tt>var dispatcher = _.clone(Backbone.Events)</tt>
    705. 

  705.     </p>
    706. 

  706. 

  707.     <p id="Events-on">
    708. 

  708.       <b class="header">on</b><code>object.on(event, callback, [context])</code><span class="alias">Alias: bind</span>
    709. 

  709.       <br />
    710. 

  710.       Bind a <b>callback</b> function to an object. The callback will be invoked
    711. 

  711.       whenever the <b>event</b> is fired.
    712. 

  712.       If you have a large number of different events on a page, the convention is to use colons to
    713. 

  713.       namespace them: <tt>"poll:start"</tt>, or <tt>"change:selection"</tt>.
    714. 

  714.       The event string may also be a space-delimited list of several events...
    715. 

  715.     </p>
    716. 

  716. 

  717. <pre>
    718. 

  718. book.on("change:title change:author", ...);
    719. 

  719. </pre>
    720. 

  720. 

  721.     <p>
    722. 

  722.       To supply a <b>context</b> value for <tt>this</tt> when the callback is invoked,
    723. 

  723.       pass the optional third argument: <tt>model.on('change', this.render, this)</tt>
    724. 

  724.     </p>
    725. 

  725. 

  726.     <p>
    727. 

  727.       Callbacks bound to the special
    728. 

  728.       <tt>"all"</tt> event will be triggered when any event occurs, and are passed
    729. 

  729.       the name of the event as the first argument. For example, to proxy all events
    730. 

  730.       from one object to another:
    731. 

  731.     </p>
    732. 

  732. 

  733. <pre>
    734. 

  734. proxy.on("all", function(eventName) {
    735. 

  735.   object.trigger(eventName);
    736. 

  736. });
    737. 

  737. </pre>
    738. 

  738. 

  739.     <p>
    740. 

  740.       All Backbone event methods also support an event map syntax, as an alternative
    741. 

  741.       to positional arguments:
    742. 

  742.     </p>
    743. 

  743. 

  744. <pre>
    745. 

  745. book.on({
    746. 

  746.   "change:title": titleView.update,
    747. 

  747.   "change:author": authorPane.update,
    748. 

  748.   "destroy": bookView.remove
    749. 

  749. });
    750. 

  750. </pre>
    751. 

  751. 

  752.     <p id="Events-off">
    753. 

  753.       <b class="header">off</b><code>object.off([event], [callback], [context])</code><span class="alias">Alias: unbind</span>
    754. 

  754.       <br />
    755. 

  755.       Remove a previously-bound <b>callback</b> function from an object. If no
    756. 

  756.       <b>context</b> is specified, all of the versions of the callback with
    757. 

  757.       different contexts will be removed. If no
    758. 

  758.       callback is specified, all callbacks for the <b>event</b> will be
    759. 

  759.       removed. If no event is specified, callbacks for <i>all</i> events
    760. 

  760.       will be removed.
    761. 

  761.     </p>
    762. 

  762. 

  763. <pre>
    764. 

  764. // Removes just the `onChange` callback.
    765. 

  765. object.off("change", onChange);
    766. 

  766. 

  767. // Removes all "change" callbacks.
    768. 

  768. object.off("change");
    769. 

  769. 

  770. // Removes the `onChange` callback for all events.
    771. 

  771. object.off(null, onChange);
    772. 

  772. 

  773. // Removes all callbacks for `context` for all events.
    774. 

  774. object.off(null, null, context);
    775. 

  775. 

  776. // Removes all callbacks on `object`.
    777. 

  777. object.off();
    778. 

  778. </pre>
    779. 

  779. 

  780.     <p>
    781. 

  781.       Note that calling <tt>model.off()</tt>, for example, will indeed remove <i>all</i> events
    782. 

  782.       on the model &mdash; including events that Backbone uses for internal bookkeeping.
    783. 

  783.     </p>
    784. 

  784. 

  785.     <p id="Events-trigger">
    786. 

  786.       <b class="header">trigger</b><code>object.trigger(event, [*args])</code>
    787. 

  787.       <br />
    788. 

  788.       Trigger callbacks for the given <b>event</b>, or space-delimited list of events.
    789. 

  789.       Subsequent arguments to <b>trigger</b> will be passed along to the
    790. 

  790.       event callbacks.
    791. 

  791.     </p>
    792. 

  792. 

  793.     <p id="Events-once">
    794. 

  794.       <b class="header">once</b><code>object.once(event, callback, [context])</code>
    795. 

  795.       <br />
    796. 

  796.       Just like <a href="#Events-on">on</a>, but causes the bound callback to only
    797. 

  797.       fire once before being removed. Handy for saying "the next time that X happens, do this".
    798. 

  798.     </p>
    799. 

  799. 

  800.     <p id="Events-listenTo">
    801. 

  801.       <b class="header">listenTo</b><code>object.listenTo(other, event, callback)</code>
    802. 

  802.       <br />
    803. 

  803.       Tell an <b>object</b> to listen to a particular event on an <b>other</b>
    804. 

  804.       object.  The advantage of using this form, instead of <tt>other.on(event,
    805. 

  805.       callback, object)</tt>, is that <b>listenTo</b> allows the <b>object</b>
    806. 

  806.       to keep track of the events, and they can be removed all at once later
    807. 

  807.       on.  The <b>callback</b> will always be called with <b>object</b> as
    808. 

  808.       context.
    809. 

  809.     </p>
    810. 

  810. 

  811. <pre>
    812. 

  812. view.listenTo(model, 'change', view.render);
    813. 

  813. </pre>
    814. 

  814. 

  815.     <p id="Events-stopListening">
    816. 

  816.       <b class="header">stopListening</b><code>object.stopListening([other], [event], [callback])</code>
    817. 

  817.       <br />
    818. 

  818.       Tell an <b>object</b> to stop listening to events. Either call
    819. 

  819.       <b>stopListening</b> with no arguments to have the <b>object</b> remove
    820. 

  820.       all of its <a href="#Events-listenTo">registered</a> callbacks ... or be more
    821. 

  821.       precise by telling it to remove just the events it's listening to on a
    822. 

  822.       specific object, or a specific event, or just a specific callback.
    823. 

  823.     </p>
    824. 

  824. 

  825. <pre>
    826. 

  826. view.stopListening();
    827. 

  827. 

  828. view.stopListening(model);
    829. 

  829. </pre>
    830. 

  830. 

  831.     <p id="Events-listenToOnce">
    832. 

  832.       <b class="header">listenToOnce</b><code>object.listenToOnce(other, event, callback)</code>
    833. 

  833.       <br />
    834. 

  834.       Just like <a href="#Events-listenTo">listenTo</a>, but causes the bound
    835. 

  835.       callback to only fire once before being removed.
    836. 

  836.     </p>
    837. 

  837. 

  838.     <p id="Events-catalog">
    839. 

  839.       <b class="header">Catalog of Events</b>
    840. 

  840.       <br />
    841. 

  841.       Here's the complete list of built-in Backbone events, with arguments.
    842. 

  842.       You're also free to trigger your own events on Models, Collections and
    843. 

  843.       Views as you see fit. The <tt>Backbone</tt> object itself mixes in <tt>Events</tt>,
    844. 

  844.       and can be used to emit any global events that your application needs.
    845. 

  845.     </p>
    846. 

  846. 

  847.     <ul class="small">
    848. 

  848.       <li><b>"add"</b> (model, collection, options) &mdash; when a model is added to a collection. </li>
    849. 

  849.       <li><b>"remove"</b> (model, collection, options) &mdash; when a model is removed from a collection. </li>
    850. 

  850.       <li><b>"reset"</b> (collection, options) &mdash; when the collection's entire contents have been replaced. </li>
    851. 

  851.       <li><b>"sort"</b> (collection, options) &mdash; when the collection has been re-sorted. </li>
    852. 

  852.       <li><b>"change"</b> (model, options) &mdash; when a model's attributes have changed. </li>
    853. 

  853.       <li><b>"change:[attribute]"</b> (model, value, options) &mdash; when a specific attribute has been updated. </li>
    854. 

  854.       <li><b>"destroy"</b> (model, collection, options) &mdash; when a model is <a href="#Model-destroy">destroyed</a>. </li>
    855. 

  855.       <li><b>"request"</b> (model, xhr, options) &mdash; when a model (or collection) has started a request to the server. </li>
    856. 

  856.       <li><b>"sync"</b> (model, resp, options) &mdash; when a model (or collection) has been successfully synced with the server. </li>
    857. 

  857.       <li><b>"error"</b> (model, xhr, options) &mdash; when a model's <a href="#Model-save">save</a> call fails on the server. </li>
    858. 

  858.       <li><b>"invalid"</b> (model, error, options) &mdash; when a model's <a href="#Model-validate">validation</a> fails on the client. </li>
    859. 

  859.       <li><b>"route:[name]"</b> (params) &mdash; Fired by the router when a specific route is matched.</li>
    860. 

  860.       <li><b>"route"</b> (route, params) &mdash; Fired by the router when <i>any</i> route has been matched.</li>
    861. 

  861.       <li><b>"route"</b> (router, route, params) &mdash; Fired by history when <i>any</i> route has been matched.</li>
    862. 

  862.       <li><b>"all"</b> &mdash; this special event fires for <i>any</i> triggered event, passing the event name as the first argument. </li>
    863. 

  863.     </ul>
    864. 

  864. 

  865.     <p>
    866. 

  866.       Generally speaking, when calling a function that emits an event
    867. 

  867.       (<tt>model.set()</tt>, <tt>collection.add</tt>, and so on...),
    868. 

  868.       if you'd like to prevent the event from being triggered, you may pass
    869. 

  869.       <tt>{silent: true}</tt> as an option. Note that this is <i>rarely</i>,
    870. 

  870.       perhaps even never, a good idea. Passing through a specific flag
    871. 

  871.       in the options for your event callback to look at, and choose to ignore,
    872. 

  872.       will usually work out better.
    873. 

  873.     </p>
    874. 

  874. 

  875.     <h2 id="Model">Backbone.Model</h2>
    876. 

  876. 

  877.     <p>
    878. 

  878.       <b>Models</b> are the heart of any JavaScript application, containing
    879. 

  879.       the interactive data as well as a large part of the logic surrounding it:
    880. 

  880.       conversions, validations, computed properties, and access control. You
    881. 

  881.       extend <b>Backbone.Model</b> with your domain-specific methods, and
    882. 

  882.       <b>Model</b> provides a basic set of functionality for managing changes.
    883. 

  883.     </p>
    884. 

  884. 

  885.     <p>
    886. 

  886.       The following is a contrived example, but it demonstrates defining a model
    887. 

  887.       with a custom method, setting an attribute, and firing an event keyed
    888. 

  888.       to changes in that specific attribute.
    889. 

  889.       After running this code once, <tt>sidebar</tt> will be
    890. 

  890.       available in your browser's console, so you can play around with it.
    891. 

  891.     </p>
    892. 

  892. 

  893. <pre class="runnable">
    894. 

  894. var Sidebar = Backbone.Model.extend({
    895. 

  895.   promptColor: function() {
    896. 

  896.     var cssColor = prompt("Please enter a CSS color:");
    897. 

  897.     this.set({color: cssColor});
    898. 

  898.   }
    899. 

  899. });
    900. 

  900. 

  901. window.sidebar = new Sidebar;
    902. 

  902. 

  903. sidebar.on('change:color', function(model, color) {
    904. 

  904.   $('#sidebar').css({background: color});
    905. 

  905. });
    906. 

  906. 

  907. sidebar.set({color: 'white'});
    908. 

  908. 

  909. sidebar.promptColor();
    910. 

  910. </pre>
    911. 

  911. 

  912.     <p id="Model-extend">
    913. 

  913.       <b class="header">extend</b><code>Backbone.Model.extend(properties, [classProperties])</code>
    914. 

  914.       <br />
    915. 

  915.       To create a <b>Model</b> class of your own, you extend <b>Backbone.Model</b>
    916. 

  916.       and provide instance <b>properties</b>, as well as optional
    917. 

  917.       <b>classProperties</b> to be attached directly to the constructor function.
    918. 

  918.     </p>
    919. 

  919. 

  920.     <p>
    921. 

  921.       <b>extend</b> correctly sets up the prototype chain, so subclasses created
    922. 

  922.       with <b>extend</b> can be further extended and subclassed as far as you like.
    923. 

  923.     </p>
    924. 

  924. 

  925. <pre>
    926. 

  926. var Note = Backbone.Model.extend({
    927. 

  927. 

  928.   initialize: function() { ... },
    929. 

  929. 

  930.   author: function() { ... },
    931. 

  931. 

  932.   coordinates: function() { ... },
    933. 

  933. 

  934.   allowedToEdit: function(account) {
    935. 

  935.     return true;
    936. 

  936.   }
    937. 

  937. 

  938. });
    939. 

  939. 

  940. var PrivateNote = Note.extend({
    941. 

  941. 

  942.   allowedToEdit: function(account) {
    943. 

  943.     return account.owns(this);
    944. 

  944.   }
    945. 

  945. 

  946. });
    947. 

  947. </pre>
    948. 

  948. 

  949.     <p class="warning">
    950. 

  950.         Brief aside on <tt>super</tt>: JavaScript does not provide
    951. 

  951.         a simple way to call super &mdash; the function of the same name defined
    952. 

  952.         higher on the prototype chain. If you override a core function like
    953. 

  953.         <tt>set</tt>, or <tt>save</tt>, and you want to invoke the
    954. 

  954.         parent object's implementation, you'll have to explicitly call it, along these lines:
    955. 

  955.     </p>
    956. 

  956. 

  957. <pre>
    958. 

  958. var Note = Backbone.Model.extend({
    959. 

  959.   set: function(attributes, options) {
    960. 

  960.     Backbone.Model.prototype.set.apply(this, arguments);
    961. 

  961.     ...
    962. 

  962.   }
    963. 

  963. });
    964. 

  964. </pre>
    965. 

  965. 

  966.     <p id="Model-constructor">
    967. 

  967.       <b class="header">constructor / initialize</b><code>new Model([attributes], [options])</code>
    968. 

  968.       <br />
    969. 

  969.       When creating an instance of a model, you can pass in the initial values
    970. 

  970.       of the <b>attributes</b>, which will be <a href="#Model-set">set</a> on the
    971. 

  971.       model. If you define an <b>initialize</b> function, it will be invoked when
    972. 

  972.       the model is created.
    973. 

  973.     </p>
    974. 

  974. 

  975. <pre>
    976. 

  976. new Book({
    977. 

  977.   title: "One Thousand and One Nights",
    978. 

  978.   author: "Scheherazade"
    979. 

  979. });
    980. 

  980. </pre>
    981. 

  981. 

  982.     <p>
    983. 

  983.       In rare cases, if you're looking to get fancy,
    984. 

  984.       you may want to override <b>constructor</b>, which allows
    985. 

  985.       you to replace the actual constructor function for your model.
    986. 

  986.     </p>
    987. 

  987. 

  988. <pre>
    989. 

  989. var Library = Backbone.Model.extend({
    990. 

  990.   constructor: function() {
    991. 

  991.     this.books = new Books();
    992. 

  992.     Backbone.Model.apply(this, arguments);
    993. 

  993.   },
    994. 

  994.   parse: function(data, options) {
    995. 

  995.     this.books.reset(data.books);
    996. 

  996.     return data.library;
    997. 

  997.   }
    998. 

  998. });
    999. 

  999. </pre>
    1000. 

  1000. 

  1001.     <p>
    1002. 

  1002.       If you pass a <tt>{collection: ...}</tt> as the <b>options</b>, the model
    1003. 

  1003.       gains a <tt>collection</tt> property that will be used to indicate which
    1004. 

  1004.       collection the model belongs to, and is used to help compute the model's
    1005. 

  1005.       <a href="#Model-url">url</a>. The <tt>model.collection</tt> property is
    1006. 

  1006.       normally created automatically when you first add a model to a collection.
    1007. 

  1007.       Note that the reverse is not true, as passing this option to the constructor 
    1008. 

  1008.       will not automatically add the model to the collection. Useful, sometimes.
    1009. 

  1009.     </p>
    1010. 

  1010. 

  1011.     <p>
    1012. 

  1012.       If <tt>{parse: true}</tt> is passed as an <b>option</b>, the <b>attributes</b>
    1013. 

  1013.       will first be converted by <a href="#Model-parse">parse</a> before being
    1014. 

  1014.       <a href="#Model-set">set</a> on the model.
    1015. 

  1015.     </p>
    1016. 

  1016. 

  1017.     <p id="Model-get">
    1018. 

  1018.       <b class="header">get</b><code>model.get(attribute)</code>
    1019. 

  1019.       <br />
    1020. 

  1020.       Get the current value of an attribute from the model. For example:
    1021. 

  1021.       <tt>note.get("title")</tt>
    1022. 

  1022.     </p>
    1023. 

  1023. 

  1024.     <p id="Model-set">
    1025. 

  1025.       <b class="header">set</b><code>model.set(attributes, [options])</code>
    1026. 

  1026.       <br />
    1027. 

  1027.       Set a hash of attributes (one or many) on the model. If any of the attributes
    1028. 

  1028.       change the model's state, a <tt>"change"</tt> event will be triggered on the model.
    1029. 

  1029.       Change events for specific attributes are also triggered, and you can bind
    1030. 

  1030.       to those as well, for example: <tt>change:title</tt>, and <tt>change:content</tt>.
    1031. 

  1031.       You may also pass individual keys and values.
    1032. 

  1032.     </p>
    1033. 

  1033. 

  1034. <pre>
    1035. 

  1035. note.set({title: "March 20", content: "In his eyes she eclipses..."});
    1036. 

  1036. 

  1037. book.set("title", "A Scandal in Bohemia");
    1038. 

  1038. </pre>
    1039. 

  1039. 

  1040.     <p id="Model-escape">
    1041. 

  1041.       <b class="header">escape</b><code>model.escape(attribute)</code>
    1042. 

  1042.       <br />
    1043. 

  1043.       Similar to <a href="#Model-get">get</a>, but returns the HTML-escaped version
    1044. 

  1044.       of a model's attribute. If you're interpolating data from the model into
    1045. 

  1045.       HTML, using <b>escape</b> to retrieve attributes will prevent
    1046. 

  1046.       <a href="http://en.wikipedia.org/wiki/Cross-site_scripting">XSS</a> attacks.
    1047. 

  1047.     </p>
    1048. 

  1048. 

  1049. <pre class="runnable">
    1050. 

  1050. var hacker = new Backbone.Model({
    1051. 

  1051.   name: "&lt;script&gt;alert('xss')&lt;/script&gt;"
    1052. 

  1052. });
    1053. 

  1053. 

  1054. alert(hacker.escape('name'));
    1055. 

  1055. </pre>
    1056. 

  1056. 

  1057.     <p id="Model-has">
    1058. 

  1058.       <b class="header">has</b><code>model.has(attribute)</code>
    1059. 

  1059.       <br />
    1060. 

  1060.       Returns <tt>true</tt> if the attribute is set to a non-null or non-undefined
    1061. 

  1061.       value.
    1062. 

  1062.     </p>
    1063. 

  1063. 

  1064. <pre>
    1065. 

  1065. if (note.has("title")) {
    1066. 

  1066.   ...
    1067. 

  1067. }
    1068. 

  1068. </pre>
    1069. 

  1069. 

  1070.     <p id="Model-unset">
    1071. 

  1071.       <b class="header">unset</b><code>model.unset(attribute, [options])</code>
    1072. 

  1072.       <br />
    1073. 

  1073.       Remove an attribute by deleting it from the internal attributes hash.
    1074. 

  1074.       Fires a <tt>"change"</tt> event unless <tt>silent</tt> is passed as an option.
    1075. 

  1075.     </p>
    1076. 

  1076. 

  1077.     <p id="Model-clear">
    1078. 

  1078.       <b class="header">clear</b><code>model.clear([options])</code>
    1079. 

  1079.       <br />
    1080. 

  1080.       Removes all attributes from the model, including the <tt>id</tt> attribute. Fires a <tt>"change"</tt> event unless
    1081. 

  1081.       <tt>silent</tt> is passed as an option.
    1082. 

  1082.     </p>
    1083. 

  1083. 

  1084.     <p id="Model-id">
    1085. 

  1085.       <b class="header">id</b><code>model.id</code>
    1086. 

  1086.       <br />
    1087. 

  1087.       A special property of models, the <b>id</b> is an arbitrary string
    1088. 

  1088.       (integer id or UUID). If you set the <b>id</b> in the
    1089. 

  1089.       attributes hash, it will be copied onto the model as a direct property.
    1090. 

  1090.       Models can be retrieved by id from collections, and the id is used to generate
    1091. 

  1091.       model URLs by default.
    1092. 

  1092.     </p>
    1093. 

  1093. 

  1094.     <p id="Model-idAttribute">
    1095. 

  1095.       <b class="header">idAttribute</b><code>model.idAttribute</code>
    1096. 

  1096.       <br />
    1097. 

  1097.       A model's unique identifier is stored under the <tt>id</tt> attribute.
    1098. 

  1098.       If you're directly communicating with a backend (CouchDB, MongoDB) that uses
    1099. 

  1099.       a different unique key, you may set a Model's <tt>idAttribute</tt> to
    1100. 

  1100.       transparently map from that key to <tt>id</tt>.
    1101. 

  1101. 

  1102. <pre class="runnable">
    1103. 

  1103. var Meal = Backbone.Model.extend({
    1104. 

  1104.   idAttribute: "_id"
    1105. 

  1105. });
    1106. 

  1106. 

  1107. var cake = new Meal({ _id: 1, name: "Cake" });
    1108. 

  1108. alert("Cake id: " + cake.id);
    1109. 

  1109. </pre>
    1110. 

  1110.     </p>
    1111. 

  1111. 

  1112.     <p id="Model-cid">
    1113. 

  1113.       <b class="header">cid</b><code>model.cid</code>
    1114. 

  1114.       <br />
    1115. 

  1115.       A special property of models, the <b>cid</b> or client id is a unique identifier
    1116. 

  1116.       automatically assigned to all models when they're first created. Client ids
    1117. 

  1117.       are handy when the model has not yet been saved to the server, and does not
    1118. 

  1118.       yet have its eventual true <b>id</b>, but already needs to be visible in the UI.
    1119. 

  1119.     </p>
    1120. 

  1120. 

  1121.     <p id="Model-attributes">
    1122. 

  1122.       <b class="header">attributes</b><code>model.attributes</code>
    1123. 

  1123.       <br />
    1124. 

  1124.       The <b>attributes</b> property is the internal hash containing the model's
    1125. 

  1125.       state &mdash; usually (but not necessarily) a form of the JSON object
    1126. 

  1126.       representing the model data on the server. It's often a straightforward
    1127. 

  1127.       serialization of a row from the database, but it could also be client-side
    1128. 

  1128.       computed state.
    1129. 

  1129.     </p>
    1130. 

  1130. 

  1131.     <p>
    1132. 

  1132.       Please use <a href="#Model-set">set</a> to update the <b>attributes</b>
    1133. 

  1133.       instead of modifying them directly. If you'd like to retrieve and munge a
    1134. 

  1134.       copy of the model's attributes, use <tt>_.clone(model.attributes)</tt>
    1135. 

  1135.       instead.
    1136. 

  1136.     </p>
    1137. 

  1137. 

  1138.     <p class="warning">
    1139. 

  1139.       Due to the fact that <a href="#Events">Events</a> accepts space separated
    1140. 

  1140.       lists of events, attribute names should not include spaces.
    1141. 

  1141.     </p>
    1142. 

  1142. 

  1143.     <p id="Model-changed">
    1144. 

  1144.       <b class="header">changed</b><code>model.changed</code>
    1145. 

  1145.       <br />
    1146. 

  1146.       The <b>changed</b> property is the internal hash containing all the attributes
    1147. 

  1147.       that have changed since the last <a href="Model#set">set</a>.
    1148. 

  1148.       Please do not update <b>changed</b> directly since its state is internally maintained
    1149. 

  1149.       by <a href="#Model-set">set</a>.  A copy of <b>changed</b> can be acquired from
    1150. 

  1150.       <a href="#Model-changedAttributes">changedAttributes</a>.
    1151. 

  1151.     </p>
    1152. 

  1152. 

  1153.     <p id="Model-defaults">
    1154. 

  1154.       <b class="header">defaults</b><code>model.defaults or model.defaults()</code>
    1155. 

  1155.       <br />
    1156. 

  1156.       The <b>defaults</b> hash (or function) can be used to specify the default
    1157. 

  1157.       attributes for your model. When creating an instance of the model,
    1158. 

  1158.       any unspecified attributes will be set to their default value.
    1159. 

  1159.     </p>
    1160. 

  1160. 

  1161. <pre class="runnable">
    1162. 

  1162. var Meal = Backbone.Model.extend({
    1163. 

  1163.   defaults: {
    1164. 

  1164.     "appetizer":  "caesar salad",
    1165. 

  1165.     "entree":     "ravioli",
    1166. 

  1166.     "dessert":    "cheesecake"
    1167. 

  1167.   }
    1168. 

  1168. });
    1169. 

  1169. 

  1170. alert("Dessert will be " + (new Meal).get('dessert'));
    1171. 

  1171. </pre>
    1172. 

  1172. 

  1173.     <p class="warning">
    1174. 

  1174.       Remember that in JavaScript, objects are passed by reference, so if you
    1175. 

  1175.       include an object as a default value, it will be shared among all instances.
    1176. 

  1176.       Instead, define <b>defaults</b> as a function.
    1177. 

  1177.     </p>
    1178. 

  1178. 

  1179.     <p id="Model-toJSON">
    1180. 

  1180.       <b class="header">toJSON</b><code>model.toJSON([options])</code>
    1181. 

  1181.       <br />
    1182. 

  1182.       Return a shallow copy of the model's <a href="#Model-attributes">attributes</a>
    1183. 

  1183.       for JSON stringification.  This can be used for persistence,
    1184. 

  1184.       serialization, or for augmentation before being sent to the server. The
    1185. 

  1185.       name of this method is a bit confusing, as it doesn't actually return a
    1186. 

  1186.       JSON string &mdash; but I'm afraid that it's the way that the
    1187. 

  1187.       <a href="https://developer.mozilla.org/en/JSON#toJSON()_method">JavaScript API for <b>JSON.stringify</b></a>
    1188. 

  1188.       works.
    1189. 

  1189.     </p>
    1190. 

  1190. 

  1191. <pre class="runnable">
    1192. 

  1192. var artist = new Backbone.Model({
    1193. 

  1193.   firstName: "Wassily",
    1194. 

  1194.   lastName: "Kandinsky"
    1195. 

  1195. });
    1196. 

  1196. 

  1197. artist.set({birthday: "December 16, 1866"});
    1198. 

  1198. 

  1199. alert(JSON.stringify(artist));
    1200. 

  1200. </pre>
    1201. 

  1201. 

  1202.     <p id="Model-sync">
    1203. 

  1203.       <b class="header">sync</b><code>model.sync(method, model, [options])</code>
    1204. 

  1204.       <br />
    1205. 

  1205.       Uses <a href="#Sync">Backbone.sync</a> to persist the state of a model to
    1206. 

  1206.       the server.  Can be overridden for custom behavior.
    1207. 

  1207.     </p>
    1208. 

  1208. 

  1209.     <p id="Model-fetch">
    1210. 

  1210.       <b class="header">fetch</b><code>model.fetch([options])</code>
    1211. 

  1211.       <br />
    1212. 

  1212.       Resets the model's state from the server by delegating to
    1213. 

  1213.       <a href="#Sync">Backbone.sync</a>. Returns a
    1214. 

  1214.       <a href="http://api.jquery.com/jQuery.ajax/#jqXHR">jqXHR</a>.
    1215. 

  1215.       Useful if the model has never
    1216. 

  1216.       been populated with data, or if you'd like to ensure that you have the
    1217. 

  1217.       latest server state. A <tt>"change"</tt> event will be triggered if the
    1218. 

  1218.       server's state differs from the current attributes. Accepts
    1219. 

  1219.       <tt>success</tt> and <tt>error</tt> callbacks in the options hash, which
    1220. 

  1220.       are both passed <tt>(model, response, options)</tt> as arguments.
    1221. 

  1221.     </p>
    1222. 

  1222. 

  1223. <pre>
    1224. 

  1224. // Poll every 10 seconds to keep the channel model up-to-date.
    1225. 

  1225. setInterval(function() {
    1226. 

  1226.   channel.fetch();
    1227. 

  1227. }, 10000);
    1228. 

  1228. </pre>
    1229. 

  1229. 

  1230.     <p id="Model-save">
    1231. 

  1231.       <b class="header">save</b><code>model.save([attributes], [options])</code>
    1232. 

  1232.       <br />
    1233. 

  1233.       Save a model to your database (or alternative persistence layer),
    1234. 

  1234.       by delegating to <a href="#Sync">Backbone.sync</a>.  Returns a
    1235. 

  1235.       <a href="http://api.jquery.com/jQuery.ajax/#jqXHR">jqXHR</a> if
    1236. 

  1236.       validation is successful and <tt>false</tt> otherwise. The <b>attributes</b>
    1237. 

  1237.       hash (as in <a href="#Model-set">set</a>) should contain the attributes
    1238. 

  1238.       you'd like to change &mdash; keys that aren't mentioned won't be altered &mdash; but,
    1239. 

  1239.       a <i>complete representation</i> of the resource will be sent to the server.
    1240. 

  1240.       As with <tt>set</tt>, you may pass individual keys and values instead of a hash.
    1241. 

  1241.       If the model has a <a href="#Model-validate">validate</a>
    1242. 

  1242.       method, and validation fails, the model will not be saved. If the model
    1243. 

  1243.       <a href="#Model-isNew">isNew</a>, the save will be a <tt>"create"</tt>
    1244. 

  1244.       (HTTP <tt>POST</tt>), if the model already
    1245. 

  1245.       exists on the server, the save will be an <tt>"update"</tt> (HTTP <tt>PUT</tt>).
    1246. 

  1246.     </p>
    1247. 

  1247. 

  1248.     <p>
    1249. 

  1249.       If instead, you'd only like the <i>changed</i> attributes to be sent to the
    1250. 

  1250.       server, call <tt>model.save(attrs, {patch: true})</tt>. You'll get an HTTP
    1251. 

  1251.       <tt>PATCH</tt> request to the server with just the passed-in attributes.
    1252. 

  1252.     </p>
    1253. 

  1253. 

  1254.     <p>
    1255. 

  1255.       Calling <tt>save</tt> with new attributes will cause a <tt>"change"</tt>
    1256. 

  1256.       event immediately, a <tt>"request"</tt> event as the Ajax request begins to
    1257. 

  1257.       go to the server, and a <tt>"sync"</tt> event after the server has acknowledged
    1258. 

  1258.       the successful change. Pass <tt>{wait: true}</tt> if you'd like to wait
    1259. 

  1259.       for the server before setting the new attributes on the model.
    1260. 

  1260.     </p>
    1261. 

  1261. 

  1262.     <p>
    1263. 

  1263.       In the following example, notice how our overridden version
    1264. 

  1264.       of <tt>Backbone.sync</tt> receives a <tt>"create"</tt> request
    1265. 

  1265.       the first time the model is saved and an <tt>"update"</tt>
    1266. 

  1266.       request the second time.
    1267. 

  1267.     </p>
    1268. 

  1268. 

  1269. <pre class="runnable">
    1270. 

  1270. Backbone.sync = function(method, model) {
    1271. 

  1271.   alert(method + ": " + JSON.stringify(model));
    1272. 

  1272.   model.id = 1;
    1273. 

  1273. };
    1274. 

  1274. 

  1275. var book = new Backbone.Model({
    1276. 

  1276.   title: "The Rough Riders",
    1277. 

  1277.   author: "Theodore Roosevelt"
    1278. 

  1278. });
    1279. 

  1279. 

  1280. book.save();
    1281. 

  1281. 

  1282. book.save({author: "Teddy"});
    1283. 

  1283. </pre>
    1284. 

  1284. 

  1285.     <p>
    1286. 

  1286.       <b>save</b> accepts <tt>success</tt> and <tt>error</tt> callbacks in the
    1287. 

  1287.       options hash, which are passed <tt>(model, response, options)</tt> and
    1288. 

  1288.       <tt>(model, xhr, options)</tt> as arguments, respectively.
    1289. 

  1289.       If a server-side validation fails, return a non-<tt>200</tt>
    1290. 

  1290.       HTTP response code, along with an error response in text or JSON.
    1291. 

  1291.     </p>
    1292. 

  1292. 

  1293. <pre>
    1294. 

  1294. book.save("author", "F.D.R.", {error: function(){ ... }});
    1295. 

  1295. </pre>
    1296. 

  1296. 

  1297.     <p id="Model-destroy">
    1298. 

  1298.       <b class="header">destroy</b><code>model.destroy([options])</code>
    1299. 

  1299.       <br />
    1300. 

  1300.       Destroys the model on the server by delegating an HTTP <tt>DELETE</tt>
    1301. 

  1301.       request to <a href="#Sync">Backbone.sync</a>. Returns a
    1302. 

  1302.       <a href="http://api.jquery.com/jQuery.ajax/#jqXHR">jqXHR</a> object, or
    1303. 

  1303.       <tt>false</tt> if the model <a href="#Model-isNew">isNew</a>. Accepts
    1304. 

  1304.       <tt>success</tt> and <tt>error</tt> callbacks in the options hash, which
    1305. 

  1305.       are passed <tt>(model, response, options)</tt> and <tt>(model, xhr, options)</tt>
    1306. 

  1306.       as arguments, respectively.
    1307. 

  1307.       Triggers a <tt>"destroy"</tt> event on the model, which will bubble up
    1308. 

  1308.       through any collections that contain it, a <tt>"request"</tt> event as it
    1309. 

  1309.       begins the Ajax request to the server, and a <tt>"sync"</tt> event, after
    1310. 

  1310.       the server has successfully acknowledged the model's deletion. Pass
    1311. 

  1311.       <tt>{wait: true}</tt> if you'd like to wait for the server to respond
    1312. 

  1312.       before removing the model from the collection.
    1313. 

  1313.     </p>
    1314. 

  1314. 

  1315. <pre>
    1316. 

  1316. book.destroy({success: function(model, response) {
    1317. 

  1317.   ...
    1318. 

  1318. }});
    1319. 

  1319. </pre>
    1320. 

  1320. 

  1321.     <p id="Model-Underscore-Methods">
    1322. 

  1322.       <b class="header">Underscore Methods (6)</b>
    1323. 

  1323.       <br />
    1324. 

  1324.       Backbone proxies to <b>Underscore.js</b> to provide 6 object functions
    1325. 

  1325.       on <b>Backbone.Model</b>. They aren't all documented here, but
    1326. 

  1326.       you can take a look at the Underscore documentation for the full details&hellip;
    1327. 

  1327.     </p>
    1328. 

  1328. 

  1329.     <ul class="small">
    1330. 

  1330.       <li><a href="http://underscorejs.org/#keys">keys</a></li>
    1331. 

  1331.       <li><a href="http://underscorejs.org/#values">values</a></li>
    1332. 

  1332.       <li><a href="http://underscorejs.org/#pairs">pairs</a></li>
    1333. 

  1333.       <li><a href="http://underscorejs.org/#invert">invert</a></li>
    1334. 

  1334.       <li><a href="http://underscorejs.org/#pick">pick</a></li>
    1335. 

  1335.       <li><a href="http://underscorejs.org/#omit">omit</a></li>
    1336. 

  1336.     </ul>
    1337. 

  1337. 

  1338. <pre>
    1339. 

  1339. user.pick('first_name', 'last_name', 'email');
    1340. 

  1340. 

  1341. chapters.keys().join(', ');
    1342. 

  1342. </pre>
    1343. 

  1343. 

  1344.     <p id="Model-validate">
    1345. 

  1345.       <b class="header">validate</b><code>model.validate(attributes, options)</code>
    1346. 

  1346.       <br />
    1347. 

  1347.       This method is left undefined, and you're encouraged to override it with
    1348. 

  1348.       your custom validation logic, if you have any that can be performed
    1349. 

  1349.       in JavaScript. By default <b>validate</b> is called before
    1350. 

  1350.       <tt>save</tt>, but can also be called before <tt>set</tt> if
    1351. 

  1351.       <tt>{validate:true}</tt> is passed. The <b>validate</b> method is passed
    1352. 

  1352.       the model attributes, as well as the options from <tt>set</tt> or <tt>save</tt>.
    1353. 

  1353.       If the attributes are valid, don't return anything from <b>validate</b>;
    1354. 

  1354.       if they are invalid, return an error of your choosing. It
    1355. 

  1355.       can be as simple as a string error message to be displayed, or a complete
    1356. 

  1356.       error object that describes the error programmatically. If <b>validate</b>
    1357. 

  1357.       returns an error, <tt>save</tt> will not continue, and the
    1358. 

  1358.       model attributes will not be modified on the server.
    1359. 

  1359.       Failed validations trigger an <tt>"invalid"</tt> event, and set the
    1360. 

  1360.       <tt>validationError</tt> property on the model with the value returned by
    1361. 

  1361.       this method.
    1362. 

  1362.     </p>
    1363. 

  1363. 

  1364. <pre class="runnable">
    1365. 

  1365. var Chapter = Backbone.Model.extend({
    1366. 

  1366.   validate: function(attrs, options) {
    1367. 

  1367.     if (attrs.end &lt; attrs.start) {
    1368. 

  1368.       return "can't end before it starts";
    1369. 

  1369.     }
    1370. 

  1370.   }
    1371. 

  1371. });
    1372. 

  1372. 

  1373. var one = new Chapter({
    1374. 

  1374.   title : "Chapter One: The Beginning"
    1375. 

  1375. });
    1376. 

  1376. 

  1377. one.on("invalid", function(model, error) {
    1378. 

  1378.   alert(model.get("title") + " " + error);
    1379. 

  1379. });
    1380. 

  1380. 

  1381. one.save({
    1382. 

  1382.   start: 15,
    1383. 

  1383.   end:   10
    1384. 

  1384. });
    1385. 

  1385. </pre>
    1386. 

  1386. 

  1387.     <p>
    1388. 

  1388.       <tt>"invalid"</tt> events are useful for providing coarse-grained error
    1389. 

  1389.       messages at the model or collection level.
    1390. 

  1390.     </p>
    1391. 

  1391. 

  1392.     <p id="Model-validationError">
    1393. 

  1393.       <b class="header">validationError</b><code>model.validationError</code>
    1394. 

  1394.       <br />
    1395. 

  1395.       The value returned by <a href="#Model-validate">validate</a> during the last failed validation.
    1396. 

  1396.     </p>
    1397. 

  1397. 

  1398.     <p id="Model-isValid">
    1399. 

  1399.       <b class="header">isValid</b><code>model.isValid</code>
    1400. 

  1400.       <br />
    1401. 

  1401.       Run <a href="#Model-validate">validate</a> to check the model state.
    1402. 

  1402.     </p>
    1403. 

  1403. 

  1404. <pre class="runnable">
    1405. 

  1405. var Chapter = Backbone.Model.extend({
    1406. 

  1406.   validate: function(attrs, options) {
    1407. 

  1407.     if (attrs.end &lt; attrs.start) {
    1408. 

  1408.       return "can't end before it starts";
    1409. 

  1409.     }
    1410. 

  1410.   }
    1411. 

  1411. });
    1412. 

  1412. 

  1413. var one = new Chapter({
    1414. 

  1414.   title : "Chapter One: The Beginning"
    1415. 

  1415. });
    1416. 

  1416. 

  1417. one.set({
    1418. 

  1418.   start: 15,
    1419. 

  1419.   end:   10
    1420. 

  1420. });
    1421. 

  1421. 

  1422. if (!one.isValid()) {
    1423. 

  1423.   alert(one.get("title") + " " + one.validationError);
    1424. 

  1424. }
    1425. 

  1425. </pre>
    1426. 

  1426. 

  1427.     <p id="Model-url">
    1428. 

  1428.       <b class="header">url</b><code>model.url()</code>
    1429. 

  1429.       <br />
    1430. 

  1430.       Returns the relative URL where the model's resource would be located on
    1431. 

  1431.       the server. If your models are located somewhere else, override this method
    1432. 

  1432.       with the correct logic. Generates URLs of the form: <tt>"[collection.url]/[id]"</tt>
    1433. 

  1433.       by default, but you may override by specifying an explicit <tt>urlRoot</tt>
    1434. 

  1434.       if the model's collection shouldn't be taken into account. You can also
    1435. 

  1435.       pass in the model's <tt>url</tt> as an option when instantiating it.
    1436. 

  1436.     </p>
    1437. 

  1437. 

  1438.     <p>
    1439. 

  1439.       Delegates to <a href="#Collection-url">Collection#url</a> to generate the
    1440. 

  1440.       URL, so make sure that you have it defined, or a <a href="#Model-urlRoot">urlRoot</a>
    1441. 

  1441.       property, if all models of this class share a common root URL.
    1442. 

  1442.       A model with an id of <tt>101</tt>, stored in a
    1443. 

  1443.       <a href="#Collection">Backbone.Collection</a> with a <tt>url</tt> of <tt>"/documents/7/notes"</tt>,
    1444. 

  1444.       would have this URL: <tt>"/documents/7/notes/101"</tt>
    1445. 

  1445.     </p>
    1446. 

  1446. 

  1447.     <p id="Model-urlRoot">
    1448. 

  1448.       <b class="header">urlRoot</b><code>model.urlRoot or model.urlRoot()</code>
    1449. 

  1449.       <br />
    1450. 

  1450.       Specify a <tt>urlRoot</tt> if you're using a model <i>outside</i> of a collection,
    1451. 

  1451.       to enable the default <a href="#Model-url">url</a> function to generate
    1452. 

  1452.       URLs based on the model id. <tt>"[urlRoot]/id"</tt><br />
    1453. 

  1453.       Normally, you won't need to define this.
    1454. 

  1454.       Note that <tt>urlRoot</tt> may also be a function.
    1455. 

  1455.     </p>
    1456. 

  1456. 

  1457. <pre class="runnable">
    1458. 

  1458. var Book = Backbone.Model.extend({urlRoot : '/books'});
    1459. 

  1459. 

  1460. var solaris = new Book({id: "1083-lem-solaris"});
    1461. 

  1461. 

  1462. alert(solaris.url());
    1463. 

  1463. </pre>
    1464. 

  1464. 

  1465.     <p id="Model-parse">
    1466. 

  1466.       <b class="header">parse</b><code>model.parse(response, options)</code>
    1467. 

  1467.       <br />
    1468. 

  1468.       <b>parse</b> is called whenever a model's data is returned by the
    1469. 

  1469.       server, in <a href="#Model-fetch">fetch</a>, and <a href="#Model-save">save</a>.
    1470. 

  1470.       The function is passed the raw <tt>response</tt> object, and should return
    1471. 

  1471.       the attributes hash to be <a href="#Model-set">set</a> on the model. The
    1472. 

  1472.       default implementation is a no-op, simply passing through the JSON response.
    1473. 

  1473.       Override this if you need to work with a preexisting API, or better namespace
    1474. 

  1474.       your responses.
    1475. 

  1475.     </p>
    1476. 

  1476. 

  1477.     <p>
    1478. 

  1478.       If you're working with a Rails backend that has a version prior to 3.1,
    1479. 

  1479.       you'll notice that its default <tt>to_json</tt> implementation includes
    1480. 

  1480.       a model's attributes under a namespace. To disable this behavior for
    1481. 

  1481.       seamless Backbone integration, set:
    1482. 

  1482.     </p>
    1483. 

  1483. 

  1484. <pre>
    1485. 

  1485. ActiveRecord::Base.include_root_in_json = false
    1486. 

  1486. </pre>
    1487. 

  1487. 

  1488.     <p id="Model-clone">
    1489. 

  1489.       <b class="header">clone</b><code>model.clone()</code>
    1490. 

  1490.       <br />
    1491. 

  1491.       Returns a new instance of the model with identical attributes.
    1492. 

  1492.     </p>
    1493. 

  1493. 

  1494.     <p id="Model-isNew">
    1495. 

  1495.       <b class="header">isNew</b><code>model.isNew()</code>
    1496. 

  1496.       <br />
    1497. 

  1497.       Has this model been saved to the server yet? If the model does not yet have
    1498. 

  1498.       an <tt>id</tt>, it is considered to be new.
    1499. 

  1499.     </p>
    1500. 

  1500. 

  1501.     <p id="Model-hasChanged">
    1502. 

  1502.       <b class="header">hasChanged</b><code>model.hasChanged([attribute])</code>
    1503. 

  1503.       <br />
    1504. 

  1504.       Has the model changed since the last <a href="#Model-set">set</a>? If an <b>attribute</b>
    1505. 

  1505.       is passed, returns <tt>true</tt> if that specific attribute has changed.
    1506. 

  1506.     </p>
    1507. 

  1507. 

  1508.     <p class="warning">
    1509. 

  1509.       Note that this method, and the following change-related ones,
    1510. 

  1510.       are only useful during the course of a <tt>"change"</tt> event.
    1511. 

  1511.     </p>
    1512. 

  1512. 

  1513. <pre>
    1514. 

  1514. book.on("change", function() {
    1515. 

  1515.   if (book.hasChanged("title")) {
    1516. 

  1516.     ...
    1517. 

  1517.   }
    1518. 

  1518. });
    1519. 

  1519. </pre>
    1520. 

  1520. 

  1521.     <p id="Model-changedAttributes">
    1522. 

  1522.       <b class="header">changedAttributes</b><code>model.changedAttributes([attributes])</code>
    1523. 

  1523.       <br />
    1524. 

  1524.       Retrieve a hash of only the model's attributes that have changed since the last
    1525. 

  1525.       <a href="#Model-set">set</a>, or <tt>false</tt> if there are none. Optionally, an external
    1526. 

  1526.       <b>attributes</b> hash can be passed in, returning the attributes in that
    1527. 

  1527.       hash which differ from the model. This can be used to figure out which
    1528. 

  1528.       portions of a view should be updated, or what calls
    1529. 

  1529.       need to be made to sync the changes to the server.
    1530. 

  1530.     </p>
    1531. 

  1531. 

  1532.     <p id="Model-previous">
    1533. 

  1533.       <b class="header">previous</b><code>model.previous(attribute)</code>
    1534. 

  1534.       <br />
    1535. 

  1535.       During a <tt>"change"</tt> event, this method can be used to get the
    1536. 

  1536.       previous value of a changed attribute.
    1537. 

  1537.     </p>
    1538. 

  1538. 

  1539. <pre class="runnable">
    1540. 

  1540. var bill = new Backbone.Model({
    1541. 

  1541.   name: "Bill Smith"
    1542. 

  1542. });
    1543. 

  1543. 

  1544. bill.on("change:name", function(model, name) {
    1545. 

  1545.   alert("Changed name from " + bill.previous("name") + " to " + name);
    1546. 

  1546. });
    1547. 

  1547. 

  1548. bill.set({name : "Bill Jones"});
    1549. 

  1549. </pre>
    1550. 

  1550. 

  1551.     <p id="Model-previousAttributes">
    1552. 

  1552.       <b class="header">previousAttributes</b><code>model.previousAttributes()</code>
    1553. 

  1553.       <br />
    1554. 

  1554.       Return a copy of the model's previous attributes. Useful for getting a
    1555. 

  1555.       diff between versions of a model, or getting back to a valid state after
    1556. 

  1556.       an error occurs.
    1557. 

  1557.     </p>
    1558. 

  1558. 

  1559.     <h2 id="Collection">Backbone.Collection</h2>
    1560. 

  1560. 

  1561.     <p>
    1562. 

  1562.       Collections are ordered sets of models. You can bind <tt>"change"</tt> events
    1563. 

  1563.       to be notified when any model in the collection has been modified,
    1564. 

  1564.       listen for <tt>"add"</tt> and <tt>"remove"</tt> events, <tt>fetch</tt>
    1565. 

  1565.       the collection from the server, and use a full suite of
    1566. 

  1566.       <a href="#Collection-Underscore-Methods">Underscore.js methods</a>.
    1567. 

  1567.     </p>
    1568. 

  1568. 

  1569.     <p>
    1570. 

  1570.       Any event that is triggered on a model in a collection will also be
    1571. 

  1571.       triggered on the collection directly, for convenience.
    1572. 

  1572.       This allows you to listen for changes to specific attributes in any
    1573. 

  1573.       model in a collection, for example:
    1574. 

  1574.       <tt>documents.on("change:selected", ...)</tt>
    1575. 

  1575.     </p>
    1576. 

  1576. 

  1577.     <p id="Collection-extend">
    1578. 

  1578.       <b class="header">extend</b><code>Backbone.Collection.extend(properties, [classProperties])</code>
    1579. 

  1579.       <br />
    1580. 

  1580.       To create a <b>Collection</b> class of your own, extend <b>Backbone.Collection</b>,
    1581. 

  1581.       providing instance <b>properties</b>, as well as optional <b>classProperties</b> to be attached
    1582. 

  1582.       directly to the collection's constructor function.
    1583. 

  1583.     </p>
    1584. 

  1584. 

  1585.     <p id="Collection-model">
    1586. 

  1586.       <b class="header">model</b><code>collection.model</code>
    1587. 

  1587.       <br />
    1588. 

  1588.       Override this property to specify the model class that the collection
    1589. 

  1589.       contains. If defined, you can pass raw attributes objects (and arrays) to
    1590. 

  1590.       <a href="#Collection-add">add</a>, <a href="#Collection-create">create</a>,
    1591. 

  1591.       and <a href="#Collection-reset">reset</a>, and the attributes will be
    1592. 

  1592.       converted into a model of the proper type.
    1593. 

  1593.     </p>
    1594. 

  1594. 

  1595. <pre>
    1596. 

  1596. var Library = Backbone.Collection.extend({
    1597. 

  1597.   model: Book
    1598. 

  1598. });
    1599. 

  1599. </pre>
    1600. 

  1600. 

  1601.     <p>
    1602. 

  1602.       A collection can also contain polymorphic models by overriding this property
    1603. 

  1603.       with a constructor that returns a model.
    1604. 

  1604.     </p>
    1605. 

  1605. 

  1606. <pre>
    1607. 

  1607. var Library = Backbone.Collection.extend({
    1608. 

  1608. 

  1609.   model: function(attrs, options) {
    1610. 

  1610.     if (condition) {
    1611. 

  1611.       return new PublicDocument(attrs, options);
    1612. 

  1612.     } else {
    1613. 

  1613.       return new PrivateDocument(attrs, options);
    1614. 

  1614.     }
    1615. 

  1615.   }
    1616. 

  1616. 

  1617. });
    1618. 

  1618. </pre>
    1619. 

  1619. 

  1620.     <p id="Collection-constructor">
    1621. 

  1621.       <b class="header">constructor / initialize</b><code>new Backbone.Collection([models], [options])</code>
    1622. 

  1622.       <br />
    1623. 

  1623.       When creating a Collection, you may choose to pass in the initial array
    1624. 

  1624.       of <b>models</b>.  The collection's <a href="#Collection-comparator">comparator</a>
    1625. 

  1625.       may be included as an option. Passing <tt>false</tt> as the
    1626. 

  1626.       comparator option will prevent sorting. If you define an
    1627. 

  1627.       <b>initialize</b> function, it will be invoked when the collection is
    1628. 

  1628.       created. There are a couple of options that, if provided, are attached to
    1629. 

  1629.       the collection directly: <tt>model</tt> and <tt>comparator</tt>.
    1630. 

  1630.     </p>
    1631. 

  1631. 

  1632. <pre>
    1633. 

  1633. var tabs = new TabSet([tab1, tab2, tab3]);
    1634. 

  1634. var spaces = new Backbone.Collection([], {
    1635. 

  1635.   model: Space
    1636. 

  1636. });
    1637. 

  1637. </pre>
    1638. 

  1638. 

  1639.     <p id="Collection-models">
    1640. 

  1640.       <b class="header">models</b><code>collection.models</code>
    1641. 

  1641.       <br />
    1642. 

  1642.       Raw access to the JavaScript array of models inside of the collection. Usually you'll
    1643. 

  1643.       want to use <tt>get</tt>, <tt>at</tt>, or the <b>Underscore methods</b>
    1644. 

  1644.       to access model objects, but occasionally a direct reference to the array
    1645. 

  1645.       is desired.
    1646. 

  1646.     </p>
    1647. 

  1647. 

  1648.     <p id="Collection-toJSON">
    1649. 

  1649.       <b class="header">toJSON</b><code>collection.toJSON([options])</code>
    1650. 

  1650.       <br />
    1651. 

  1651.       Return an array containing the attributes hash of each model
    1652. 

  1652.       (via <a href="#Model-toJSON">toJSON</a>) in the
    1653. 

  1653.       collection. This can be used to serialize and persist the
    1654. 

  1654.       collection as a whole. The name of this method is a bit confusing, because
    1655. 

  1655.       it conforms to
    1656. 

  1656.       <a href="https://developer.mozilla.org/en/JSON#toJSON()_method">JavaScript's JSON API</a>.
    1657. 

  1657.     </p>
    1658. 

  1658. 

  1659. <pre class="runnable">
    1660. 

  1660. var collection = new Backbone.Collection([
    1661. 

  1661.   {name: "Tim", age: 5},
    1662. 

  1662.   {name: "Ida", age: 26},
    1663. 

  1663.   {name: "Rob", age: 55}
    1664. 

  1664. ]);
    1665. 

  1665. 

  1666. alert(JSON.stringify(collection));
    1667. 

  1667. </pre>
    1668. 

  1668. 

  1669.     <p id="Collection-sync">
    1670. 

  1670.       <b class="header">sync</b><code>collection.sync(method, collection, [options])</code>
    1671. 

  1671.       <br />
    1672. 

  1672.       Uses <a href="#Sync">Backbone.sync</a> to persist the state of a
    1673. 

  1673.       collection to the server.  Can be overridden for custom behavior.
    1674. 

  1674.     </p>
    1675. 

  1675. 

  1676.     <p id="Collection-Underscore-Methods">
    1677. 

  1677.       <b class="header">Underscore Methods (28)</b>
    1678. 

  1678.       <br />
    1679. 

  1679.       Backbone proxies to <b>Underscore.js</b> to provide 28 iteration functions
    1680. 

  1680.       on <b>Backbone.Collection</b>. They aren't all documented here, but
    1681. 

  1681.       you can take a look at the Underscore documentation for the full details&hellip;
    1682. 

  1682.     </p>
    1683. 

  1683. 

  1684.     <ul class="small">
    1685. 

  1685.       <li><a href="http://underscorejs.org/#each">forEach (each)</a></li>
    1686. 

  1686.       <li><a href="http://underscorejs.org/#map">map (collect)</a></li>
    1687. 

  1687.       <li><a href="http://underscorejs.org/#reduce">reduce (foldl, inject)</a></li>
    1688. 

  1688.       <li><a href="http://underscorejs.org/#reduceRight">reduceRight (foldr)</a></li>
    1689. 

  1689.       <li><a href="http://underscorejs.org/#find">find (detect)</a></li>
    1690. 

  1690.       <li><a href="http://underscorejs.org/#filter">filter (select)</a></li>
    1691. 

  1691.       <li><a href="http://underscorejs.org/#reject">reject</a></li>
    1692. 

  1692.       <li><a href="http://underscorejs.org/#every">every (all)</a></li>
    1693. 

  1693.       <li><a href="http://underscorejs.org/#some">some (any)</a></li>
    1694. 

  1694.       <li><a href="http://underscorejs.org/#contains">contains (include)</a></li>
    1695. 

  1695.       <li><a href="http://underscorejs.org/#invoke">invoke</a></li>
    1696. 

  1696.       <li><a href="http://underscorejs.org/#max">max</a></li>
    1697. 

  1697.       <li><a href="http://underscorejs.org/#min">min</a></li>
    1698. 

  1698.       <li><a href="http://underscorejs.org/#sortBy">sortBy</a></li>
    1699. 

  1699.       <li><a href="http://underscorejs.org/#groupBy">groupBy</a></li>
    1700. 

  1700.       <li><a href="http://underscorejs.org/#shuffle">shuffle</a></li>
    1701. 

  1701.       <li><a href="http://underscorejs.org/#toArray">toArray</a></li>
    1702. 

  1702.       <li><a href="http://underscorejs.org/#size">size</a></li>
    1703. 

  1703.       <li><a href="http://underscorejs.org/#first">first (head, take)</a></li>
    1704. 

  1704.       <li><a href="http://underscorejs.org/#initial">initial</a></li>
    1705. 

  1705.       <li><a href="http://underscorejs.org/#rest">rest (tail)</a></li>
    1706. 

  1706.       <li><a href="http://underscorejs.org/#last">last</a></li>
    1707. 

  1707.       <li><a href="http://underscorejs.org/#without">without</a></li>
    1708. 

  1708.       <li><a href="http://underscorejs.org/#indexOf">indexOf</a></li>
    1709. 

  1709.       <li><a href="http://underscorejs.org/#lastIndexOf">lastIndexOf</a></li>
    1710. 

  1710.       <li><a href="http://underscorejs.org/#isEmpty">isEmpty</a></li>
    1711. 

  1711.       <li><a href="http://underscorejs.org/#chain">chain</a></li>
    1712. 

  1712.     </ul>
    1713. 

  1713. 

  1714. <pre>
    1715. 

  1715. books.each(function(book) {
    1716. 

  1716.   book.publish();
    1717. 

  1717. });
    1718. 

  1718. 

  1719. var titles = books.map(function(book) {
    1720. 

  1720.   return book.get("title");
    1721. 

  1721. });
    1722. 

  1722. 

  1723. var publishedBooks = books.filter(function(book) {
    1724. 

  1724.   return book.get("published") === true;
    1725. 

  1725. });
    1726. 

  1726. 

  1727. var alphabetical = books.sortBy(function(book) {
    1728. 

  1728.   return book.author.get("name").toLowerCase();
    1729. 

  1729. });
    1730. 

  1730. </pre>
    1731. 

  1731. 

  1732.     <p id="Collection-add">
    1733. 

  1733.       <b class="header">add</b><code>collection.add(models, [options])</code>
    1734. 

  1734.       <br />
    1735. 

  1735.       Add a model (or an array of models) to the collection, firing an <tt>"add"</tt>
    1736. 

  1736.       event. If a <a href="#Collection-model">model</a> property is defined, you may also pass
    1737. 

  1737.       raw attributes objects, and have them be vivified as instances of the model.
    1738. 

  1738.       Returns the added (or preexisting, if duplicate) models.
    1739. 

  1739.       Pass <tt>{at: index}</tt> to splice the model into the collection at the
    1740. 

  1740.       specified <tt>index</tt>. If you're adding models to the collection that are
    1741. 

  1741.       <i>already</i> in the collection, they'll be ignored, unless you pass
    1742. 

  1742.       <tt>{merge: true}</tt>, in which case their attributes will be merged
    1743. 

  1743.       into the corresponding models, firing any appropriate <tt>"change"</tt> events.
    1744. 

  1744.     </p>
    1745. 

  1745. 

  1746. <pre class="runnable">
    1747. 

  1747. var ships = new Backbone.Collection;
    1748. 

  1748. 

  1749. ships.on("add", function(ship) {
    1750. 

  1750.   alert("Ahoy " + ship.get("name") + "!");
    1751. 

  1751. });
    1752. 

  1752. 

  1753. ships.add([
    1754. 

  1754.   {name: "Flying Dutchman"},
    1755. 

  1755.   {name: "Black Pearl"}
    1756. 

  1756. ]);
    1757. 

  1757. </pre>
    1758. 

  1758. 

  1759.     <p class="warning">
    1760. 

  1760.       Note that adding the same model (a model with the same <tt>id</tt>) to
    1761. 

  1761.       a collection more than once <br /> is a no-op.
    1762. 

  1762.     </p>
    1763. 

  1763. 

  1764.     <p id="Collection-remove">
    1765. 

  1765.       <b class="header">remove</b><code>collection.remove(models, [options])</code>
    1766. 

  1766.       <br />
    1767. 

  1767.       Remove a model (or an array of models) from the collection, and returns them. 
    1768. 

  1768.       Fires a <tt>"remove"</tt> event, which you can use <tt>silent</tt> to suppress.
    1769. 

  1769.       The model's index before removal is available to listeners as
    1770. 

  1770.       <tt>options.index</tt>.
    1771. 

  1771.     </p>
    1772. 

  1772. 

  1773.     <p id="Collection-reset">
    1774. 

  1774.       <b class="header">reset</b><code>collection.reset([models], [options])</code>
    1775. 

  1775.       <br />
    1776. 

  1776.       Adding and removing models one at a time is all well and good, but sometimes
    1777. 

  1777.       you have so many models to change that you'd rather just update the collection
    1778. 

  1778.       in bulk. Use <b>reset</b> to replace a collection with a new list
    1779. 

  1779.       of models (or attribute hashes), triggering a single <tt>"reset"</tt> event
    1780. 

  1780.       at the end. Returns the newly-set models.
    1781. 

  1781.       For convenience, within a <tt>"reset"</tt> event, the list of any
    1782. 

  1782.       previous models is available as <tt>options.previousModels</tt>.
    1783. 

  1783.     </p>
    1784. 

  1784. 

  1785.     <p>
    1786. 

  1786.       Here's an example using <b>reset</b> to bootstrap a collection during initial page load,
    1787. 

  1787.       in a Rails application:
    1788. 

  1788.     </p>
    1789. 

  1789. 

  1790. <pre>
    1791. 

  1791. &lt;script&gt;
    1792. 

  1792.   var accounts = new Backbone.Collection;
    1793. 

  1793.   accounts.reset(&lt;%= @accounts.to_json %&gt;);
    1794. 

  1794. &lt;/script&gt;
    1795. 

  1795. </pre>
    1796. 

  1796. 

  1797.     <p>
    1798. 

  1798.       Calling <tt>collection.reset()</tt> without passing any models as arguments
    1799. 

  1799.       will empty the entire collection.
    1800. 

  1800.     </p>
    1801. 

  1801. 

  1802.     <p id="Collection-set">
    1803. 

  1803.       <b class="header">set</b><code>collection.set(models, [options])</code>
    1804. 

  1804.       <br />
    1805. 

  1805.       The <b>set</b> method performs a "smart" update of the collection
    1806. 

  1806.       with the passed list of models. If a model in the list isn't yet in the
    1807. 

  1807.       collection it will be added; if the model is already in the collection
    1808. 

  1808.       its attributes will be merged; and if the collection contains any models that
    1809. 

  1809.       <i>aren't</i> present in the list, they'll be removed. All of the appropriate
    1810. 

  1810.       <tt>"add"</tt>, <tt>"remove"</tt>, and <tt>"change"</tt> events are fired
    1811. 

  1811.       as this happens. Returns the touched models in the collection.
    1812. 

  1812.       If you'd like to customize the behavior, you can disable
    1813. 

  1813.       it with options: <tt>{add: false}</tt>, <tt>{remove: false}</tt>, or <tt>{merge: false}</tt>.
    1814. 

  1814.     </p>
    1815. 

  1815. 

  1816. <pre>
    1817. 

  1817. var vanHalen = new Backbone.Collection([eddie, alex, stone, roth]);
    1818. 

  1818. 

  1819. vanHalen.set([eddie, alex, stone, hagar]);
    1820. 

  1820. 

  1821. // Fires a "remove" event for roth, and an "add" event for "hagar".
    1822. 

  1822. // Updates any of stone, alex, and eddie's attributes that may have
    1823. 

  1823. // changed over the years.
    1824. 

  1824. </pre>
    1825. 

  1825. 

  1826.     <p id="Collection-get">
    1827. 

  1827.       <b class="header">get</b><code>collection.get(id)</code>
    1828. 

  1828.       <br />
    1829. 

  1829.       Get a model from a collection, specified by an <a href="#Model-id">id</a>,
    1830. 

  1830.       a <a href="#Model-cid">cid</a>, or by passing in a <b>model</b>.
    1831. 

  1831.     </p>
    1832. 

  1832. 

  1833. <pre>
    1834. 

  1834. var book = library.get(110);
    1835. 

  1835. </pre>
    1836. 

  1836. 

  1837.     <p id="Collection-at">
    1838. 

  1838.       <b class="header">at</b><code>collection.at(index)</code>
    1839. 

  1839.       <br />
    1840. 

  1840.       Get a model from a collection, specified by index. Useful if your collection
    1841. 

  1841.       is sorted, and if your collection isn't sorted, <b>at</b> will still
    1842. 

  1842.       retrieve models in insertion order.
    1843. 

  1843.     </p>
    1844. 

  1844. 

  1845.     <p id="Collection-push">
    1846. 

  1846.       <b class="header">push</b><code>collection.push(model, [options])</code>
    1847. 

  1847.       <br />
    1848. 

  1848.       Add a model at the end of a collection. Takes the same options as
    1849. 

  1849.       <a href="#Collection-add">add</a>.
    1850. 

  1850.     </p>
    1851. 

  1851. 

  1852.     <p id="Collection-pop">
    1853. 

  1853.       <b class="header">pop</b><code>collection.pop([options])</code>
    1854. 

  1854.       <br />
    1855. 

  1855.       Remove and return the last model from a collection. Takes the same options as
    1856. 

  1856.       <a href="#Collection-remove">remove</a>.
    1857. 

  1857.     </p>
    1858. 

  1858. 

  1859.     <p id="Collection-unshift">
    1860. 

  1860.       <b class="header">unshift</b><code>collection.unshift(model, [options])</code>
    1861. 

  1861.       <br />
    1862. 

  1862.       Add a model at the beginning of a collection. Takes the same options as
    1863. 

  1863.       <a href="#Collection-add">add</a>.
    1864. 

  1864.     </p>
    1865. 

  1865. 

  1866.     <p id="Collection-shift">
    1867. 

  1867.       <b class="header">shift</b><code>collection.shift([options])</code>
    1868. 

  1868.       <br />
    1869. 

  1869.       Remove and return the first model from a collection. Takes the same options as
    1870. 

  1870.       <a href="#Collection-remove">remove</a>.
    1871. 

  1871.     </p>
    1872. 

  1872. 

  1873.     <p id="Collection-slice">
    1874. 

  1874.       <b class="header">slice</b><code>collection.slice(begin, end)</code>
    1875. 

  1875.       <br />
    1876. 

  1876.       Return a shallow copy of this collection's models, using the same options as
    1877. 

  1877.       native
    1878. 

  1878.       <a href="https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Array/slice">Array#slice</a>.
    1879. 

  1879.     </p>
    1880. 

  1880. 

  1881.     <p id="Collection-length">
    1882. 

  1882.       <b class="header">length</b><code>collection.length</code>
    1883. 

  1883.       <br />
    1884. 

  1884.       Like an array, a Collection maintains a <tt>length</tt> property, counting
    1885. 

  1885.       the number of models it contains.
    1886. 

  1886.     </p>
    1887. 

  1887. 

  1888.     <p id="Collection-comparator">
    1889. 

  1889.       <b class="header">comparator</b><code>collection.comparator</code>
    1890. 

  1890.       <br />
    1891. 

  1891.       By default there is no <b>comparator</b> for a collection.
    1892. 

  1892.       If you define a comparator, it will be used to maintain
    1893. 

  1893.       the collection in sorted order. This means that as models are added,
    1894. 

  1894.       they are inserted at the correct index in <tt>collection.models</tt>.
    1895. 

  1895.       A comparator can be defined as a
    1896. 

  1896.       <a href="http://underscorejs.org/#sortBy">sortBy</a>
    1897. 

  1897.       (pass a function that takes a single argument),
    1898. 

  1898.       as a
    1899. 

  1899.       <a href="https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Array/sort">sort</a>
    1900. 

  1900.       (pass a comparator function that expects two arguments),
    1901. 

  1901.       or as a string indicating the attribute to sort by.
    1902. 

  1902.     </p>
    1903. 

  1903. 

  1904.     <p>
    1905. 

  1905.       "sortBy" comparator functions take a model and return a numeric or string
    1906. 

  1906.       value by which the model should be ordered relative to others.
    1907. 

  1907.       "sort" comparator functions take two models, and return <tt>-1</tt> if
    1908. 

  1908.       the first model should come before the second, <tt>0</tt> if they are of
    1909. 

  1909.       the same rank and <tt>1</tt> if the first model should come after.
    1910. 

  1910.     </p>
    1911. 

  1911. 

  1912.     <p>
    1913. 

  1913.       Note how even though all of the chapters in this example are added backwards,
    1914. 

  1914.       they come out in the proper order:
    1915. 

  1915.     </p>
    1916. 

  1916. 

  1917. <pre class="runnable">
    1918. 

  1918. var Chapter  = Backbone.Model;
    1919. 

  1919. var chapters = new Backbone.Collection;
    1920. 

  1920. 

  1921. chapters.comparator = 'page';
    1922. 

  1922. 

  1923. chapters.add(new Chapter({page: 9, title: "The End"}));
    1924. 

  1924. chapters.add(new Chapter({page: 5, title: "The Middle"}));
    1925. 

  1925. chapters.add(new Chapter({page: 1, title: "The Beginning"}));
    1926. 

  1926. 

  1927. alert(chapters.pluck('title'));
    1928. 

  1928. </pre>
    1929. 

  1929. 

  1930.     <p class="warning">
    1931. 

  1931.       Collections with a comparator will not automatically re-sort if you
    1932. 

  1932.       later change model attributes, so you may wish to call
    1933. 

  1933.       <tt>sort</tt> after changing model attributes that would affect the order.
    1934. 

  1934.     </p>
    1935. 

  1935. 

  1936.     <p id="Collection-sort">
    1937. 

  1937.       <b class="header">sort</b><code>collection.sort([options])</code>
    1938. 

  1938.       <br />
    1939. 

  1939.       Force a collection to re-sort itself. You don't need to call this under
    1940. 

  1940.       normal circumstances, as a collection with a <a href="#Collection-comparator">comparator</a>
    1941. 

  1941.       will sort itself whenever a model is added. To disable sorting when adding
    1942. 

  1942.       a model, pass <tt>{sort: false}</tt> to <tt>add</tt>. Calling <b>sort</b>
    1943. 

  1943.       triggers a <tt>"sort"</tt> event on the collection.
    1944. 

  1944.     </p>
    1945. 

  1945. 

  1946.     <p id="Collection-pluck">
    1947. 

  1947.       <b class="header">pluck</b><code>collection.pluck(attribute)</code>
    1948. 

  1948.       <br />
    1949. 

  1949.       Pluck an attribute from each model in the collection. Equivalent to calling
    1950. 

  1950.       <tt>map</tt> and returning a single attribute from the iterator.
    1951. 

  1951.     </p>
    1952. 

  1952. 

  1953. <pre class="runnable">
    1954. 

  1954. var stooges = new Backbone.Collection([
    1955. 

  1955.   {name: "Curly"},
    1956. 

  1956.   {name: "Larry"},
    1957. 

  1957.   {name: "Moe"}
    1958. 

  1958. ]);
    1959. 

  1959. 

  1960. var names = stooges.pluck("name");
    1961. 

  1961. 

  1962. alert(JSON.stringify(names));
    1963. 

  1963. </pre>
    1964. 

  1964. 

  1965.     <p id="Collection-where">
    1966. 

  1966.       <b class="header">where</b><code>collection.where(attributes)</code>
    1967. 

  1967.       <br />
    1968. 

  1968.       Return an array of all the models in a collection that match the
    1969. 

  1969.       passed <b>attributes</b>. Useful for simple cases of <tt>filter</tt>.
    1970. 

  1970.     </p>
    1971. 

  1971. 

  1972. <pre class="runnable">
    1973. 

  1973. var friends = new Backbone.Collection([
    1974. 

  1974.   {name: "Athos",      job: "Musketeer"},
    1975. 

  1975.   {name: "Porthos",    job: "Musketeer"},
    1976. 

  1976.   {name: "Aramis",     job: "Musketeer"},
    1977. 

  1977.   {name: "d'Artagnan", job: "Guard"},
    1978. 

  1978. ]);
    1979. 

  1979. 

  1980. var musketeers = friends.where({job: "Musketeer"});
    1981. 

  1981. 

  1982. alert(musketeers.length);
    1983. 

  1983. </pre>
    1984. 

  1984. 

  1985.     <p id="Collection-findWhere">
    1986. 

  1986.       <b class="header">findWhere</b><code>collection.findWhere(attributes)</code>
    1987. 

  1987.       <br />
    1988. 

  1988.       Just like <a href="#Collection-where">where</a>, but directly returns only
    1989. 

  1989.       the first model in the collection that matches the passed <b>attributes</b>.
    1990. 

  1990.     </p>
    1991. 

  1991. 

  1992.     <p id="Collection-url">
    1993. 

  1993.       <b class="header">url</b><code>collection.url or collection.url()</code>
    1994. 

  1994.       <br />
    1995. 

  1995.       Set the <b>url</b> property (or function) on a collection to reference
    1996. 

  1996.       its location on the server. Models within the collection will use <b>url</b>
    1997. 

  1997.       to construct URLs of their own.
    1998. 

  1998.     </p>
    1999. 

  1999. 

  2000. <pre>
    2001. 

  2001. var Notes = Backbone.Collection.extend({
    2002. 

  2002.   url: '/notes'
    2003. 

  2003. });
    2004. 

  2004. 

  2005. // Or, something more sophisticated:
    2006. 

  2006. 

  2007. var Notes = Backbone.Collection.extend({
    2008. 

  2008.   url: function() {
    2009. 

  2009.     return this.document.url() + '/notes';
    2010. 

  2010.   }
    2011. 

  2011. });
    2012. 

  2012. </pre>
    2013. 

  2013. 

  2014.     <p id="Collection-parse">
    2015. 

  2015.       <b class="header">parse</b><code>collection.parse(response, options)</code>
    2016. 

  2016.       <br />
    2017. 

  2017.       <b>parse</b> is called by Backbone whenever a collection's models are
    2018. 

  2018.       returned by the server, in <a href="#Collection-fetch">fetch</a>.
    2019. 

  2019.       The function is passed the raw <tt>response</tt> object, and should return
    2020. 

  2020.       the array of model attributes to be <a href="#Collection-add">added</a>
    2021. 

  2021.       to the collection. The default implementation is a no-op, simply passing
    2022. 

  2022.       through the JSON response. Override this if you need to work with a
    2023. 

  2023.       preexisting API, or better namespace your responses.
    2024. 

  2024.     </p>
    2025. 

  2025. 

  2026. <pre>
    2027. 

  2027. var Tweets = Backbone.Collection.extend({
    2028. 

  2028.   // The Twitter Search API returns tweets under "results".
    2029. 

  2029.   parse: function(response) {
    2030. 

  2030.     return response.results;
    2031. 

  2031.   }
    2032. 

  2032. });
    2033. 

  2033. </pre>
    2034. 

  2034. 

  2035.     <p id="Collection-clone">
    2036. 

  2036.       <b class="header">clone</b><code>collection.clone()</code>
    2037. 

  2037.       <br />
    2038. 

  2038.       Returns a new instance of the collection with an identical list of models.
    2039. 

  2039.     </p>
    2040. 

  2040. 

  2041.     <p id="Collection-fetch">
    2042. 

  2042.       <b class="header">fetch</b><code>collection.fetch([options])</code>
    2043. 

  2043.       <br />
    2044. 

  2044.       Fetch the default set of models for this collection from the server,
    2045. 

  2045.       <a href="#Collection-set">setting</a> them on the collection when they arrive.
    2046. 

  2046.       The <b>options</b> hash takes <tt>success</tt> and <tt>error</tt> callbacks
    2047. 

  2047.       which will both be passed <tt>(collection, response, options)</tt> as arguments.
    2048. 

  2048.       When the model data returns from the server, it uses <a href="#Collection-set">set</a>
    2049. 

  2049.       to (intelligently) merge the fetched models, unless you pass <tt>{reset: true}</tt>,
    2050. 

  2050.       in which case the collection will be (efficiently) <a href="#Collection-reset">reset</a>.
    2051. 

  2051.       Delegates to <a href="#Sync">Backbone.sync</a>
    2052. 

  2052.       under the covers for custom persistence strategies and returns a
    2053. 

  2053.       <a href="http://api.jquery.com/jQuery.ajax/#jqXHR">jqXHR</a>.
    2054. 

  2054.       The server handler for <b>fetch</b> requests should return a JSON array of
    2055. 

  2055.       models.
    2056. 

  2056.     </p>
    2057. 

  2057. 

  2058. <pre class="runnable">
    2059. 

  2059. Backbone.sync = function(method, model) {
    2060. 

  2060.   alert(method + ": " + model.url);
    2061. 

  2061. };
    2062. 

  2062. 

  2063. var accounts = new Backbone.Collection;
    2064. 

  2064. accounts.url = '/accounts';
    2065. 

  2065. 

  2066. accounts.fetch();
    2067. 

  2067. </pre>
    2068. 

  2068. 

  2069.     <p>
    2070. 

  2070.       The behavior of <b>fetch</b> can be customized by using the available
    2071. 

  2071.       <a href="#Collection-set">set</a> options. For example, to fetch a
    2072. 

  2072.       collection, getting an <tt>"add"</tt> event for every new model, and
    2073. 

  2073.       a <tt>"change"</tt> event for every changed existing model, without
    2074. 

  2074.       removing anything: <tt>collection.fetch({remove: false})</tt>
    2075. 

  2075.     </p>
    2076. 

  2076. 

  2077.     <p>
    2078. 

  2078.       <b>jQuery.ajax</b> options can also be passed directly as <b>fetch</b> options,
    2079. 

  2079.       so to fetch a specific page of a paginated collection:
    2080. 

  2080.       <tt>Documents.fetch({data: {page: 3}})</tt>
    2081. 

  2081.     </p>
    2082. 

  2082. 

  2083.     <p>
    2084. 

  2084.       Note that <b>fetch</b> should not be used to populate collections on
    2085. 

  2085.       page load &mdash; all models needed at load time should already be
    2086. 

  2086.       <a href="#FAQ-bootstrap">bootstrapped</a> in to place. <b>fetch</b> is
    2087. 

  2087.       intended for lazily-loading models for interfaces that are not needed
    2088. 

  2088.       immediately: for example, documents with collections of notes that may be
    2089. 

  2089.       toggled open and closed.
    2090. 

  2090.     </p>
    2091. 

  2091. 

  2092.     <p id="Collection-create">
    2093. 

  2093.       <b class="header">create</b><code>collection.create(attributes, [options])</code>
    2094. 

  2094.       <br />
    2095. 

  2095.       Convenience to create a new instance of a model within a collection.
    2096. 

  2096.       Equivalent to instantiating a model with a hash of attributes,
    2097. 

  2097.       saving the model to the server, and adding the model to the set after being
    2098. 

  2098.       successfully created. Returns the new model. If client-side validation
    2099. 

  2099.       failed, the model will be unsaved, with validation errors.
    2100. 

  2100.       In order for this to work, you should set the
    2101. 

  2101.       <a href="#Collection-model">model</a> property of the collection.
    2102. 

  2102.       The <b>create</b> method can accept either an attributes hash or an
    2103. 

  2103.       existing, unsaved model object.
    2104. 

  2104.     </p>
    2105. 

  2105. 

  2106.     <p>
    2107. 

  2107.       Creating a model will cause an immediate <tt>"add"</tt> event to be
    2108. 

  2108.       triggered on the collection, a <tt>"request"</tt> event as the new model is
    2109. 

  2109.       sent to the server, as well as a <tt>"sync"</tt> event, once the
    2110. 

  2110.       server has responded with the successful creation of the model. Pass <tt>{wait: true}</tt>
    2111. 

  2111.       if you'd like to wait for the server before adding the new model to the collection.
    2112. 

  2112.     </p>
    2113. 

  2113. 

  2114. <pre>
    2115. 

  2115. var Library = Backbone.Collection.extend({
    2116. 

  2116.   model: Book
    2117. 

  2117. });
    2118. 

  2118. 

  2119. var nypl = new Library;
    2120. 

  2120. 

  2121. var othello = nypl.create({
    2122. 

  2122.   title: "Othello",
    2123. 

  2123.   author: "William Shakespeare"
    2124. 

  2124. });
    2125. 

  2125. </pre>
    2126. 

  2126. 

  2127.     <h2 id="Router">Backbone.Router</h2>
    2128. 

  2128. 

  2129.     <p>
    2130. 

  2130.       Web applications often provide linkable, bookmarkable, shareable URLs for
    2131. 

  2131.       important locations in the app. Until recently, hash fragments
    2132. 

  2132.       (<tt>#page</tt>) were used to provide these permalinks, but with the
    2133. 

  2133.       arrival of the History API, it's now possible to use standard URLs (<tt>/page</tt>).
    2134. 

  2134.       <b>Backbone.Router</b> provides methods for routing client-side pages, and
    2135. 

  2135.       connecting them to actions and events. For browsers which don't yet support
    2136. 

  2136.       the History API, the Router handles graceful fallback and transparent
    2137. 

  2137.       translation to the fragment version of the URL.
    2138. 

  2138.     </p>
    2139. 

  2139. 

  2140.     <p>
    2141. 

  2141.       During page load, after your application has finished creating all of its routers,
    2142. 

  2142.       be sure to call <tt>Backbone.history.start()</tt>, or
    2143. 

  2143.       <tt>Backbone.history.start({pushState: true})</tt> to route the initial URL.
    2144. 

  2144.     </p>
    2145. 

  2145. 

  2146.     <p id="Router-extend">
    2147. 

  2147.       <b class="header">extend</b><code>Backbone.Router.extend(properties, [classProperties])</code>
    2148. 

  2148.       <br />
    2149. 

  2149.       Get started by creating a custom router class. Define actions that are
    2150. 

  2150.       triggered when certain URL fragments are
    2151. 

  2151.       matched, and provide a <a href="#Router-routes">routes</a> hash
    2152. 

  2152.       that pairs routes to actions. Note that you'll want to avoid using a
    2153. 

  2153.       leading slash in your route definitions:
    2154. 

  2154.     </p>
    2155. 

  2155. 

  2156. <pre>
    2157. 

  2157. var Workspace = Backbone.Router.extend({
    2158. 

  2158. 

  2159.   routes: {
    2160. 

  2160.     "help":                 "help",    // #help
    2161. 

  2161.     "search/:query":        "search",  // #search/kiwis
    2162. 

  2162.     "search/:query/p:page": "search"   // #search/kiwis/p7
    2163. 

  2163.   },
    2164. 

  2164. 

  2165.   help: function() {
    2166. 

  2166.     ...
    2167. 

  2167.   },
    2168. 

  2168. 

  2169.   search: function(query, page) {
    2170. 

  2170.     ...
    2171. 

  2171.   }
    2172. 

  2172. 

  2173. });
    2174. 

  2174. </pre>
    2175. 

  2175. 

  2176.     <p id="Router-routes">
    2177. 

  2177.       <b class="header">routes</b><code>router.routes</code>
    2178. 

  2178.       <br />
    2179. 

  2179.       The routes hash maps URLs with parameters to functions on your router
    2180. 

  2180.       (or just direct function definitions, if you prefer),
    2181. 

  2181.       similar to the <a href="#View">View</a>'s <a href="#View-delegateEvents">events hash</a>.
    2182. 

  2182.       Routes can contain parameter parts, <tt>:param</tt>, which match a single URL
    2183. 

  2183.       component between slashes; and splat parts <tt>*splat</tt>, which can match
    2184. 

  2184.       any number of URL components. Part of a route can be made optional by
    2185. 

  2185.       surrounding it in parentheses <tt>(/:optional)</tt>.
    2186. 

  2186.     </p>
    2187. 

  2187. 

  2188.     <p>
    2189. 

  2189.       For example, a route of <tt>"search/:query/p:page"</tt> will match
    2190. 

  2190.       a fragment of <tt>#search/obama/p2</tt>, passing <tt>"obama"</tt>
    2191. 

  2191.       and <tt>"2"</tt> to the action.
    2192. 

  2192.     </p>
    2193. 

  2193. 

  2194.     <p>
    2195. 

  2195.       A route of <tt>"file/*path"</tt> will match
    2196. 

  2196.       <tt>#file/nested/folder/file.txt</tt>, passing
    2197. 

  2197.       <tt>"nested/folder/file.txt"</tt> to the action.
    2198. 

  2198.     </p>
    2199. 

  2199. 

  2200.     <p>
    2201. 

  2201.       A route of <tt>"docs/:section(/:subsection)"</tt> will match
    2202. 

  2202.       <tt>#docs/faq</tt> and <tt>#docs/faq/installing</tt>, passing
    2203. 

  2203.       <tt>"faq"</tt> to the action in the first case, and passing <tt>"faq"</tt>
    2204. 

  2204.       and <tt>"installing"</tt> to the action in the second.
    2205. 

  2205.     </p>
    2206. 

  2206. 

  2207.     <p>
    2208. 

  2208.       Trailing slashes are treated as part of the URL, and (correctly) treated
    2209. 

  2209.       as a unique route when accessed. <tt>docs</tt> and <tt>docs/</tt> will fire
    2210. 

  2210.       different callbacks. If you can't avoid generating both types of URLs, you
    2211. 

  2211.       can define a <tt>"docs(/)"</tt> matcher to capture both cases.
    2212. 

  2212.     </p>
    2213. 

  2213. 

  2214.     <p>
    2215. 

  2215.       When the visitor presses the back button, or enters a URL, and a particular
    2216. 

  2216.       route is matched, the name of the action will be fired as an
    2217. 

  2217.       <a href="#Events">event</a>, so that other objects can listen to the router,
    2218. 

  2218.       and be notified. In the following example, visiting <tt>#help/uploading</tt>
    2219. 

  2219.       will fire a <tt>route:help</tt> event from the router.
    2220. 

  2220.     </p>
    2221. 

  2221. 

  2222. <pre>
    2223. 

  2223. routes: {
    2224. 

  2224.   "help/:page":         "help",
    2225. 

  2225.   "download/*path":     "download",
    2226. 

  2226.   "folder/:name":       "openFolder",
    2227. 

  2227.   "folder/:name-:mode": "openFolder"
    2228. 

  2228. }
    2229. 

  2229. </pre>
    2230. 

  2230. 

  2231. <pre>
    2232. 

  2232. router.on("route:help", function(page) {
    2233. 

  2233.   ...
    2234. 

  2234. });
    2235. 

  2235. </pre>
    2236. 

  2236. 

  2237.     <p id="Router-constructor">
    2238. 

  2238.       <b class="header">constructor / initialize</b><code>new Router([options])</code>
    2239. 

  2239.       <br />
    2240. 

  2240.       When creating a new router, you may pass its
    2241. 

  2241.       <a href="#Router-routes">routes</a> hash directly as an option, if you
    2242. 

  2242.       choose. All <tt>options</tt> will also be passed to your <tt>initialize</tt>
    2243. 

  2243.       function, if defined.
    2244. 

  2244.     </p>
    2245. 

  2245. 

  2246.     <p id="Router-route">
    2247. 

  2247.       <b class="header">route</b><code>router.route(route, name, [callback])</code>
    2248. 

  2248.       <br />
    2249. 

  2249.       Manually create a route for the router, The <tt>route</tt> argument may
    2250. 

  2250.       be a <a href="#Router-routes">routing string</a> or regular expression.
    2251. 

  2251.       Each matching capture from the route or regular expression will be passed as
    2252. 

  2252.       an argument to the callback. The <tt>name</tt> argument will be triggered as
    2253. 

  2253.       a <tt>"route:name"</tt> event whenever the route is matched.  If the
    2254. 

  2254.       <tt>callback</tt> argument is omitted <tt>router[name]</tt> will be used
    2255. 

  2255.       instead. Routes added later may override previously declared routes.
    2256. 

  2256.     </p>
    2257. 

  2257. 

  2258. <pre>
    2259. 

  2259. initialize: function(options) {
    2260. 

  2260. 

  2261.   // Matches #page/10, passing "10"
    2262. 

  2262.   this.route("page/:number", "page", function(number){ ... });
    2263. 

  2263. 

  2264.   // Matches /117-a/b/c/open, passing "117-a/b/c" to this.open
    2265. 

  2265.   this.route(/^(.*?)\/open$/, "open");
    2266. 

  2266. 

  2267. },
    2268. 

  2268. 

  2269. open: function(id) { ... }
    2270. 

  2270. </pre>
    2271. 

  2271. 

  2272.     <p id="Router-navigate">
    2273. 

  2273.       <b class="header">navigate</b><code>router.navigate(fragment, [options])</code>
    2274. 

  2274.       <br />
    2275. 

  2275.       Whenever you reach a point in your application that you'd like to save
    2276. 

  2276.       as a URL, call <b>navigate</b> in order to update the URL.
    2277. 

  2277.       If you wish to also call the route function, set the <b>trigger</b>
    2278. 

  2278.       option to <tt>true</tt>.
    2279. 

  2279.       To update the URL without creating an entry in the browser's history,
    2280. 

  2280.       set the <b>replace</b> option to <tt>true</tt>.
    2281. 

  2281.     </p>
    2282. 

  2282. 

  2283. <pre>
    2284. 

  2284. openPage: function(pageNumber) {
    2285. 

  2285.   this.document.pages.at(pageNumber).open();
    2286. 

  2286.   this.navigate("page/" + pageNumber);
    2287. 

  2287. }
    2288. 

  2288. 

  2289. # Or ...
    2290. 

  2290. 

  2291. app.navigate("help/troubleshooting", {trigger: true});
    2292. 

  2292. 

  2293. # Or ...
    2294. 

  2294. 

  2295. app.navigate("help/troubleshooting", {trigger: true, replace: true});
    2296. 

  2296. </pre>
    2297. 

  2297. 

  2298.     <h2 id="History">Backbone.history</h2>
    2299. 

  2299. 

  2300.     <p>
    2301. 

  2301.       <b>History</b> serves as a global router (per frame) to handle <tt>hashchange</tt>
    2302. 

  2302.       events or <tt>pushState</tt>, match the appropriate route, and trigger callbacks.
    2303. 

  2303.       You shouldn't ever have to create one of these yourself since <tt>Backbone.history</tt>
    2304. 

  2304.       already contains one.
    2305. 

  2305.     </p>
    2306. 

  2306. 

  2307.     <p>
    2308. 

  2308.       <b>pushState</b> support exists on a purely opt-in basis in Backbone.
    2309. 

  2309.       Older browsers that don't support <tt>pushState</tt> will continue to use
    2310. 

  2310.       hash-based URL fragments, and if a hash URL is visited by a
    2311. 

  2311.       <tt>pushState</tt>-capable browser, it will be transparently upgraded to
    2312. 

  2312.       the true URL. Note that using real URLs requires your web server to be
    2313. 

  2313.       able to correctly render those pages, so back-end changes are required
    2314. 

  2314.       as well. For example, if you have a route of <tt>/documents/100</tt>,
    2315. 

  2315.       your web server must be able to serve that page, if the browser
    2316. 

  2316.       visits that URL directly. For full search-engine crawlability, it's best to
    2317. 

  2317.       have the server generate the complete HTML for the page ... but if it's a web
    2318. 

  2318.       application, just rendering the same content you would have for the root URL,
    2319. 

  2319.       and filling in the rest with Backbone Views and JavaScript works fine.
    2320. 

  2320.     </p>
    2321. 

  2321. 

  2322.     <p id="History-start">
    2323. 

  2323.       <b class="header">start</b><code>Backbone.history.start([options])</code>
    2324. 

  2324.       <br />
    2325. 

  2325.       When all of your <a href="#Router">Routers</a> have been created,
    2326. 

  2326.       and all of the routes are set up properly, call <tt>Backbone.history.start()</tt>
    2327. 

  2327.       to begin monitoring <tt>hashchange</tt> events, and dispatching routes.
    2328. 

  2328.     </p>
    2329. 

  2329. 

  2330.     <p>
    2331. 

  2331.       To indicate that you'd like to use HTML5 <tt>pushState</tt> support in
    2332. 

  2332.       your application, use <tt>Backbone.history.start({pushState: true})</tt>.
    2333. 

  2333.       If you'd like to use <tt>pushState</tt>, but have browsers that don't support
    2334. 

  2334.       it natively use full page refreshes instead, you can add
    2335. 

  2335.       <tt>{hashChange: false}</tt> to the options.
    2336. 

  2336.     </p>
    2337. 

  2337. 

  2338.     <p>
    2339. 

  2339.       If your application is not being served from the root url <tt>/</tt> of your
    2340. 

  2340.       domain, be sure to tell History where the root really is, as an option:
    2341. 

  2341.       <tt>Backbone.history.start({pushState: true, root: "/public/search/"})</tt>
    2342. 

  2342.     </p>
    2343. 

  2343. 

  2344.     <p>
    2345. 

  2345.       When called, if a route succeeds with a match for the current URL,
    2346. 

  2346.       <tt>Backbone.history.start()</tt> returns <tt>true</tt>. If no defined
    2347. 

  2347.       route matches the current URL, it returns <tt>false</tt>.
    2348. 

  2348.     </p>
    2349. 

  2349. 

  2350.     <p>
    2351. 

  2351.       If the server has already rendered the entire page, and you don't want the
    2352. 

  2352.       initial route to trigger when starting History, pass <tt>silent: true</tt>.
    2353. 

  2353.     </p>
    2354. 

  2354. 

  2355.     <p>
    2356. 

  2356.       Because hash-based history in Internet Explorer relies on an
    2357. 

  2357.       <tt>&lt;iframe&gt;</tt>, be sure to only call <tt>start()</tt> after the DOM
    2358. 

  2358.       is ready.
    2359. 

  2359.     </p>
    2360. 

  2360. 

  2361. <pre>
    2362. 

  2362. $(function(){
    2363. 

  2363.   new WorkspaceRouter();
    2364. 

  2364.   new HelpPaneRouter();
    2365. 

  2365.   Backbone.history.start({pushState: true});
    2366. 

  2366. });
    2367. 

  2367. </pre>
    2368. 

  2368. 

  2369.     <h2 id="Sync">Backbone.sync</h2>
    2370. 

  2370. 

  2371.     <p>
    2372. 

  2372.       <b>Backbone.sync</b> is the function that Backbone calls every time it
    2373. 

  2373.       attempts to read or save a model to the server. By default, it uses
    2374. 

  2374.       <tt>jQuery.ajax</tt> to make a RESTful JSON request and returns a
    2375. 

  2375.       <a href="http://api.jquery.com/jQuery.ajax/#jqXHR">jqXHR</a>. You can override
    2376. 

  2376.       it in order to use a different persistence strategy, such as WebSockets,
    2377. 

  2377.       XML transport, or Local Storage.
    2378. 

  2378.     </p>
    2379. 

  2379. 

  2380.     <p>
    2381. 

  2381.       The method signature of <b>Backbone.sync</b> is <tt>sync(method, model, [options])</tt>
    2382. 

  2382.     </p>
    2383. 

  2383. 

  2384.     <ul>
    2385. 

  2385.       <li><b>method</b> – the CRUD method (<tt>"create"</tt>, <tt>"read"</tt>, <tt>"update"</tt>, or <tt>"delete"</tt>)</li>
    2386. 

  2386.       <li><b>model</b> – the model to be saved (or collection to be read)</li>
    2387. 

  2387.       <li><b>options</b> – success and error callbacks, and all other jQuery request options</li>
    2388. 

  2388.     </ul>
    2389. 

  2389. 

  2390.     <p>
    2391. 

  2391.       With the default implementation, when <b>Backbone.sync</b> sends up a request to save
    2392. 

  2392.       a model, its attributes will be passed, serialized as JSON, and sent in the HTTP body
    2393. 

  2393.       with content-type <tt>application/json</tt>. When returning a JSON response,
    2394. 

  2394.       send down the attributes of the  model that have been changed by the server, and need
    2395. 

  2395.       to be updated on the client. When responding to a <tt>"read"</tt> request from a collection
    2396. 

  2396.       (<a href="#Collection-fetch">Collection#fetch</a>), send down an array
    2397. 

  2397.       of model attribute objects.
    2398. 

  2398.     </p>
    2399. 

  2399. 

  2400.     <p>
    2401. 

  2401.       Whenever a model or collection begins a <b>sync</b> with the server, a
    2402. 

  2402.       <tt>"request"</tt> event is emitted. If the request completes successfully
    2403. 

  2403.       you'll get a <tt>"sync"</tt> event, and an <tt>"error"</tt> event if not.
    2404. 

  2404.     </p>
    2405. 

  2405. 

  2406.     <p>
    2407. 

  2407.       The <b>sync</b> function may be overriden globally as <tt>Backbone.sync</tt>,
    2408. 

  2408.       or at a finer-grained level, by adding a <tt>sync</tt> function to a Backbone
    2409. 

  2409.       collection or to an individual model.
    2410. 

  2410.     </p>
    2411. 

  2411. 

  2412.     <p>
    2413. 

  2413.       The default <b>sync</b> handler maps CRUD to REST like so:
    2414. 

  2414.     </p>
    2415. 

  2415. 

  2416.     <ul>
    2417. 

  2417.       <li><b>create &rarr; POST &nbsp; </b><tt>/collection</tt></li>
    2418. 

  2418.       <li><b>read &rarr; GET &nbsp; </b><tt>/collection[/id]</tt></li>
    2419. 

  2419.       <li><b>update &rarr; PUT &nbsp; </b><tt>/collection/id</tt></li>
    2420. 

  2420.       <li><b>delete &rarr; DELETE &nbsp; </b><tt>/collection/id</tt></li>
    2421. 

  2421.     </ul>
    2422. 

  2422. 

  2423.     <p>
    2424. 

  2424.       As an example, a Rails handler responding to an <tt>"update"</tt> call from
    2425. 

  2425.       <tt>Backbone</tt> might look like this: <i>(In real code, never use
    2426. 

  2426.       </i><tt>update_attributes</tt><i> blindly, and always whitelist the attributes
    2427. 

  2427.       you allow to be changed.)</i>
    2428. 

  2428.     </p>
    2429. 

  2429. 

  2430. <pre>
    2431. 

  2431. def update
    2432. 

  2432.   account = Account.find params[:id]
    2433. 

  2433.   account.update_attributes params
    2434. 

  2434.   render :json => account
    2435. 

  2435. end
    2436. 

  2436. </pre>
    2437. 

  2437. 

  2438.     <p>
    2439. 

  2439.       One more tip for integrating Rails versions prior to 3.1 is to disable
    2440. 

  2440.       the default namespacing for <tt>to_json</tt> calls on models by setting
    2441. 

  2441.       <tt>ActiveRecord::Base.include_root_in_json = false</tt>
    2442. 

  2442.     </p>
    2443. 

  2443. 

  2444.     <p id="Sync-ajax">
    2445. 

  2445.       <b class="header">ajax</b><code>Backbone.ajax = function(request) { ... };</code>
    2446. 

  2446.       <br />
    2447. 

  2447.       If you want to use a custom AJAX function, or your endpoint doesn't support
    2448. 

  2448.       the <a href="http://api.jquery.com/jQuery.ajax/">jQuery.ajax</a> API
    2449. 

  2449.       and you need to tweak things, you can do so by setting <tt>Backbone.ajax</tt>.
    2450. 

  2450.     </p>
    2451. 

  2451. 

  2452.     <p id="Sync-emulateHTTP">
    2453. 

  2453.       <b class="header">emulateHTTP</b><code>Backbone.emulateHTTP = true</code>
    2454. 

  2454.       <br />
    2455. 

  2455.       If you want to work with a legacy web server that doesn't support Backbone's
    2456. 

  2456.       default REST/HTTP approach, you may choose to turn on <tt>Backbone.emulateHTTP</tt>.
    2457. 

  2457.       Setting this option will fake <tt>PUT</tt> and <tt>DELETE</tt> requests with
    2458. 

  2458.       a HTTP <tt>POST</tt>, setting the <tt>X-HTTP-Method-Override</tt> header
    2459. 

  2459.       with the true method. If <tt>emulateJSON</tt> is also on, the true method
    2460. 

  2460.       will be passed as an additional <tt>_method</tt> parameter.
    2461. 

  2461.     </p>
    2462. 

  2462. 

  2463. <pre>
    2464. 

  2464. Backbone.emulateHTTP = true;
    2465. 

  2465. 

  2466. model.save();  // POST to "/collection/id", with "_method=PUT" + header.
    2467. 

  2467. </pre>
    2468. 

  2468. 

  2469.     <p id="Sync-emulateJSON">
    2470. 

  2470.       <b class="header">emulateJSON</b><code>Backbone.emulateJSON = true</code>
    2471. 

  2471.       <br />
    2472. 

  2472.       If you're working with a legacy web server that can't handle requests
    2473. 

  2473.       encoded as <tt>application/json</tt>, setting <tt>Backbone.emulateJSON = true;</tt>
    2474. 

  2474.       will cause the JSON to be serialized under a <tt>model</tt> parameter, and
    2475. 

  2475.       the request to be made with a <tt>application/x-www-form-urlencoded</tt>
    2476. 

  2476.       MIME type, as if from an HTML form.
    2477. 

  2477.     </p>
    2478. 

  2478. 

  2479.     <h2 id="View">Backbone.View</h2>
    2480. 

  2480. 

  2481.     <p>
    2482. 

  2482.       Backbone views are almost more convention than they are code &mdash; they
    2483. 

  2483.       don't determine anything about your HTML or CSS for you, and can be used
    2484. 

  2484.       with any JavaScript templating library.
    2485. 

  2485.       The general idea is to organize your interface into logical views,
    2486. 

  2486.       backed by models, each of which can be updated independently when the
    2487. 

  2487.       model changes, without having to redraw the page. Instead of digging into
    2488. 

  2488.       a JSON object, looking up an element in the DOM, and updating the HTML by hand,
    2489. 

  2489.       you can bind your view's <tt>render</tt> function to the model's <tt>"change"</tt>
    2490. 

  2490.       event &mdash; and now everywhere that
    2491. 

  2491.       model data is displayed in the UI, it is always immediately up to date.
    2492. 

  2492.     </p>
    2493. 

  2493. 

  2494.     <p id="View-extend">
    2495. 

  2495.       <b class="header">extend</b><code>Backbone.View.extend(properties, [classProperties])</code>
    2496. 

  2496.       <br />
    2497. 

  2497.       Get started with views by creating a custom view class. You'll want to
    2498. 

  2498.       override the <a href="#View-render">render</a> function, specify your
    2499. 

  2499.       declarative <a href="#View-delegateEvents">events</a>, and perhaps the
    2500. 

  2500.       <tt>tagName</tt>, <tt>className</tt>, or <tt>id</tt> of the View's root
    2501. 

  2501.       element.
    2502. 

  2502.     </p>
    2503. 

  2503. 

  2504. <pre>
    2505. 

  2505. var DocumentRow = Backbone.View.extend({
    2506. 

  2506. 

  2507.   tagName: "li",
    2508. 

  2508. 

  2509.   className: "document-row",
    2510. 

  2510. 

  2511.   events: {
    2512. 

  2512.     "click .icon":          "open",
    2513. 

  2513.     "click .button.edit":   "openEditDialog",
    2514. 

  2514.     "click .button.delete": "destroy"
    2515. 

  2515.   },
    2516. 

  2516. 

  2517.   initialize: function() {
    2518. 

  2518.     this.listenTo(this.model, "change", this.render);
    2519. 

  2519.   },
    2520. 

  2520. 

  2521.   render: function() {
    2522. 

  2522.     ...
    2523. 

  2523.   }
    2524. 

  2524. 

  2525. });
    2526. 

  2526. </pre>
    2527. 

  2527. 

  2528.     <p>
    2529. 

  2529.       Properties like <tt>tagName</tt>, <tt>id</tt>, <tt>className</tt>,
    2530. 

  2530.       <tt>el</tt>, and <tt>events</tt> may also be defined as a function, if
    2531. 

  2531.       you want to wait to define them until runtime.
    2532. 

  2532.     </p>
    2533. 

  2533. 

  2534.     <p id="View-constructor">
    2535. 

  2535.       <b class="header">constructor / initialize</b><code>new View([options])</code>
    2536. 

  2536.       <br />
    2537. 

  2537.       When creating a new View, the options you pass &mdash; after being merged
    2538. 

  2538.       into any default options already present on the view &mdash;
    2539. 

  2539.       are attached to the view as <tt>this.options</tt> for future reference.
    2540. 

  2540.       There are several special
    2541. 

  2541.       options that, if passed, will be attached directly to the view:
    2542. 

  2542.       <tt>model</tt>, <tt>collection</tt>,
    2543. 

  2543.       <tt>el</tt>, <tt>id</tt>, <tt>className</tt>, <tt>tagName</tt> and <tt>attributes</tt>.
    2544. 

  2544.       If the view defines an <b>initialize</b> function, it will be called when
    2545. 

  2545.       the view is first created. If you'd like to create a view that references
    2546. 

  2546.       an element <i>already</i> in the DOM, pass in the element as an option:
    2547. 

  2547.       <tt>new View({el: existingElement})</tt>
    2548. 

  2548.     </p>
    2549. 

  2549. 

  2550. <pre>
    2551. 

  2551. var doc = documents.first();
    2552. 

  2552. 

  2553. new DocumentRow({
    2554. 

  2554.   model: doc,
    2555. 

  2555.   id: "document-row-" + doc.id
    2556. 

  2556. });
    2557. 

  2557. </pre>
    2558. 

  2558. 

  2559.     <p id="View-el">
    2560. 

  2560.       <b class="header">el</b><code>view.el</code>
    2561. 

  2561.       <br />
    2562. 

  2562.       All views have a DOM element at all times (the <b>el</b> property),
    2563. 

  2563.       whether they've already been inserted into the page or not. In this
    2564. 

  2564.       fashion, views can be rendered at any time, and inserted into the DOM all
    2565. 

  2565.       at once, in order to get high-performance UI rendering with as few
    2566. 

  2566.       reflows and repaints as possible. <tt>this.el</tt> is created from the
    2567. 

  2567.       view's <tt>tagName</tt>, <tt>className</tt>, <tt>id</tt> and <tt>attributes</tt> properties,
    2568. 

  2568.       if specified. If not, <b>el</b> is an empty <tt>div</tt>.
    2569. 

  2569.     </p>
    2570. 

  2570. 

  2571. <pre class="runnable">
    2572. 

  2572. var ItemView = Backbone.View.extend({
    2573. 

  2573.   tagName: 'li'
    2574. 

  2574. });
    2575. 

  2575. 

  2576. var BodyView = Backbone.View.extend({
    2577. 

  2577.   el: 'body'
    2578. 

  2578. });
    2579. 

  2579. 

  2580. var item = new ItemView();
    2581. 

  2581. var body = new BodyView();
    2582. 

  2582. 

  2583. alert(item.el + ' ' + body.el);
    2584. 

  2584. </pre>
    2585. 

  2585. 

  2586.     <p id="View-$el">
    2587. 

  2587.       <b class="header">$el</b><code>view.$el</code>
    2588. 

  2588.       <br />
    2589. 

  2589.       A cached jQuery object for the view's element. A handy
    2590. 

  2590.       reference instead of re-wrapping the DOM element all the time.
    2591. 

  2591.     </p>
    2592. 

  2592. 

  2593. <pre>
    2594. 

  2594. view.$el.show();
    2595. 

  2595. 

  2596. listView.$el.append(itemView.el);
    2597. 

  2597. </pre>
    2598. 

  2598. 

  2599.     <p id="View-setElement">
    2600. 

  2600.       <b class="header">setElement</b><code>view.setElement(element)</code>
    2601. 

  2601.       <br />
    2602. 

  2602.       If you'd like to apply a Backbone view to a different DOM element, use
    2603. 

  2603.       <b>setElement</b>, which will also create the cached <tt>$el</tt> reference
    2604. 

  2604.       and move the view's delegated events from the old element to the new one.
    2605. 

  2605.     </p>
    2606. 

  2606. 

  2607.     <p id="View-attributes">
    2608. 

  2608.       <b class="header">attributes</b><code>view.attributes</code>
    2609. 

  2609.       <br />
    2610. 

  2610.       A hash of attributes that will be set as HTML DOM element attributes on the
    2611. 

  2611.       view's <tt>el</tt> (id, class, data-properties, etc.), or a function that
    2612. 

  2612.       returns such a hash.
    2613. 

  2613.     </p>
    2614. 

  2614. 

  2615.     <p id="View-dollar">
    2616. 

  2616.       <b class="header">$ (jQuery)</b><code>view.$(selector)</code>
    2617. 

  2617.       <br />
    2618. 

  2618.       If jQuery is included on the page, each view has a
    2619. 

  2619.       <b>$</b> function that runs queries scoped within the view's element. If you use this
    2620. 

  2620.       scoped jQuery function, you don't have to use model ids as part of your query
    2621. 

  2621.       to pull out specific elements in a list, and can rely much more on HTML class
    2622. 

  2622.       attributes. It's equivalent to running: <tt>view.$el.find(selector)</tt>
    2623. 

  2623.     </p>
    2624. 

  2624. 

  2625. <pre>
    2626. 

  2626. ui.Chapter = Backbone.View.extend({
    2627. 

  2627.   serialize : function() {
    2628. 

  2628.     return {
    2629. 

  2629.       title: this.$(".title").text(),
    2630. 

  2630.       start: this.$(".start-page").text(),
    2631. 

  2631.       end:   this.$(".end-page").text()
    2632. 

  2632.     };
    2633. 

  2633.   }
    2634. 

  2634. });
    2635. 

  2635. </pre>
    2636. 

  2636. 

  2637.     <p id="View-template">
    2638. 

  2638.       <b class="header">template</b><code>view.template([data])</code>
    2639. 

  2639.       <br />
    2640. 

  2640.       While templating for a view isn't a function provided directly by Backbone,
    2641. 

  2641.       it's often a nice convention to define a <b>template</b> function on your 
    2642. 

  2642.       views. In this way, when rendering your view, you have convenient access to
    2643. 

  2643.       instance data (<tt>this.model</tt>, <tt>options</tt>, and so on). 
    2644. 

  2644.       For example, using Underscore templates:
    2645. 

  2645.     </p>
    2646. 

  2646. 

  2647. <pre>
    2648. 

  2648. var LibraryView = Backbone.View.extend({
    2649. 

  2649.   template: _.template(...)
    2650. 

  2650. });
    2651. 

  2651. </pre>
    2652. 

  2652. 

  2653.     <p id="View-render">
    2654. 

  2654.       <b class="header">render</b><code>view.render()</code>
    2655. 

  2655.       <br />
    2656. 

  2656.       The default implementation of <b>render</b> is a no-op. Override this
    2657. 

  2657.       function with your code that renders the view template from model data,
    2658. 

  2658.       and updates <tt>this.el</tt> with the new HTML. A good
    2659. 

  2659.       convention is to <tt>return this</tt> at the end of <b>render</b> to
    2660. 

  2660.       enable chained calls.
    2661. 

  2661.     </p>
    2662. 

  2662. 

  2663. <pre>
    2664. 

  2664. var Bookmark = Backbone.View.extend({
    2665. 

  2665.   template: _.template(...),
    2666. 

  2666.   render: function() {
    2667. 

  2667.     this.$el.html(this.template(this.model.attributes));
    2668. 

  2668.     return this;
    2669. 

  2669.   }
    2670. 

  2670. });
    2671. 

  2671. </pre>
    2672. 

  2672. 

  2673.     <p>
    2674. 

  2674.       Backbone is agnostic with respect to your preferred method of HTML templating.
    2675. 

  2675.       Your <b>render</b> function could even munge together an HTML string, or use
    2676. 

  2676.       <tt>document.createElement</tt> to generate a DOM tree. However, we suggest
    2677. 

  2677.       choosing a nice JavaScript templating library.
    2678. 

  2678.       <a href="http://github.com/janl/mustache.js">Mustache.js</a>,
    2679. 

  2679.       <a href="http://github.com/creationix/haml-js">Haml-js</a>, and
    2680. 

  2680.       <a href="http://github.com/sstephenson/eco">Eco</a> are all fine alternatives.
    2681. 

  2681.       Because <a href="http://underscorejs.org/">Underscore.js</a> is already on the page,
    2682. 

  2682.       <a href="http://underscorejs.org/#template">_.template</a>
    2683. 

  2683.       is available, and is an excellent choice if you prefer simple
    2684. 

  2684.       interpolated-JavaScript style templates.
    2685. 

  2685.     </p>
    2686. 

  2686. 

  2687.     <p>
    2688. 

  2688.       Whatever templating strategy you end up with, it's nice if you <i>never</i>
    2689. 

  2689.       have to put strings of HTML in your JavaScript. At DocumentCloud, we
    2690. 

  2690.       use <a href="http://documentcloud.github.com/jammit/">Jammit</a> in order
    2691. 

  2691.       to package up JavaScript templates stored in <tt>/app/views</tt> as part
    2692. 

  2692.       of our main <tt>core.js</tt> asset package.
    2693. 

  2693.     </p>
    2694. 

  2694. 

  2695.     <p id="View-remove">
    2696. 

  2696.       <b class="header">remove</b><code>view.remove()</code>
    2697. 

  2697.       <br />
    2698. 

  2698.       Removes a view from the DOM, and calls
    2699. 

  2699.       <a href="#Events-stopListening">stopListening</a> to remove any bound
    2700. 

  2700.       events that the view has <a href="#Events-listenTo">listenTo</a>'d.
    2701. 

  2701.     </p>
    2702. 

  2702. 

  2703.     <p id="View-delegateEvents">
    2704. 

  2704.       <b class="header">delegateEvents</b><code>delegateEvents([events])</code>
    2705. 

  2705.       <br />
    2706. 

  2706.       Uses jQuery's <tt>on</tt> function to provide declarative callbacks
    2707. 

  2707.       for DOM events within a view.
    2708. 

  2708.       If an <b>events</b> hash is not passed directly, uses <tt>this.events</tt>
    2709. 

  2709.       as the source. Events are written in the format <tt>{"event selector": "callback"}</tt>.
    2710. 

  2710.       The callback may be either the name of a method on the view, or a direct
    2711. 

  2711.       function body.
    2712. 

  2712.       Omitting the <tt>selector</tt> causes the event to be bound to the view's
    2713. 

  2713.       root element (<tt>this.el</tt>). By default, <tt>delegateEvents</tt> is called
    2714. 

  2714.       within the View's constructor for you, so if you have a simple <tt>events</tt>
    2715. 

  2715.       hash, all of your DOM events will always already be connected, and you will
    2716. 

  2716.       never have to call this function yourself.
    2717. 

  2717.     </p>
    2718. 

  2718. 

  2719.     <p>
    2720. 

  2720.       The <tt>events</tt> property may also be defined as a function that returns
    2721. 

  2721.       an <b>events</b> hash, to make it easier to programmatically define your
    2722. 

  2722.       events, as well as inherit them from parent views.
    2723. 

  2723.     </p>
    2724. 

  2724. 

  2725.     <p>
    2726. 

  2726.       Using <b>delegateEvents</b> provides a number of advantages over manually
    2727. 

  2727.       using jQuery to bind events to child elements during <a href="#View-render">render</a>. All attached
    2728. 

  2728.       callbacks are bound to the view before being handed off to jQuery, so when
    2729. 

  2729.       the callbacks are invoked, <tt>this</tt> continues to refer to the view object. When
    2730. 

  2730.       <b>delegateEvents</b> is run again, perhaps with a different <tt>events</tt>
    2731. 

  2731.       hash, all callbacks are removed and delegated afresh &mdash; useful for
    2732. 

  2732.       views which need to behave differently when in different modes.
    2733. 

  2733.     </p>
    2734. 

  2734. 

  2735.     <p>
    2736. 

  2736.       A view that displays a document in a search result might look
    2737. 

  2737.       something like this:
    2738. 

  2738.     </p>
    2739. 

  2739. 

  2740. <pre>
    2741. 

  2741. var DocumentView = Backbone.View.extend({
    2742. 

  2742. 

  2743.   events: {
    2744. 

  2744.     "dblclick"                : "open",
    2745. 

  2745.     "click .icon.doc"         : "select",
    2746. 

  2746.     "contextmenu .icon.doc"   : "showMenu",
    2747. 

  2747.     "click .show_notes"       : "toggleNotes",
    2748. 

  2748.     "click .title .lock"      : "editAccessLevel",
    2749. 

  2749.     "mouseover .title .date"  : "showTooltip"
    2750. 

  2750.   },
    2751. 

  2751. 

  2752.   render: function() {
    2753. 

  2753.     this.$el.html(this.template(this.model.attributes));
    2754. 

  2754.     return this;
    2755. 

  2755.   },
    2756. 

  2756. 

  2757.   open: function() {
    2758. 

  2758.     window.open(this.model.get("viewer_url"));
    2759. 

  2759.   },
    2760. 

  2760. 

  2761.   select: function() {
    2762. 

  2762.     this.model.set({selected: true});
    2763. 

  2763.   },
    2764. 

  2764. 

  2765.   ...
    2766. 

  2766. 

  2767. });
    2768. 

  2768. </pre>
    2769. 

  2769. 

  2770.     <p id="View-undelegateEvents">
    2771. 

  2771.       <b class="header">undelegateEvents</b><code>undelegateEvents()</code>
    2772. 

  2772.       <br />
    2773. 

  2773.       Removes all of the view's delegated events. Useful if you want to disable
    2774. 

  2774.       or remove a view from the DOM temporarily.
    2775. 

  2775.     </p>
    2776. 

  2776. 

  2777.     <h2 id="Utility">Utility</h2>
    2778. 

  2778. 

  2779.     <p id="Utility-Backbone-noConflict">
    2780. 

  2780.       <b class="header">Backbone.noConflict</b><code>var backbone = Backbone.noConflict();</code>
    2781. 

  2781.       <br />
    2782. 

  2782.       Returns the <tt>Backbone</tt> object back to its original value. You can
    2783. 

  2783.       use the return value of <tt>Backbone.noConflict()</tt> to keep a local
    2784. 

  2784.       reference to Backbone. Useful for embedding Backbone on third-party
    2785. 

  2785.       websites, where you don't want to clobber the existing Backbone.
    2786. 

  2786.     </p>
    2787. 

  2787. 

  2788. <pre>
    2789. 

  2789. var localBackbone = Backbone.noConflict();
    2790. 

  2790. var model = localBackbone.Model.extend(...);
    2791. 

  2791. </pre>
    2792. 

  2792. 

  2793.     <p id="Utility-Backbone-$">
    2794. 

  2794.       <b class="header">Backbone.$</b><code>Backbone.$ = $;</code>
    2795. 

  2795.       <br />
    2796. 

  2796.       If you have multiple copies of <tt>jQuery</tt> on the page, or simply want
    2797. 

  2797.       to tell Backbone to use a particular object as its DOM / Ajax library,
    2798. 

  2798.       this is the property for you.
    2799. 

  2799.     </p>
    2800. 

  2800. 

  2801.     <h2 id="examples">Examples</h2>
    2802. 

  2802. 

  2803.     <p>
    2804. 

  2804.       The list of examples that follows, while long, is not exhaustive. If you've
    2805. 

  2805.       worked on an app that uses Backbone, please add it to the
    2806. 

  2806.       <a href="https://github.com/jashkenas/backbone/wiki/Projects-and-Companies-using-Backbone">wiki page of Backbone apps</a>.
    2807. 

  2807.     </p>
    2808. 

  2808. 

  2809.     <p id="examples-todos">
    2810. 

  2810.       <a href="http://jgn.me/">Jérôme Gravel-Niquet</a> has contributed a
    2811. 

  2811.       <a href="examples/todos/index.html">Todo List application</a>
    2812. 

  2812.       that is bundled in the repository as Backbone example. If you're wondering
    2813. 

  2813.       where to get started with Backbone in general, take a moment to
    2814. 

  2814.       <a href="docs/todos.html">read through the annotated source</a>. The app uses a
    2815. 

  2815.       <a href="http://github.com/jeromegn/Backbone.localStorage">LocalStorage adapter</a>
    2816. 

  2816.       to transparently save all of your todos within your browser, instead of
    2817. 

  2817.       sending them to a server. Jérôme also has a version hosted at
    2818. 

  2818.       <a href="http://localtodos.com/">localtodos.com</a>.
    2819. 

  2819.     </p>
    2820. 

  2820. 

  2821.     <div style="text-align: center;">
    2822. 

  2822.       <a href="examples/todos/index.html">
    2823. 

  2823.         <img width="400" height="427" data-original="docs/images/todos.png" alt="Todos" class="example_image" />
    2824. 

  2824.       </a>
    2825. 

  2825.     </div>
    2826. 

  2826. 

  2827.     <h2 id="examples-documentcloud">DocumentCloud</h2>
    2828. 

  2828. 

  2829.     <p>
    2830. 

  2830.       The <a href="http://www.documentcloud.org/public/#search/">DocumentCloud workspace</a>
    2831. 

  2831.       is built on Backbone.js, with <i>Documents</i>, <i>Projects</i>,
    2832. 

  2832.       <i>Notes</i>, and <i>Accounts</i> all as Backbone models and collections.
    2833. 

  2833.       If you're interested in history &mdash; both Underscore.js and Backbone.js
    2834. 

  2834.       were originally extracted from the DocumentCloud codebase, and packaged
    2835. 

  2835.       into standalone JS libraries.
    2836. 

  2836.     </p>
    2837. 

  2837. 

  2838.     <div style="text-align: center;">
    2839. 

  2839.       <a href="http://www.documentcloud.org/public/#search/">
    2840. 

  2840.         <img width="550" height="453" data-original="docs/images/dc-workspace.png" alt="DocumentCloud Workspace" class="example_image" />
    2841. 

  2841.       </a>
    2842. 

  2842.     </div>
    2843. 

  2843. 

  2844.     <h2 id="examples-usa-today">USA Today</h2>
    2845. 

  2845. 

  2846.     <p>
    2847. 

  2847.       <a href="http://usatoday.com">USA Today</a> takes advantage of the modularity of
    2848. 

  2848.       Backbone's data/model lifecycle &mdash; which makes it simple to create, inherit,
    2849. 

  2849.       isolate, and link application objects &mdash; to keep the codebase both manageable and efficient.
    2850. 

  2850.       The new website also makes heavy use of the Backbone Router to control the
    2851. 

  2851.       page for both pushState-capable and legacy browsers.
    2852. 

  2852.       Finally, the team took advantage of Backbone's Event module to create a
    2853. 

  2853.       PubSub API that allows third parties and analytics packages to hook into the
    2854. 

  2854.       heart of the app.
    2855. 

  2855.     </p>
    2856. 

  2856. 

  2857.     <div style="text-align: center;">
    2858. 

  2858.       <a href="http://usatoday.com">
    2859. 

  2859.         <img width="550" height="532" data-original="docs/images/usa-today.png" alt="USA Today" class="example_image" />
    2860. 

  2860.       </a>
    2861. 

  2861.     </div>
    2862. 

  2862. 

  2863.     <h2 id="examples-rdio">Rdio</h2>
    2864. 

  2864. 

  2865.     <p>
    2866. 

  2866.       <a href="http://rdio.com/new">New Rdio</a> was developed from the ground
    2867. 

  2867.       up with a component based framework based on Backbone.js. Every component
    2868. 

  2868.       on the screen is dynamically loaded and rendered, with data provided by the
    2869. 

  2869.       <a href="http://developer.rdio.com/">Rdio API</a>. When changes are pushed,
    2870. 

  2870.       every component can update itself without reloading the page or interrupting
    2871. 

  2871.       the user's music. All of this relies on Backbone's views and models,
    2872. 

  2872.       and all URL routing is handled by Backbone's Router. When data changes are
    2873. 

  2873.       signaled in realtime, Backbone's Events notify the interested components
    2874. 

  2874.       in the data changes. Backbone forms the core of the new, dynamic, realtime
    2875. 

  2875.       Rdio web and <i>desktop</i> applications.
    2876. 

  2876.     </p>
    2877. 

  2877. 

  2878.     <div style="text-align: center;">
    2879. 

  2879.       <a href="http://rdio.com/new">
    2880. 

  2880.         <img width="550" height="344" data-original="docs/images/rdio.png" alt="Rdio" class="example_image" />
    2881. 

  2881.       </a>
    2882. 

  2882.     </div>
    2883. 

  2883. 

  2884.     <h2 id="examples-hulu">Hulu</h2>
    2885. 

  2885. 

  2886.     <p>
    2887. 

  2887.       <a href="http://hulu.com">Hulu</a> used Backbone.js to build its next
    2888. 

  2888.       generation online video experience. With Backbone as a foundation, the
    2889. 

  2889.       web interface was rewritten from scratch so that all page content can
    2890. 

  2890.       be loaded dynamically with smooth transitions as you navigate.
    2891. 

  2891.       Backbone makes it easy to move through the app quickly without the
    2892. 

  2892.       reloading of scripts and embedded videos, while also offering models and
    2893. 

  2893.       collections for additional data manipulation support.
    2894. 

  2894.     </p>
    2895. 

  2895. 

  2896.     <div style="text-align: center;">
    2897. 

  2897.       <a href="http://hulu.com">
    2898. 

  2898.         <img width="550" height="449" data-original="docs/images/hulu.png" alt="Hulu" class="example_image" />
    2899. 

  2899.       </a>
    2900. 

  2900.     </div>
    2901. 

  2901. 

  2902.     <h2 id="examples-quartz">Quartz</h2>
    2903. 

  2903. 

  2904.     <p>
    2905. 

  2905.       <a href="http://qz.com">Quartz</a> sees itself as a digitally native news
    2906. 

  2906.       outlet for the new
    2907. 

  2907.       global economy. Because Quartz believes in the future of open,
    2908. 

  2908.       cross-platform web applications, they selected Backbone and Underscore
    2909. 

  2909.       to fetch, sort, store, and display content from a custom WordPress
    2910. 

  2910.       API. Although <a href="http://qz.com">qz.com</a> uses responsive design
    2911. 

  2911.       for phone, tablet, and
    2912. 

  2912.       desktop browsers, it also takes advantage of Backbone events and views
    2913. 

  2913.       to render device-specific templates in some cases.
    2914. 

  2914.     </p>
    2915. 

  2915. 

  2916.     <div style="text-align: center;">
    2917. 

  2917.       <a href="http://qz.com">
    2918. 

  2918.         <img width="510" height="360" data-original="docs/images/quartz.jpg" alt="Quartz" class="example_retina" />
    2919. 

  2919.       </a>
    2920. 

  2920.     </div>
    2921. 

  2921. 

  2922.     <h2 id="examples-gawker">Gawker Media</h2>
    2923. 

  2923. 

  2924.     <p>
    2925. 

  2925.       <a href="http://kinja.com">Kinja</a> is Gawker Media's publishing platform designed
    2926. 

  2926.       to create great stories by breaking down the lines between the traditional
    2927. 

  2927.       roles of content creators and consumers. Everyone — editors, readers,
    2928. 

  2928.       marketers — have access to the same tools to engage in passionate discussion
    2929. 

  2929.       and pursue the truth of the story. Sharing, recommending, and following within the
    2930. 

  2930.       Kinja ecosystem allows for improved information discovery across all the sites.
    2931. 

  2931.     </p>
    2932. 

  2932.     <p>
    2933. 

  2933.       Kinja is the platform behind
    2934. 

  2934.       <a href="http://gawker.com/">Gawker</a>,
    2935. 

  2935.       <a href="http://gizmodo.com/">Gizmodo</a>,
    2936. 

  2936.       <a href="http://lifehacker.com/">Lifehacker</a>,
    2937. 

  2937.       <a href="http://io9.com/">io9</a> and other Gawker Media
    2938. 

  2938.       blogs. Backbone.js underlies the front-end application code that powers
    2939. 

  2939.       everything from user authentication to post authoring, commenting, and even serving
    2940. 

  2940.       ads. The JavaScript stack includes
    2941. 

  2941.       <a href="http://underscorejs.org/">Underscore.js</a> and
    2942. 

  2942.       <a href="http://jquery.com/">jQuery</a>, with some plugins,
    2943. 

  2943.       all loaded with
    2944. 

  2944.       <a href="http://requirejs.org/">RequireJS</a>. Closure templates are shared between the
    2945. 

  2945.       <a href="http://www.playframework.com/">Play! Framework</a> based Scala application and Backbone views, and the responsive layout
    2946. 

  2946.       is done with the
    2947. 

  2947.       <a href="http://foundation.zurb.com/">Foundation</a> framework using
    2948. 

  2948.       <a href="http://sass-lang.com/">SASS</a>.
    2949. 

  2949.     </p>
    2950. 

  2950. 

  2951.     <div style="text-align: center;">
    2952. 

  2952.       <a href="http://gawker.com">
    2953. 

  2953.         <img width="558" height="473" data-original="docs/images/gawker.png" alt="Gawker" class="example_image" />
    2954. 

  2954.       </a>
    2955. 

  2955.     </div>
    2956. 

  2956. 

  2957.     <h2 id="examples-flow">Flow</h2>
    2958. 

  2958. 

  2959.     <p>
    2960. 

  2960.       <a href="http://www.metalabdesign.com/">MetaLab</a> used Backbone.js to create
    2961. 

  2961.       <a href="http://www.getflow.com/">Flow</a>, a task management app for teams. The
    2962. 

  2962.       workspace relies on Backbone.js to construct task views, activities, accounts,
    2963. 

  2963.       folders, projects, and tags. You can see the internals under <tt>window.Flow</tt>.
    2964. 

  2964.     </p>
    2965. 

  2965. 

  2966.     <div style="text-align: center;">
    2967. 

  2967.       <a href="http://www.getflow.com/">
    2968. 

  2968.         <img width="550" height="416" data-original="docs/images/flow.png" alt="Flow" class="example_image" />
    2969. 

  2969.       </a>
    2970. 

  2970.     </div>
    2971. 

  2971. 

  2972.     <h2 id="examples-gilt">Gilt Groupe</h2>
    2973. 

  2973. 

  2974.     <p>
    2975. 

  2975.       <a href="http://gilt.com">Gilt Groupe</a> uses Backbone.js to build multiple
    2976. 

  2976.       applications across their family of sites.
    2977. 

  2977.       <a href="http://m.gilt.com">Gilt's mobile website</a> uses Backbone and
    2978. 

  2978.       <a href="http://zeptojs.com">Zepto.js</a> to create a blazing-fast
    2979. 

  2979.       shopping experience for users on-the-go, while
    2980. 

  2980.       <a href="http://live.gilt.com">Gilt Live</a> combines Backbone with
    2981. 

  2981.       WebSockets to display the items that customers are buying in real-time. Gilt's search
    2982. 

  2982.       functionality also uses Backbone to filter and sort products efficiently
    2983. 

  2983.       by moving those actions to the client-side.
    2984. 

  2984.     </p>
    2985. 

  2985. 

  2986.     <div style="text-align: center;">
    2987. 

  2987.       <a href="http://www.gilt.com/">
    2988. 

  2988.         <img width="550" height="444" data-original="docs/images/gilt.jpg" alt="Gilt Groupe" class="example_image" />
    2989. 

  2989.       </a>
    2990. 

  2990.     </div>
    2991. 

  2991. 

  2992.     <h2 id="examples-newsblur">NewsBlur</h2>
    2993. 

  2993. 

  2994.     <p>
    2995. 

  2995.       <a href="http://www.newsblur.com">NewsBlur</a> is an RSS feed reader and
    2996. 

  2996.       social news network with a fast and responsive UI that feels like a
    2997. 

  2997.       native desktop app. Backbone.js was selected for
    2998. 

  2998.       <a href="http://www.ofbrooklyn.com/2012/11/13/backbonification-migrating-javascript-to-backbone/">a major rewrite and transition from spaghetti code</a>
    2999. 

  2999.       because of its powerful yet simple feature set, easy integration, and large
    3000. 

  3000.       community. If you want to poke around under the hood, NewsBlur is also entirely
    3001. 

  3001.       <a href="http://github.com/samuelclay/NewsBlur">open-source</a>.
    3002. 

  3002.     </p>
    3003. 

  3003. 

  3004.     <div style="text-align: center;">
    3005. 

  3005.       <a href="http://newsblur.com">
    3006. 

  3006.         <img width="510" height="340" data-original="docs/images/newsblur.jpg" alt="Newsblur" class="example_retina" />
    3007. 

  3007.       </a>
    3008. 

  3008.     </div>
    3009. 

  3009. 

  3010.     <h2 id="examples-wordpress">WordPress.com</h2>
    3011. 

  3011. 

  3012.     <p>
    3013. 

  3013.       <a href="http://wordpress.com/">WordPress.com</a> is the software-as-a-service
    3014. 

  3014.       version of <a href="http://wordpress.org">WordPress</a>. It uses Backbone.js
    3015. 

  3015.       Models, Collections, and Views in its
    3016. 

  3016.       <a href="http://en.blog.wordpress.com/2012/05/25/notifications-refreshed/">Notifications system</a>.  Backbone.js was selected
    3017. 

  3017.       because it was easy to fit into the structure of the application, not the
    3018. 

  3018.       other way around. <a href="http://automattic.com">Automattic</a>
    3019. 

  3019.       (the company behind WordPress.com) is integrating Backbone.js into the
    3020. 

  3020.       Stats tab and other features throughout the homepage.
    3021. 

  3021.     </p>
    3022. 

  3022. 

  3023.     <div style="text-align: center;">
    3024. 

  3024.       <a href="http://wordpress.com/">
    3025. 

  3025.         <img width="550" height="387" data-original="docs/images/wpcom-notifications.png" alt="WordPress.com Notifications"
    3026. 

  3026.     title="WordPress.com Notifications" class="example_image" />
    3027. 

  3027.       </a>
    3028. 

  3028.     </div>
    3029. 

  3029. 

  3030.     <h2 id="examples-foursquare">Foursquare</h2>
    3031. 

  3031. 

  3032.     <p>
    3033. 

  3033.       Foursquare is a fun little startup that helps you meet up with friends,
    3034. 

  3034.       discover new places, and save money. Backbone Models are heavily used in
    3035. 

  3035.       the core JavaScript API layer and Views power many popular features like
    3036. 

  3036.       the <a href="https://foursquare.com">homepage map</a> and
    3037. 

  3037.       <a href="https://foursquare.com/seriouseats/list/the-best-doughnuts-in-ny">lists</a>.
    3038. 

  3038.     </p>
    3039. 

  3039. 

  3040.     <div style="text-align: center;">
    3041. 

  3041.       <a href="http://foursquare.com">
    3042. 

  3042.         <img width="550" height="427" data-original="docs/images/foursquare.png" alt="Foursquare" class="example_image" />
    3043. 

  3043.       </a>
    3044. 

  3044.     </div>
    3045. 

  3045. 

  3046.     <h2 id="examples-bitbucket">Bitbucket</h2>
    3047. 

  3047. 

  3048.     <p>
    3049. 

  3049.       <a href="http://www.bitbucket.org">Bitbucket</a> is a free source code hosting
    3050. 

  3050.       service for Git and Mercurial. Through its models and collections,
    3051. 

  3051.       Backbone.js has proved valuable in supporting Bitbucket's
    3052. 

  3052.       <a href="https://api.bitbucket.org">REST API</a>, as well as newer
    3053. 

  3053.       components such as in-line code comments and approvals for pull requests.
    3054. 

  3054.       Mustache templates provide server and client-side rendering, while a custom
    3055. 

  3055.       <a href="https://developers.google.com/closure/library/">Google Closure</a>
    3056. 

  3056.       inspired life-cycle for widgets allows Bitbucket to decorate existing DOM
    3057. 

  3057.       trees and insert new ones.
    3058. 

  3058.     </p>
    3059. 

  3059. 

  3060.     <div style="text-align: center;">
    3061. 

  3061.       <a href="http://www.bitbucket.org">
    3062. 

  3062.         <img width="550" height="356" data-original="docs/images/bitbucket.png" alt="Bitbucket" class="example_image" />
    3063. 

  3063.       </a>
    3064. 

  3064.     </div>
    3065. 

  3065. 

  3066.     <h2 id="examples-disqus">Disqus</h2>
    3067. 

  3067. 

  3068.     <p>
    3069. 

  3069.       <a href="http://www.disqus.com">Disqus</a> chose Backbone.js to power the
    3070. 

  3070.       latest version of their commenting widget. Backbone&rsquo;s small
    3071. 

  3071.       footprint and easy extensibility made it the right choice for Disqus&rsquo;
    3072. 

  3072.       distributed web application, which is hosted entirely inside an iframe and
    3073. 

  3073.       served on thousands of large web properties, including IGN, Wired, CNN, MLB, and more.
    3074. 

  3074.     </p>
    3075. 

  3075. 

  3076.     <div style="text-align: center;">
    3077. 

  3077.       <a href="http://www.disqus.com">
    3078. 

  3078.         <img width="550" height="454" data-original="docs/images/disqus.png" alt="Disqus" class="example_image" />
    3079. 

  3079.       </a>
    3080. 

  3080.     </div>
    3081. 

  3081. 

  3082.     <h2 id="examples-khan-academy">Khan Academy</h2>
    3083. 

  3083. 

  3084.     <p>
    3085. 

  3085.       <a href="http://www.khanacademy.org">Khan Academy</a> is on a mission to
    3086. 

  3086.       provide a free world-class education to anyone anywhere. With thousands of
    3087. 

  3087.       videos, hundreds of JavaScript-driven exercises, and big plans for the
    3088. 

  3088.       future, Khan Academy uses Backbone to keep frontend code modular and organized.
    3089. 

  3089.       User profiles and goal setting are implemented with Backbone,
    3090. 

  3090.       <a href="http://jquery.com/">jQuery</a> and
    3091. 

  3091.       <a href="http://handlebarsjs.com/">Handlebars</a>, and most new feature
    3092. 

  3092.       work is being pushed to the client side, greatly increasing the quality of
    3093. 

  3093.       <a href="https://github.com/Khan/khan-api/">the API</a>.
    3094. 

  3094.     </p>
    3095. 

  3095. 

  3096.     <div style="text-align: center;">
    3097. 

  3097.       <a href="http://www.khanacademy.org">
    3098. 

  3098.         <img width="550" height="454" data-original="docs/images/khan-academy.png" alt="Khan Academy" class="example_image" />
    3099. 

  3099.       </a>
    3100. 

  3100.     </div>
    3101. 

  3101. 

  3102.     <h2 id="examples-elife-lens">eLife Lens</h2>
    3103. 

  3103. 

  3104.     <p>
    3105. 

  3105.       <a href="http://elifesciences.github.io/lens/#about/figures/all/video_video1">eLife Lens</a>
    3106. 

  3106.       is a novel system for writing on the web. Instead of tying the content to a
    3107. 

  3107.       presentation focused format, Lens treats
    3108. 

  3108.       <a href="http://blog.okfn.org/2013/01/15/content-as-data-towards-open-digital-publishing-with-substance/">content as data</a>
    3109. 

  3109.       and makes the links that exist within a document easy to navigate. Backbone.js
    3110. 

  3110.       is used to structure the views,
    3111. 

  3111.       <a href="http://interior.substance.io/modules/document.html">Substance Document</a>
    3112. 

  3112.       for representing content and
    3113. 

  3113.       <a href="http://ken.quasipartikel.at/">Ken</a>
    3114. 

  3114.       for faceted filtering. Read more in the official
    3115. 

  3115.       <a href="http://www.elifesciences.org/lens/">introduction post</a>
    3116. 

  3116.       or dig into the <a href="http://github.com/elifesciences/lens">source code</a>.
    3117. 

  3117.     </p>
    3118. 

  3118. 

  3119.     <div style="text-align: center;">
    3120. 

  3120.       <a href="http://elifesciences.github.io/lens/#about/figures/all/video_video1">
    3121. 

  3121.         <img width="510" height="383" data-original="docs/images/lens.png" alt="eLife Lens" class="example_retina" />
    3122. 

  3122.       </a>
    3123. 

  3123.     </div>
    3124. 

  3124. 

  3125.     <h2 id="examples-do">Do</h2>
    3126. 

  3126. 

  3127.     <p>
    3128. 

  3128.       <a href="http://do.com">Do</a> is a social productivity app that makes it
    3129. 

  3129.       easy to work on tasks, track projects, and take notes with your team.
    3130. 

  3130.       The <a href="http://do.com">Do.com</a> web application was built from the
    3131. 

  3131.       ground up to work seamlessly on your smartphone, tablet and computer. The
    3132. 

  3132.       team used Backbone, <a href="http://coffeescript.org/">CoffeeScript</a> and <a href="http://handlebarsjs.com/">Handlebars</a> to build a full-featured
    3133. 

  3133.       app in record time and rolled their own extensions for complex navigation
    3134. 

  3134.       and model sync support.
    3135. 

  3135.     </p>
    3136. 

  3136. 

  3137.     <div style="text-align: center;">
    3138. 

  3138.       <a href="http://do.com">
    3139. 

  3139.         <img width="550" height="425" data-original="docs/images/do.png" alt="Do" class="example_image" />
    3140. 

  3140.       </a>
    3141. 

  3141.     </div>
    3142. 

  3142. 

  3143.     <h2 id="examples-irccloud">IRCCloud</h2>
    3144. 

  3144. 

  3145.     <p>
    3146. 

  3146.       <a href="http://irccloud.com/">IRCCloud</a>
    3147. 

  3147.       is an always-connected IRC client that you use in your
    3148. 

  3148.       browser &mdash; often leaving it open all day in a tab.
    3149. 

  3149.       The sleek web interface communicates with an
    3150. 

  3150.       Erlang backend via websockets and the
    3151. 

  3151.       <a href="https://github.com/irccloud/irccloud-tools/wiki/API-Overview">IRCCloud API</a>.
    3152. 

  3152.       It makes heavy use of Backbone.js events, models, views and routing to keep
    3153. 

  3153.       your IRC conversations flowing in real time.
    3154. 

  3154.     </p>
    3155. 

  3155. 

  3156.     <div style="text-align: center;">
    3157. 

  3157.       <a href="http://irccloud.com/">
    3158. 

  3158.         <img width="550" height="392" data-original="docs/images/irccloud.png" alt="IRCCloud" class="example_image" />
    3159. 

  3159.       </a>
    3160. 

  3160.     </div>
    3161. 

  3161. 

  3162.     <h2 id="examples-pitchfork">Pitchfork</h2>
    3163. 

  3163. 

  3164.     <p>
    3165. 

  3165.       <a href="http://pitchfork.com/">Pitchfork</a> uses Backbone.js to power
    3166. 

  3166.       its site-wide audio player, <a href="http://pitchfork.com/tv/">Pitchfork.tv</a>,
    3167. 

  3167.       location routing, a write-thru page fragment cache, and more. Backbone.js
    3168. 

  3168.       (and <a href="http://underscorejs.org/">Underscore.js</a>) helps the team
    3169. 

  3169.       create clean and modular components,
    3170. 

  3170.       move very quickly, and focus on the site, not the spaghetti.
    3171. 

  3171.     </p>
    3172. 

  3172. 

  3173.     <div style="text-align: center;">
    3174. 

  3174.       <a href="http://pitchfork.com/">
    3175. 

  3175.         <img width="550" height="428" data-original="docs/images/pitchfork.png" alt="Pitchfork" class="example_image" />
    3176. 

  3176.       </a>
    3177. 

  3177.     </div>
    3178. 

  3178. 

  3179.     <h2 id="examples-spin">Spin</h2>
    3180. 

  3180. 

  3181.     <p>
    3182. 

  3182.       <a href="http://spin.com/">Spin</a> pulls in the
    3183. 

  3183.       <a href="http://www.spin.com/news">latest news stories</a> from
    3184. 

  3184.       their internal API onto their site using Backbone models and collections, and a
    3185. 

  3185.       custom <tt>sync</tt> method. Because the music should never stop playing,
    3186. 

  3186.       even as you click through to different "pages", Spin uses a Backbone router
    3187. 

  3187.       for navigation within the site.
    3188. 

  3188.     </p>
    3189. 

  3189. 

  3190.     <div style="text-align: center;">
    3191. 

  3191.       <a href="http://spin.com/">
    3192. 

  3192.         <img width="550" height="543" data-original="docs/images/spin.png" alt="Spin" class="example_image" />
    3193. 

  3193.       </a>
    3194. 

  3194.     </div>
    3195. 

  3195. 

  3196.     <h2 id="examples-zocdoc">ZocDoc</h2>
    3197. 

  3197. 

  3198.     <p>
    3199. 

  3199.       <a href="http://www.zocdoc.com">ZocDoc</a> helps patients
    3200. 

  3200.       find local, in-network doctors and dentists, see their real-time 
    3201. 

  3201.       availability, and instantly book appointments.
    3202. 

  3202.       On the public side, the webapp uses Backbone.js to handle client-side state and rendering in 
    3203. 

  3203.       <a href="http://www.zocdoc.com/primary-care-doctors/los-angeles-13122pm">search pages</a>
    3204. 

  3204.       and <a href="http://www.zocdoc.com/doctor/nathan-hashimoto-md-58078">doctor profiles</a>. 
    3205. 

  3205.       In addition, the new version of the doctor-facing part of the website is a 
    3206. 

  3206.       large single-page application that 
    3207. 

  3207.       benefits from Backbone's structure and modularity. ZocDoc's Backbone 
    3208. 

  3208.       classes are tested with 
    3209. 

  3209.       <a href="http://pivotal.github.io/jasmine/">Jasmine</a>, and delivered 
    3210. 

  3210.       to the end user with 
    3211. 

  3211.       <a href="http://getcassette.net/">Cassette</a>.
    3212. 

  3212.     </p>
    3213. 

  3213. 

  3214.     <div style="text-align: center;">
    3215. 

  3215.       <a href="http://www.zocdoc.com">
    3216. 

  3216.         <img width="510" height="464" data-original="docs/images/zocdoc.jpg" alt="ZocDoc" class="example_retina" />
    3217. 

  3217.       </a>
    3218. 

  3218.     </div>
    3219. 

  3219. 

  3220.     <h2 id="examples-walmart">Walmart Mobile</h2>
    3221. 

  3221. 

  3222.     <p>
    3223. 

  3223.       <a href="http://www.walmart.com/">Walmart</a> used Backbone.js to create the new version
    3224. 

  3224.       of <a href="http://mobile.walmart.com/r/phoenix">their mobile web application</a> and
    3225. 

  3225.       created two new frameworks in the process.
    3226. 

  3226.       <a href="http://walmartlabs.github.com/thorax/">Thorax</a> provides mixins, inheritable
    3227. 

  3227.       events, as well as model and collection view bindings that integrate directly with
    3228. 

  3228.       <a href="http://handlebarsjs.com/">Handlebars</a> templates.
    3229. 

  3229.       <a href="http://walmartlabs.github.com/lumbar/">Lumbar</a> allows the application to be
    3230. 

  3230.       split into modules which can be loaded on demand, and creates platform specific builds
    3231. 

  3231.       for the portions of the web application that are embedded in Walmart's native Android
    3232. 

  3232.       and iOS applications.
    3233. 

  3233.     </p>
    3234. 

  3234. 

  3235.     <div style="text-align: center;">
    3236. 

  3236.       <a href="http://mobile.walmart.com/r/phoenix">
    3237. 

  3237.         <img width="256" height="500" data-original="docs/images/walmart-mobile.png" alt="Walmart Mobile" class="example_image" />
    3238. 

  3238.       </a>
    3239. 

  3239.     </div>
    3240. 

  3240. 

  3241.     <h2 id="examples-groupon">Groupon Now!</h2>
    3242. 

  3242. 

  3243.     <p>
    3244. 

  3244.       <a href="http://www.groupon.com/now">Groupon Now!</a> helps you find
    3245. 

  3245.       local deals that you can buy and use right now. When first developing
    3246. 

  3246.       the product, the team decided it would be AJAX heavy with smooth transitions
    3247. 

  3247.       between sections instead of full refreshes, but still needed to be fully
    3248. 

  3248.       linkable and shareable. Despite never having used Backbone before, the
    3249. 

  3249.       learning curve was incredibly quick &mdash; a prototype was hacked out in an
    3250. 

  3250.       afternoon, and the team was able to ship the product in two weeks.
    3251. 

  3251.       Because the source is minimal and understandable, it was easy to
    3252. 

  3252.       add several Backbone extensions for Groupon Now!: changing the router
    3253. 

  3253.       to handle URLs with querystring parameters, and adding a simple
    3254. 

  3254.       in-memory store for caching repeated requests for the same data.
    3255. 

  3255.     </p>
    3256. 

  3256. 

  3257.     <div style="text-align: center;">
    3258. 

  3258.       <a href="http://www.groupon.com/now">
    3259. 

  3259.         <img width="550" height="466" data-original="docs/images/groupon.png" alt="Groupon Now!" class="example_image" />
    3260. 

  3260.       </a>
    3261. 

  3261.     </div>
    3262. 

  3262. 

  3263.     <h2 id="examples-basecamp">Basecamp</h2>
    3264. 

  3264. 

  3265.     <p>
    3266. 

  3266.       <a href="http://37signals.com/">37Signals</a> chose Backbone.js to create
    3267. 

  3267.       the <a href="http://basecamp.com/calendar">calendar feature</a> of its
    3268. 

  3268.       popular project management software <a href="http://basecamp.com/">Basecamp</a>.
    3269. 

  3269.       The Basecamp Calendar uses Backbone.js models and views in conjunction with the
    3270. 

  3270.       <a href="https://github.com/sstephenson/eco">Eco</a> templating system to
    3271. 

  3271.       present a polished, highly interactive group scheduling interface.
    3272. 

  3272.     </p>
    3273. 

  3273. 

  3274.     <div style="text-align: center;">
    3275. 

  3275.       <a href="http://basecamp.com/calendar">
    3276. 

  3276.         <img width="530" height="380" data-original="docs/images/basecamp-calendar.jpg" alt="Basecamp Calendar" class="example_image" />
    3277. 

  3277.       </a>
    3278. 

  3278.     </div>
    3279. 

  3279. 

  3280.     <h2 id="examples-slavery-footprint">Slavery Footprint</h2>
    3281. 

  3281. 

  3282.     <p>
    3283. 

  3283.       <a href="http://slaveryfootprint.org/survey">Slavery Footprint</a>
    3284. 

  3284.       allows consumers to visualize how their consumption habits are
    3285. 

  3285.       connected to modern-day slavery and provides them with an opportunity
    3286. 

  3286.       to have a deeper conversation with the companies that manufacture the
    3287. 

  3287.       goods they purchased.
    3288. 

  3288.       Based in Oakland, California, the Slavery Footprint team works to engage
    3289. 

  3289.       individuals, groups, and businesses to build awareness for and create
    3290. 

  3290.       deployable action against forced labor, human trafficking, and modern-day
    3291. 

  3291.       slavery through online tools, as well as off-line community education and
    3292. 

  3292.       mobilization programs.
    3293. 

  3293.     </p>
    3294. 

  3294. 

  3295.     <div style="text-align: center;">
    3296. 

  3296.       <a href="http://slaveryfootprint.org/survey">
    3297. 

  3297.         <img width="550" height="394" data-original="docs/images/slavery-footprint.png" alt="Slavery Footprint" class="example_image" />
    3298. 

  3298.       </a>
    3299. 

  3299.     </div>
    3300. 

  3300. 

  3301.     <h2 id="examples-stripe">Stripe</h2>
    3302. 

  3302. 

  3303.     <p>
    3304. 

  3304.       <a href="https://stripe.com">Stripe</a> provides an API for accepting
    3305. 

  3305.       credit cards on the web. Stripe's
    3306. 

  3306.       <a href="https://manage.stripe.com">management interface</a> was recently
    3307. 

  3307.       rewritten from scratch in CoffeeScript using Backbone.js as the primary
    3308. 

  3308.       framework, <a href="https://github.com/sstephenson/eco">Eco</a> for templates, <a href="http://sass-lang.com/">Sass</a> for stylesheets, and <a href="https://github.com/sstephenson/stitch">Stitch</a> to package
    3309. 

  3309.       everything together as <a href="http://commonjs.org/">CommonJS</a> modules. The new app uses
    3310. 

  3310.       <a href="https://stripe.com/docs/api">Stripe's API</a> directly for the
    3311. 

  3311.       majority of its actions; Backbone.js models made it simple to map
    3312. 

  3312.       client-side models to their corresponding RESTful resources.
    3313. 

  3313.     </p>
    3314. 

  3314. 

  3315.     <div style="text-align: center;">
    3316. 

  3316.       <a href="https://stripe.com">
    3317. 

  3317.         <img width="555" height="372" data-original="docs/images/stripe.png" alt="Stripe" class="example_image" />
    3318. 

  3318.       </a>
    3319. 

  3319.     </div>
    3320. 

  3320. 

  3321.     <h2 id="examples-airbnb">Airbnb</h2>
    3322. 

  3322. 

  3323.     <p>
    3324. 

  3324.       <a href="http://airbnb.com">Airbnb</a> uses Backbone in many of its products.
    3325. 

  3325.       It started with <a href="http://m.airbnb.com">Airbnb Mobile Web</a>
    3326. 

  3326.       (built in six weeks by a team of three) and has since grown to
    3327. 

  3327.       <a href="https://www.airbnb.com/wishlists/popular">Wish Lists</a>,
    3328. 

  3328.       <a href="http://www.airbnb.com/match">Match</a>,
    3329. 

  3329.       <a href="http://www.airbnb.com/s/">Search</a>, Communities, Payments, and
    3330. 

  3330.       Internal Tools.
    3331. 

  3331.     </p>
    3332. 

  3332. 

  3333.     <div style="text-align: center;">
    3334. 

  3334.       <a href="http://m.airbnb.com/">
    3335. 

  3335.         <img width="500" height="489" data-original="docs/images/airbnb.png" alt="Airbnb" class="example_image" />
    3336. 

  3336.       </a>
    3337. 

  3337.     </div>
    3338. 

  3338. 

  3339.     <h2 id="examples-diaspora">Diaspora</h2>
    3340. 

  3340. 

  3341.     <p>
    3342. 

  3342.       <a href="http://www.joindiaspora.com/">Diaspora</a> is a distributed social
    3343. 

  3343.       network, formed from a number of independently operated <i>pods</i>.
    3344. 

  3344.       You own your personal data, and control with whom you share.
    3345. 

  3345.       All of Diaspora is <a href="https://github.com/diaspora/diaspora">open-source</a>
    3346. 

  3346.       code, built with <a href="http://rubyonrails.org/">Rails</a> and Backbone.js.
    3347. 

  3347.     </p>
    3348. 

  3348. 

  3349.     <div style="text-align: center;">
    3350. 

  3350.       <a href="http://www.joindiaspora.com/">
    3351. 

  3351.         <img width="550" height="394" data-original="docs/images/diaspora.png" alt="Diaspora" class="example_image" />
    3352. 

  3352.       </a>
    3353. 

  3353.     </div>
    3354. 

  3354. 

  3355.     <h2 id="examples-soundcloud">SoundCloud Mobile</h2>
    3356. 

  3356. 

  3357.     <p>
    3358. 

  3358.       <a href="http://soundcloud.com">SoundCloud</a> is the leading sound sharing
    3359. 

  3359.       platform on the internet, and Backbone.js provides the foundation for
    3360. 

  3360.       <a href="http://m.soundcloud.com">SoundCloud Mobile</a>. The project uses
    3361. 

  3361.       the public SoundCloud <a href="http://soundcloud.com/developers">API</a>
    3362. 

  3362.       as a data source (channeled through a nginx proxy),
    3363. 

  3363.       <a href="http://api.jquery.com/category/plugins/templates/">jQuery templates</a>
    3364. 

  3364.       for the rendering, <a href="http://docs.jquery.com/Qunit">Qunit
    3365. 

  3365.       </a> and <a href="http://www.phantomjs.org/">PhantomJS</a> for
    3366. 

  3366.       the testing suite. The JS code, templates and CSS are built for the
    3367. 

  3367.       production deployment with various Node.js tools like
    3368. 

  3368.       <a href="https://github.com/dsimard/ready.js">ready.js</a>,
    3369. 

  3369.       <a href="https://github.com/mde/jake">Jake</a>,
    3370. 

  3370.       <a href="https://github.com/tmpvar/jsdom">jsdom</a>.
    3371. 

  3371.       The <b>Backbone.History</b> was modified to support the HTML5 <tt>history.pushState</tt>.
    3372. 

  3372.       <b>Backbone.sync</b> was extended with an additional SessionStorage based cache
    3373. 

  3373.       layer.
    3374. 

  3374.     </p>
    3375. 

  3375. 

  3376.     <div style="text-align: center;">
    3377. 

  3377.       <a href="http://m.soundcloud.com">
    3378. 

  3378.         <img width="266" height="500" data-original="docs/images/soundcloud.png" alt="SoundCloud" class="example_image" />
    3379. 

  3379.       </a>
    3380. 

  3380.     </div>
    3381. 

  3381. 

  3382.     <h2 id="examples-artsy">Art.sy</h2>
    3383. 

  3383. 

  3384.     <p>
    3385. 

  3385.       <a href="http://artsy.net">Art.sy</a> is a place to discover art you'll
    3386. 

  3386.       love. Art.sy is built on Rails, using
    3387. 

  3387.       <a href="https://github.com/intridea/grape">Grape</a> to serve a robust
    3388. 

  3388.       <a href="http://artsy.net/api">JSON API</a>. The main site is a single page
    3389. 

  3389.       app written in CoffeeScript and uses Backbone to provide structure around
    3390. 

  3390.       this API. An admin panel and partner CMS have also been extracted into
    3391. 

  3391.       their own API-consuming Backbone projects.
    3392. 

  3392.     </p>
    3393. 

  3393. 

  3394.     <div style="text-align: center;">
    3395. 

  3395.       <a href="http://artsy.net">
    3396. 

  3396.         <img width="550" height="550" data-original="docs/images/artsy.png" alt="Art.sy" class="example_image" />
    3397. 

  3397.       </a>
    3398. 

  3398.     </div>
    3399. 

  3399. 

  3400.     <h2 id="examples-pandora">Pandora</h2>
    3401. 

  3401. 

  3402.     <p>
    3403. 

  3403.       When <a href="http://www.pandora.com/newpandora">Pandora</a> redesigned
    3404. 

  3404.       their site in HTML5, they chose Backbone.js to help
    3405. 

  3405.       manage the user interface and interactions. For example, there's a model
    3406. 

  3406.       that represents the "currently playing track", and multiple views that
    3407. 

  3407.       automatically update when the current track changes. The station list is a
    3408. 

  3408.       collection, so that when stations are added or changed, the UI stays up to date.
    3409. 

  3409.     </p>
    3410. 

  3410. 

  3411.     <div style="text-align: center;">
    3412. 

  3412.       <a href="http://www.pandora.com/newpandora">
    3413. 

  3413.         <img width="476" height="359" data-original="docs/images/pandora.png" alt="Pandora" class="example_image" />
    3414. 

  3414.       </a>
    3415. 

  3415.     </div>
    3416. 

  3416. 

  3417.     <h2 id="examples-inkling">Inkling</h2>
    3418. 

  3418. 

  3419.     <p>
    3420. 

  3420.       <a href="http://inkling.com/">Inkling</a> is a cross-platform way to
    3421. 

  3421.       publish interactive learning content.
    3422. 

  3422.       <a href="https://www.inkling.com/read/">Inkling for Web</a> uses Backbone.js
    3423. 

  3423.       to make hundreds of complex books — from student textbooks to travel guides and
    3424. 

  3424.       programming manuals — engaging and accessible on the web. Inkling supports
    3425. 

  3425.       WebGL-enabled 3D graphics, interactive assessments, social sharing,
    3426. 

  3426.       and a system for running practice code right
    3427. 

  3427.       in the book, all within a single page Backbone-driven app. Early on, the
    3428. 

  3428.       team decided to keep the site lightweight by using only Backbone.js and
    3429. 

  3429.       raw JavaScript. The result? Complete source code weighing in at a mere
    3430. 

  3430.       350kb with feature-parity across the iPad, iPhone and web clients.
    3431. 

  3431.       Give it a try with
    3432. 

  3432.       <a href="https://www.inkling.com/read/javascript-definitive-guide-david-flanagan-6th/chapter-4/function-definition-expressions">this excerpt from JavaScript: The Definitive Guide</a>.
    3433. 

  3433.     </p>
    3434. 

  3434. 

  3435.     <div style="text-align: center;">
    3436. 

  3436.       <a href="http://inkling.com">
    3437. 

  3437.         <img width="550" height="361" data-original="docs/images/inkling.png" alt="Inkling" class="example_image" />
    3438. 

  3438.       </a>
    3439. 

  3439.     </div>
    3440. 

  3440. 

  3441.     <h2 id="examples-code-school">Code School</h2>
    3442. 

  3442. 

  3443.     <p>
    3444. 

  3444.       <a href="http://www.codeschool.com">Code School</a> courses teach people
    3445. 

  3445.       about various programming topics like <a href="http://coffeescript.org">CoffeeScript</a>, CSS, Ruby on Rails,
    3446. 

  3446.       and more. The new Code School course
    3447. 

  3447.       <a href="http://coffeescript.codeschool.com/levels/1/challenges/1">challenge page</a>
    3448. 

  3448.       is built from the ground up on Backbone.js, using
    3449. 

  3449.       everything it has to offer: the router, collections, models, and complex
    3450. 

  3450.       event handling. Before, the page was a mess of <a href="http://jquery.com/">jQuery</a> DOM manipulation
    3451. 

  3451.       and manual Ajax calls. Backbone.js helped introduce a new way to
    3452. 

  3452.       think about developing an organized front-end application in JavaScript.
    3453. 

  3453.     </p>
    3454. 

  3454. 

  3455.     <div style="text-align: center;">
    3456. 

  3456.       <a href="http://www.codeschool.com">
    3457. 

  3457.         <img width="550" height="482" data-original="docs/images/code-school.png" alt="Code School" class="example_image" />
    3458. 

  3458.       </a>
    3459. 

  3459.     </div>
    3460. 

  3460. 

  3461.     <h2 id="examples-cloudapp">CloudApp</h2>
    3462. 

  3462. 

  3463.     <p>
    3464. 

  3464.       <a href="http://getcloudapp.com">CloudApp</a> is simple file and link
    3465. 

  3465.       sharing for the Mac. Backbone.js powers the web tools
    3466. 

  3466.       which consume the <a href="http://developer.getcloudapp.com">documented API</a>
    3467. 

  3467.       to manage Drops. Data is either pulled manually or pushed by
    3468. 

  3468.       <a href="http://pusher.com">Pusher</a> and fed to
    3469. 

  3469.       <a href="http://github.com/janl/mustache.js">Mustache</a> templates for
    3470. 

  3470.       rendering. Check out the <a href="http://cloudapp.github.com/engine">annotated source code</a>
    3471. 

  3471.       to see the magic.
    3472. 

  3472.     </p>
    3473. 

  3473. 

  3474.     <div style="text-align: center;">
    3475. 

  3475.       <a href="http://getcloudapp.com">
    3476. 

  3476.         <img width="550" height="426" data-original="docs/images/cloudapp.png" alt="CloudApp" class="example_image" />
    3477. 

  3477.       </a>
    3478. 

  3478.     </div>
    3479. 

  3479. 

  3480.     <h2 id="examples-seatgeek">SeatGeek</h2>
    3481. 

  3481. 

  3482.     <p>
    3483. 

  3483.       <a href="http://seatgeek.com">SeatGeek</a>'s stadium ticket maps were originally
    3484. 

  3484.       developed with <a href="http://prototypejs.org/">Prototype.js</a>. Moving to Backbone.js and <a href="http://jquery.com/">jQuery</a> helped organize
    3485. 

  3485.       a lot of the UI code, and the increased structure has made adding features
    3486. 

  3486.       a lot easier. SeatGeek is also in the process of building a mobile
    3487. 

  3487.       interface that will be Backbone.js from top to bottom.
    3488. 

  3488.     </p>
    3489. 

  3489. 

  3490.     <div style="text-align: center;">
    3491. 

  3491.       <a href="http://seatgeek.com">
    3492. 

  3492.         <img width="550" height="455" data-original="docs/images/seatgeek.png" alt="SeatGeek" class="example_image" />
    3493. 

  3493.       </a>
    3494. 

  3494.     </div>
    3495. 

  3495. 

  3496.     <h2 id="examples-easel">Easel</h2>
    3497. 

  3497. 

  3498.     <p>
    3499. 

  3499.       <a href="http://easel.io">Easel</a> is an in-browser, high fidelity web
    3500. 

  3500.       design tool that integrates with your design and development
    3501. 

  3501.       process. The Easel team uses CoffeeScript, Underscore.js and Backbone.js for
    3502. 

  3502.       their <a href="http://easel.io/demo">rich visual editor</a> as well as other
    3503. 

  3503.       management functions throughout the site. The structure of Backbone allowed
    3504. 

  3504.       the team to break the complex problem of building a visual editor into
    3505. 

  3505.       manageable components and still move quickly.
    3506. 

  3506.     </p>
    3507. 

  3507. 

  3508.     <div style="text-align: center;">
    3509. 

  3509.       <a href="http://easel.io">
    3510. 

  3510.         <img width="550" height="395" data-original="docs/images/easel.png" alt="Easel" class="example_image" />
    3511. 

  3511.       </a>
    3512. 

  3512.     </div>
    3513. 

  3513. 

  3514.     <h2 id="examples-jolicloud">Jolicloud</h2>
    3515. 

  3515. 

  3516.     <p>
    3517. 

  3517.       <a href="http://www.jolicloud.com/">Jolicloud</a> is an open and independent
    3518. 

  3518.       platform and <a href="http://www.jolicloud.com/jolios">operating system</a>
    3519. 

  3519.       that provides music playback, video streaming, photo browsing and
    3520. 

  3520.       document editing &mdash; transforming low cost computers into beautiful cloud devices.
    3521. 

  3521.       The <a href="https://my.jolicloud.com/">new Jolicloud HTML5 app</a> was built
    3522. 

  3522.       from the ground up using Backbone and talks to the
    3523. 

  3523.       <a href="http://developers.jolicloud.com">Jolicloud Platform</a>, which is
    3524. 

  3524.       based on Node.js. Jolicloud works offline using the HTML5 AppCache, extends
    3525. 

  3525.       Backbone.sync to store data in IndexedDB or localStorage, and communicates
    3526. 

  3526.       with the <a href="http://www.jolicloud.com/jolios">Joli OS</a> via WebSockets.
    3527. 

  3527.     </p>
    3528. 

  3528. 

  3529.     <div style="text-align: center;">
    3530. 

  3530.       <a href="http://jolicloud.com/">
    3531. 

  3531.         <img width="510" height="384" data-original="docs/images/jolicloud.jpg" alt="Jolicloud" class="example_retina" />
    3532. 

  3532.       </a>
    3533. 

  3533.     </div>
    3534. 

  3534. 

  3535.     <h2 id="examples-syllabus">Syllabus</h2>
    3536. 

  3536. 

  3537.     <p>
    3538. 

  3538.       <a href="http://product.voxmedia.com/post/25113965826/introducing-syllabus-vox-medias-s3-powered-liveblog">Syllabus</a>
    3539. 

  3539.       is the new live blogging platform used by
    3540. 

  3540.       <a href="http://www.theverge.com/">The Verge</a>
    3541. 

  3541.       and other <a href="http://www.voxmedia.com/">Vox Media</a> sites.
    3542. 

  3542.       Syllabus uses Backbone on both ends: an editorial dashboard and the live blog
    3543. 

  3543.       page itself. In the back, Backbone is used to provide a
    3544. 

  3544.       single-page experience for uploading, writing, editing and publishing content.
    3545. 

  3545.       On the live blog, Backbone manages fetching a JSON API feed, and updating
    3546. 

  3546.       the infinite-scrolling river of updates with new and revised content.
    3547. 

  3547.     </p>
    3548. 

  3548. 

  3549.     <div style="text-align: center;">
    3550. 

  3550.       <a href="http://live.theverge.com/">
    3551. 

  3551.         <img width="510" height="354" data-original="docs/images/syllabus.jpg" alt="Syllabus" class="example_retina" />
    3552. 

  3552.       </a>
    3553. 

  3553.     </div>
    3554. 

  3554. 

  3555.     <h2 id="examples-salon">Salon.io</h2>
    3556. 

  3556. 

  3557.     <p>
    3558. 

  3558.       <a href="http://salon.io">Salon.io</a> provides a space where photographers,
    3559. 

  3559.       artists and designers freely arrange their visual art on virtual walls.
    3560. 

  3560.       <a href="http://salon.io">Salon.io</a> runs on <a href="http://rubyonrails.org/">Rails</a>, but does not use
    3561. 

  3561.       much of the traditional stack, as the entire frontend is designed as a
    3562. 

  3562.       single page web app, using Backbone.js, <a href="http://brunch.io/">Brunch</a> and
    3563. 

  3563.       <a href="http://coffeescript.org">CoffeeScript</a>.
    3564. 

  3564.     </p>
    3565. 

  3565. 

  3566.     <div style="text-align: center;">
    3567. 

  3567.       <a href="http://salon.io">
    3568. 

  3568.         <img width="550" height="483" data-original="docs/images/salon.png" alt="Salon.io" class="example_image" />
    3569. 

  3569.       </a>
    3570. 

  3570.     </div>
    3571. 

  3571. 

  3572.     <h2 id="examples-tilemill">TileMill</h2>
    3573. 

  3573. 

  3574.     <p>
    3575. 

  3575.       Our fellow
    3576. 

  3576.       <a href="http://www.newschallenge.org/">Knight Foundation News Challenge</a>
    3577. 

  3577.       winners, <a href="http://mapbox.com/">MapBox</a>, created an open-source
    3578. 

  3578.       map design studio with Backbone.js:
    3579. 

  3579.       <a href="http://mapbox.github.com/tilemill/">TileMill</a>.
    3580. 

  3580.       TileMill lets you manage map layers based on shapefiles and rasters, and
    3581. 

  3581.       edit their appearance directly in the browser with the
    3582. 

  3582.       <a href="https://github.com/mapbox/carto">Carto styling language</a>.
    3583. 

  3583.       Note that the gorgeous <a href="http://mapbox.com/">MapBox</a> homepage
    3584. 

  3584.       is also a Backbone.js app.
    3585. 

  3585.     </p>
    3586. 

  3586. 

  3587.     <div style="text-align: center;">
    3588. 

  3588.       <a href="http://mapbox.github.com/tilemill/">
    3589. 

  3589.         <img width="544" height="375" data-original="docs/images/tilemill.png" alt="TileMill" class="example_image" />
    3590. 

  3590.       </a>
    3591. 

  3591.     </div>
    3592. 

  3592. 

  3593.     <h2 id="examples-blossom">Blossom</h2>
    3594. 

  3594. 

  3595.     <p>
    3596. 

  3596.       <a href="http://blossom.io">Blossom</a> is a lightweight project management
    3597. 

  3597.       tool for lean teams. Backbone.js is heavily used in combination with
    3598. 

  3598.       <a href="http://coffeescript.org">CoffeeScript</a> to provide a smooth
    3599. 

  3599.       interaction experience. The app is packaged with <a href="http://brunch.io">Brunch</a>.
    3600. 

  3600.       The RESTful backend is built with <a href="http://flask.pocoo.org/">Flask</a> on Google App Engine.
    3601. 

  3601.     </p>
    3602. 

  3602. 

  3603.     <div style="text-align: center;">
    3604. 

  3604.       <a href="http://blossom.io">
    3605. 

  3605.         <img width="550" height="367" data-original="docs/images/blossom.png" alt="Blossom" class="example_image" />
    3606. 

  3606.       </a>
    3607. 

  3607.     </div>
    3608. 

  3608. 

  3609.     <h2 id="examples-trello">Trello</h2>
    3610. 

  3610. 

  3611.     <p>
    3612. 

  3612.       <a href="http://trello.com">Trello</a> is a collaboration tool that
    3613. 

  3613.       organizes your projects into boards. A Trello board holds many lists of
    3614. 

  3614.       cards, which can contain checklists, files and conversations, and may be
    3615. 

  3615.       voted on and organized with labels. Updates on the board happen in
    3616. 

  3616.       real time. The site was built ground up using Backbone.js for all the
    3617. 

  3617.       models, views, and routes.
    3618. 

  3618.     </p>
    3619. 

  3619. 

  3620.     <div style="text-align: center;">
    3621. 

  3621.       <a href="http://trello.com">
    3622. 

  3622.         <img width="550" height="416" data-original="docs/images/trello.png" alt="Trello" class="example_image" />
    3623. 

  3623.       </a>
    3624. 

  3624.     </div>
    3625. 

  3625. 

  3626.     <h2 id="examples-tzigla">Tzigla</h2>
    3627. 

  3627. 

  3628.     <p>
    3629. 

  3629.       <a href="http://twitter.com/evilchelu">Cristi Balan</a> and
    3630. 

  3630.       <a href="http://dira.ro">Irina Dumitrascu</a> created
    3631. 

  3631.       <a href="http://tzigla.com">Tzigla</a>, a collaborative drawing
    3632. 

  3632.       application where artists make tiles that connect to each other to
    3633. 

  3633.       create <a href="http://tzigla.com/boards/1">surreal drawings</a>.
    3634. 

  3634.       Backbone models help organize the code, routers provide
    3635. 

  3635.       <a href="http://tzigla.com/boards/1#!/tiles/2-2">bookmarkable deep links</a>,
    3636. 

  3636.       and the views are rendered with
    3637. 

  3637.       <a href="https://github.com/creationix/haml-js">haml.js</a> and
    3638. 

  3638.       <a href="http://zeptojs.com/">Zepto</a>.
    3639. 

  3639.       Tzigla is written in Ruby (<a href="http://rubyonrails.org/">Rails</a>) on the backend, and
    3640. 

  3640.       <a href="http://coffeescript.org">CoffeeScript</a> on the frontend, with
    3641. 

  3641.       <a href="http://documentcloud.github.com/jammit/">Jammit</a>
    3642. 

  3642.       prepackaging the static assets.
    3643. 

  3643.     </p>
    3644. 

  3644. 

  3645.     <div style="text-align: center;">
    3646. 

  3646.       <a href="http://www.tzigla.com/">
    3647. 

  3647.         <img width="550" height="376" data-original="docs/images/tzigla.png" alt="Tzigla" class="example_image" />
    3648. 

  3648.       </a>
    3649. 

  3649.     </div>
    3650. 

  3650. 

  3651.     <h2 id="faq">F.A.Q.</h2>
    3652. 

  3652. 

  3653.     <p id="FAQ-why-backbone">
    3654. 

  3654.       <b class="header">Why use Backbone, not [other framework X]?</b>
    3655. 

  3655.       <br />
    3656. 

  3656.       If your eye hasn't already been caught by the adaptability and elan on display
    3657. 

  3657.       in the above <a href="#examples">list of examples</a>, we can get more specific:
    3658. 

  3658.       Backbone.js aims to provide the common foundation that data-rich web applications
    3659. 

  3659.       with ambitious interfaces require &mdash; while very deliberately avoiding
    3660. 

  3660.       painting you into a corner by making any decisions that you're
    3661. 

  3661.       better equipped to make yourself.
    3662. 

  3662.     </p>
    3663. 

  3663. 

  3664.     <ul>
    3665. 

  3665.       <li>
    3666. 

  3666.         The focus is on supplying you with
    3667. 

  3667.         <a href="#Collection-Underscore-Methods">helpful methods to manipulate and
    3668. 

  3668.         query your data</a>, not on HTML widgets or reinventing the JavaScript
    3669. 

  3669.         object model.
    3670. 

  3670.       </li>
    3671. 

  3671.       <li>
    3672. 

  3672.         Backbone does not force you to use a single template engine. Views can bind
    3673. 

  3673.         to HTML constructed in
    3674. 

  3674.         <a href="http://underscorejs.org/#template">your</a>
    3675. 

  3675.         <a href="http://guides.rubyonrails.org/layouts_and_rendering.html">favorite</a>
    3676. 

  3676.         <a href="http://mustache.github.com">way</a>.
    3677. 

  3677.       </li>
    3678. 

  3678.       <li>
    3679. 

  3679.         It's smaller. There are fewer kilobytes for your browser or phone to download,
    3680. 

  3680.         and less <i>conceptual</i> surface area. You can read and understand
    3681. 

  3681.         the source in an afternoon.
    3682. 

  3682.       </li>
    3683. 

  3683.       <li>
    3684. 

  3684.         It doesn't depend on stuffing application logic into your HTML.
    3685. 

  3685.         There's no embedded JavaScript, template logic, or binding hookup code in
    3686. 

  3686.         <tt>data-</tt> or <tt>ng-</tt> attributes, and no need to invent your own HTML tags.
    3687. 

  3687.       </li>
    3688. 

  3688.       <li>
    3689. 

  3689.         <a href="#Events">Synchronous events</a> are used as the fundamental
    3690. 

  3690.         building block, not a difficult-to-reason-about run loop, or by constantly
    3691. 

  3691.         polling and traversing your data structures to hunt for changes. And if
    3692. 

  3692.         you want a specific event to be asynchronous and aggregated,
    3693. 

  3693.         <a href="http://underscorejs.org/#debounce">no problem</a>.
    3694. 

  3694.       </li>
    3695. 

  3695.       <li>
    3696. 

  3696.         Backbone scales well, from <a href="http://disqus.com">embedded widgets</a>
    3697. 

  3697.         to <a href="http://www.usatoday.com">massive apps</a>.
    3698. 

  3698.       </li>
    3699. 

  3699.       <li>
    3700. 

  3700.         Backbone is a library, not a framework, and plays well with others.
    3701. 

  3701.         You can embed Backbone widgets in Dojo apps without trouble, or use Backbone
    3702. 

  3702.         models as the data backing for D3 visualizations (to pick two entirely
    3703. 

  3703.         random examples).
    3704. 

  3704.       </li>
    3705. 

  3705.       <li>
    3706. 

  3706.         "Two way data-binding" is avoided. While it certainly makes for a nifty
    3707. 

  3707.         demo, and works for the most basic CRUD, it doesn't tend to be terribly
    3708. 

  3708.         useful in your real-world app. Sometimes you want to update on
    3709. 

  3709.         every keypress, sometimes on blur, sometimes when the panel is closed,
    3710. 

  3710.         and sometimes when the "save" button is clicked. In almost all cases, simply
    3711. 

  3711.         serializing the form to JSON is faster and easier. All that aside, if your
    3712. 

  3712.         heart is set, <a href="http://rivetsjs.com">go</a>
    3713. 

  3713.         <a href="http://nytimes.github.com/backbone.stickit/">for it</a>.
    3714. 

  3714.       </li>
    3715. 

  3715.       <li>
    3716. 

  3716.         There's no built-in performance penalty for choosing to structure your
    3717. 

  3717.         code with Backbone. And if you do want to optimize further, thin models and
    3718. 

  3718.         templates with flexible granularity make it easy to squeeze every last
    3719. 

  3719.         drop of potential performance out of, say, IE8.
    3720. 

  3720.       </li>
    3721. 

  3721.     </ul>
    3722. 

  3722. 

  3723.     <p id="FAQ-tim-toady">
    3724. 

  3724.       <b class="header">There's More Than One Way To Do It</b>
    3725. 

  3725.       <br />
    3726. 

  3726.       It's common for folks just getting started to treat the examples listed
    3727. 

  3727.       on this page as some sort of gospel truth. In fact, Backbone.js is intended
    3728. 

  3728.       to be fairly agnostic about many common patterns in client-side code.
    3729. 

  3729.       For example...
    3730. 

  3730.     </p>
    3731. 

  3731. 

  3732.     <p>
    3733. 

  3733.       <b>References between Models and Views</b> can be handled several ways.
    3734. 

  3734.       Some people like to have direct pointers, where views correspond 1:1 with
    3735. 

  3735.       models (<tt>model.view</tt> and <tt>view.model</tt>). Others prefer to have intermediate
    3736. 

  3736.       "controller" objects that orchestrate the creation and organization of
    3737. 

  3737.       views into a hierarchy. Others still prefer the evented approach, and always
    3738. 

  3738.       fire events instead of calling methods directly. All of these styles work well.
    3739. 

  3739.     </p>
    3740. 

  3740. 

  3741.     <p>
    3742. 

  3742.       <b>Batch operations</b> on Models are common, but often best handled differently
    3743. 

  3743.       depending on your server-side setup. Some folks don't mind making individual
    3744. 

  3744.       Ajax requests. Others create explicit resources for RESTful batch operations:
    3745. 

  3745.       <tt>/notes/batch/destroy?ids=1,2,3,4</tt>. Others tunnel REST over JSON, with the
    3746. 

  3746.       creation of "changeset" requests:
    3747. 

  3747.     </p>
    3748. 

  3748. 

  3749. <pre>
    3750. 

  3750.   {
    3751. 

  3751.     "create":  [array of models to create]
    3752. 

  3752.     "update":  [array of models to update]
    3753. 

  3753.     "destroy": [array of model ids to destroy]
    3754. 

  3754.   }
    3755. 

  3755. </pre>
    3756. 

  3756. 

  3757.     <p>
    3758. 

  3758.       <b>Feel free to define your own events.</b> <a href="#Events">Backbone.Events</a>
    3759. 

  3759.       is designed so that you can mix it in to any JavaScript object or prototype.
    3760. 

  3760.       Since you can use any string as an event, it's often handy to bind
    3761. 

  3761.       and trigger your own custom events: <tt>model.on("selected:true")</tt> or
    3762. 

  3762.       <tt>model.on("editing")</tt>
    3763. 

  3763.     </p>
    3764. 

  3764. 

  3765.     <p>
    3766. 

  3766.       <b>Render the UI</b> as you see fit. Backbone is agnostic as to whether you
    3767. 

  3767.       use <a href="http://underscorejs.org/#template">Underscore templates</a>,
    3768. 

  3768.       <a href="https://github.com/janl/mustache.js">Mustache.js</a>, direct DOM
    3769. 

  3769.       manipulation, server-side rendered snippets of HTML, or
    3770. 

  3770.       <a href="http://jqueryui.com/">jQuery UI</a> in your <tt>render</tt> function.
    3771. 

  3771.       Sometimes you'll create a view for each model ... sometimes you'll have a
    3772. 

  3772.       view that renders thousands of models at once, in a tight loop. Both can be
    3773. 

  3773.       appropriate in the same app, depending on the quantity of data involved,
    3774. 

  3774.       and the complexity of the UI.
    3775. 

  3775.     </p>
    3776. 

  3776. 

  3777.     <p id="FAQ-nested">
    3778. 

  3778.       <b class="header">Nested Models &amp; Collections</b>
    3779. 

  3779.       <br />
    3780. 

  3780.       It's common to nest collections inside of models with Backbone. For example,
    3781. 

  3781.       consider a <tt>Mailbox</tt> model that contains many <tt>Message</tt> models.
    3782. 

  3782.       One nice pattern for handling this is have a <tt>this.messages</tt> collection
    3783. 

  3783.       for each mailbox, enabling the lazy-loading of messages, when the mailbox
    3784. 

  3784.       is first opened ... perhaps with <tt>MessageList</tt> views listening for
    3785. 

  3785.       <tt>"add"</tt> and <tt>"remove"</tt> events.
    3786. 

  3786.     </p>
    3787. 

  3787. 

  3788. <pre>
    3789. 

  3789. var Mailbox = Backbone.Model.extend({
    3790. 

  3790. 

  3791.   initialize: function() {
    3792. 

  3792.     this.messages = new Messages;
    3793. 

  3793.     this.messages.url = '/mailbox/' + this.id + '/messages';
    3794. 

  3794.     this.messages.on("reset", this.updateCounts);
    3795. 

  3795.   },
    3796. 

  3796. 

  3797.   ...
    3798. 

  3798. 

  3799. });
    3800. 

  3800. 

  3801. var inbox = new Mailbox;
    3802. 

  3802. 

  3803. // And then, when the Inbox is opened:
    3804. 

  3804. 

  3805. inbox.messages.fetch({reset: true});
    3806. 

  3806. </pre>
    3807. 

  3807. 

  3808.     <p>
    3809. 

  3809.       If you're looking for something more opinionated, there are a number of
    3810. 

  3810.       Backbone plugins that add sophisticated associations among models,
    3811. 

  3811.       <a href="https://github.com/jashkenas/backbone/wiki/Extensions%2C-Plugins%2C-Resources">available on the wiki</a>.
    3812. 

  3812.     </p>
    3813. 

  3813. 

  3814.     <p>
    3815. 

  3815.       Backbone doesn't include direct support for nested models and collections
    3816. 

  3816.       or "has many" associations because there are a number
    3817. 

  3817.       of good patterns for modeling structured data on the client side, and
    3818. 

  3818.       <i>Backbone should provide the foundation for implementing any of them.</i>
    3819. 

  3819.       You may want to&hellip;
    3820. 

  3820.     </p>
    3821. 

  3821. 

  3822.     <ul>
    3823. 

  3823.       <li>
    3824. 

  3824.         Mirror an SQL database's structure, or the structure of a NoSQL database.
    3825. 

  3825.       </li>
    3826. 

  3826.       <li>
    3827. 

  3827.         Use models with arrays of "foreign key" ids, and join to top level
    3828. 

  3828.         collections (a-la tables).
    3829. 

  3829.       </li>
    3830. 

  3830.       <li>
    3831. 

  3831.         For associations that are numerous, use a range of ids instead of an
    3832. 

  3832.         explicit list.
    3833. 

  3833.       </li>
    3834. 

  3834.       <li>
    3835. 

  3835.         Avoid ids, and use direct references, creating a partial object graph
    3836. 

  3836.         representing your data set.
    3837. 

  3837.       </li>
    3838. 

  3838.       <li>
    3839. 

  3839.         Lazily load joined models from the server, or lazily deserialize nested
    3840. 

  3840.         models from JSON documents.
    3841. 

  3841.       </li>
    3842. 

  3842.     </ul>
    3843. 

  3843. 

  3844.     <p id="FAQ-bootstrap">
    3845. 

  3845.       <b class="header">Loading Bootstrapped Models</b>
    3846. 

  3846.       <br />
    3847. 

  3847.       When your app first loads, it's common to have a set of initial models that
    3848. 

  3848.       you know you're going to need, in order to render the page. Instead of
    3849. 

  3849.       firing an extra AJAX request to <a href="#Collection-fetch">fetch</a> them,
    3850. 

  3850.       a nicer pattern is to have their data already bootstrapped into the page.
    3851. 

  3851.       You can then use <a href="#Collection-reset">reset</a> to populate your
    3852. 

  3852.       collections with the initial data. At DocumentCloud, in the
    3853. 

  3853.       <a href="http://en.wikipedia.org/wiki/ERuby">ERB</a> template for the
    3854. 

  3854.       workspace, we do something along these lines:
    3855. 

  3855.     </p>
    3856. 

  3856. 

  3857. <pre>
    3858. 

  3858. &lt;script&gt;
    3859. 

  3859.   var accounts = new Backbone.Collection;
    3860. 

  3860.   accounts.reset(&lt;%= @accounts.to_json %&gt;);
    3861. 

  3861.   var projects = new Backbone.Collection;
    3862. 

  3862.   projects.reset(&lt;%= @projects.to_json(:collaborators => true) %&gt;);
    3863. 

  3863. &lt;/script&gt;
    3864. 

  3864. </pre>
    3865. 

  3865. 

  3866.     <p>You have to <a href="http://mathiasbynens.be/notes/etago">escape</a>
    3867. 

  3867.     <tt>&lt;/</tt> within the JSON string, to prevent javascript injection
    3868. 

  3868.     attacks.
    3869. 

  3869. 

  3870.     <p id="FAQ-extending">
    3871. 

  3871.       <b class="header">Extending Backbone</b>
    3872. 

  3872.       <br />
    3873. 

  3873.       Many JavaScript libraries are meant to be insular and self-enclosed,
    3874. 

  3874.       where you interact with them by calling their public API, but never peek
    3875. 

  3875.       inside at the guts. Backbone.js is <i>not</i> that kind of library.
    3876. 

  3876.     </p>
    3877. 

  3877. 

  3878.     <p>
    3879. 

  3879.       Because it serves as a foundation for your application, you're meant to
    3880. 

  3880.       extend and enhance it in the ways you see fit &mdash; the entire source
    3881. 

  3881.       code is <a href="docs/backbone.html">annotated</a> to make this easier
    3882. 

  3882.       for you. You'll find that there's very little there apart from core
    3883. 

  3883.       functions, and most of those can be overriden or augmented should you find
    3884. 

  3884.       the need. If you catch yourself adding methods to <tt>Backbone.Model.prototype</tt>,
    3885. 

  3885.       or creating your own base subclass, don't worry &mdash; that's how things are
    3886. 

  3886.       supposed to work.
    3887. 

  3887.     </p>
    3888. 

  3888. 

  3889.     <p id="FAQ-mvc">
    3890. 

  3890.       <b class="header">How does Backbone relate to "traditional" MVC?</b>
    3891. 

  3891.       <br />
    3892. 

  3892.       Different implementations of the
    3893. 

  3893.       <a href="http://en.wikipedia.org/wiki/Model–View–Controller">Model-View-Controller</a>
    3894. 

  3894.       pattern tend to disagree about the definition of a controller. If it helps any, in
    3895. 

  3895.       Backbone, the <a href="#View">View</a> class can also be thought of as a
    3896. 

  3896.       kind of controller, dispatching events that originate from the UI, with
    3897. 

  3897.       the HTML template serving as the true view. We call it a View because it
    3898. 

  3898.       represents a logical chunk of UI, responsible for the contents of a single
    3899. 

  3899.       DOM element.
    3900. 

  3900.     </p>
    3901. 

  3901. 

  3902.     <p>
    3903. 

  3903.       Comparing the overall structure of Backbone to a server-side MVC framework
    3904. 

  3904.       like <b>Rails</b>, the pieces line up like so:
    3905. 

  3905.     </p>
    3906. 

  3906. 

  3907.     <ul>
    3908. 

  3908.       <li>
    3909. 

  3909.         <b>Backbone.Model</b> &ndash; Like a Rails model minus the class
    3910. 

  3910.         methods. Wraps a row of data in business logic.
    3911. 

  3911.       </li>
    3912. 

  3912.       <li>
    3913. 

  3913.         <b>Backbone.Collection</b> &ndash; A group of models on the client-side,
    3914. 

  3914.         with sorting/filtering/aggregation logic.
    3915. 

  3915.       </li>
    3916. 

  3916.       <li>
    3917. 

  3917.         <b>Backbone.Router</b> &ndash; Rails <tt>routes.rb</tt> + Rails controller
    3918. 

  3918.         actions. Maps URLs to functions.
    3919. 

  3919.       </li>
    3920. 

  3920.       <li>
    3921. 

  3921.         <b>Backbone.View</b> &ndash; A logical, re-usable piece of UI. Often,
    3922. 

  3922.         but not always, associated with a model.
    3923. 

  3923.       </li>
    3924. 

  3924.       <li>
    3925. 

  3925.         <b>Client-side Templates</b> &ndash; Rails <tt>.html.erb</tt> views,
    3926. 

  3926.         rendering a chunk of HTML.
    3927. 

  3927.       </li>
    3928. 

  3928.     </ul>
    3929. 

  3929. 

  3930.     <p id="FAQ-this">
    3931. 

  3931.       <b class="header">Binding "this"</b>
    3932. 

  3932.       <br />
    3933. 

  3933.       Perhaps the single most common JavaScript "gotcha" is the fact that when
    3934. 

  3934.       you pass a function as a callback, its value for <tt>this</tt> is lost. With
    3935. 

  3935.       Backbone, when dealing with <a href="#Events">events</a> and callbacks,
    3936. 

  3936.       you'll often find it useful to rely on
    3937. 

  3937.       <a href="http://underscorejs.org/#bind">_.bind</a> and
    3938. 

  3938.       <a href="http://underscorejs.org/#bindAll">_.bindAll</a>
    3939. 

  3939.       from Underscore.js.
    3940. 

  3940.     </p>
    3941. 

  3941. 

  3942.     <p>
    3943. 

  3943.       When binding callbacks to Backbone events, you can choose to pass an optional
    3944. 

  3944.       third argument to specify the <tt>this</tt> that will be used when the
    3945. 

  3945.       callback is later invoked:
    3946. 

  3946.     </p>
    3947. 

  3947. 

  3948. <pre>
    3949. 

  3949. var MessageList = Backbone.View.extend({
    3950. 

  3950. 

  3951.   initialize: function() {
    3952. 

  3952.     var messages = this.collection;
    3953. 

  3953.     messages.on("reset", this.render, this);
    3954. 

  3954.     messages.on("add", this.addMessage, this);
    3955. 

  3955.     messages.on("remove", this.removeMessage, this);
    3956. 

  3956.   }
    3957. 

  3957. 

  3958. });
    3959. 

  3959. 

  3960. // Later, in the app...
    3961. 

  3961. 

  3962. Inbox.messages.add(newMessage);
    3963. 

  3963. </pre>
    3964. 

  3964. 

  3965.     <p id="FAQ-rails">
    3966. 

  3966.       <b class="header">Working with Rails</b>
    3967. 

  3967.       <br />
    3968. 

  3968.       Backbone.js was originally extracted from
    3969. 

  3969.       <a href="http://www.documentcloud.org">a Rails application</a>; getting
    3970. 

  3970.       your client-side (Backbone) Models to sync correctly with your server-side
    3971. 

  3971.       (Rails) Models is painless, but there are still a few things to be aware of.
    3972. 

  3972.     </p>
    3973. 

  3973. 

  3974.     <p>
    3975. 

  3975.       By default, Rails versions prior to 3.1 add an extra layer of wrapping
    3976. 

  3976.       around the JSON representation of models. You can disable this wrapping
    3977. 

  3977.       by setting:
    3978. 

  3978.     </p>
    3979. 

  3979. 

  3980. <pre>
    3981. 

  3981. ActiveRecord::Base.include_root_in_json = false
    3982. 

  3982. </pre>
    3983. 

  3983. 

  3984.     <p>
    3985. 

  3985.       ... in your configuration. Otherwise, override
    3986. 

  3986.       <a href="#Model-parse">parse</a> to pull model attributes out of the
    3987. 

  3987.       wrapper. Similarly, Backbone PUTs and POSTs direct JSON representations
    3988. 

  3988.       of models, where by default Rails expects namespaced attributes. You can
    3989. 

  3989.       have your controllers filter attributes directly from <tt>params</tt>, or
    3990. 

  3990.       you can override <a href="#Model-toJSON">toJSON</a> in Backbone to add
    3991. 

  3991.       the extra wrapping Rails expects.
    3992. 

  3992.     </p>
    3993. 

  3993. 

  3994.     <h2 id="changelog">Change Log</h2>
    3995. 

  3995. 

  3996.     <b class="header">1.1.0</b> &mdash; <small><i>Oct. 10, 2013</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/1.0.0...1.1.0">Diff</a><br />
    3997. 

  3997.     <ul style="margin-top: 5px;">
    3998. 

  3998.       <li>
    3999. 

  3999.         Made the return values of Collection's <tt>set</tt>, <tt>add</tt>, 
    4000. 

  4000.         <tt>remove</tt>, and <tt>reset</tt> more useful. Instead of returning
    4001. 

  4001.         <tt>this</tt>, they now return the changed (added, removed or updated) 
    4002. 

  4002.         model or list of models.
    4003. 

  4003.       </li>
    4004. 

  4004.       <li>
    4005. 

  4005.         Backbone Views no longer attach "special" options as direct properties
    4006. 

  4006.         on the view (<tt>model</tt>, <tt>attributes</tt>, <tt>className</tt>, and so on).
    4007. 

  4007.       </li>
    4008. 

  4008.       <li>
    4009. 

  4009.         All <tt>"invalid"</tt> events now pass consistent arguments. First the
    4010. 

  4010.         model in question, then the error object, then options.
    4011. 

  4011.       </li>
    4012. 

  4012.       <li>
    4013. 

  4013.         You are no longer permitted to change the <b>id</b> of your model during
    4014. 

  4014.         <tt>parse</tt>. Use <tt>idAttribute</tt> instead.
    4015. 

  4015.       </li>
    4016. 

  4016.       <li>
    4017. 

  4017.         On the other hand, <tt>parse</tt> is now an excellent place to extract
    4018. 

  4018.         and vivify incoming nested JSON into associated submodels.
    4019. 

  4019.       </li>
    4020. 

  4020.       <li>
    4021. 

  4021.         Many tweaks, optimizations and bugfixes relating to Backbone 1.0, 
    4022. 

  4022.         including URL overrides, mutation of options, bulk ordering, trailing
    4023. 

  4023.         slashes, edge-case listener leaks, nested model parsing...
    4024. 

  4024.       </li>
    4025. 

  4025.     </ul>
    4026. 

  4026. 

  4027.     <b class="header">1.0.0</b> &mdash; <small><i>March 20, 2013</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.9.10...1.0.0">Diff</a><br />
    4028. 

  4028.     <ul style="margin-top: 5px;">
    4029. 

  4029.       <li>
    4030. 

  4030.         Renamed Collection's "update" to <a href="#Collection-set">set</a>, for
    4031. 

  4031.         parallelism with the similar <tt>model.set()</tt>, and contrast with
    4032. 

  4032.         <a href="#Collection-reset">reset</a>. It's now the default
    4033. 

  4033.         updating mechanism after a <a href="#Collection-fetch">fetch</a>. If you'd
    4034. 

  4034.         like to continue using "reset", pass <tt>{reset: true}</tt>.
    4035. 

  4035.       </li>
    4036. 

  4036.       <li>
    4037. 

  4037.         Your route handlers will now receive their URL parameters pre-decoded.
    4038. 

  4038.       </li>
    4039. 

  4039.       <li>
    4040. 

  4040.         Added <a href="#Events-listenToOnce">listenToOnce</a> as the analogue of
    4041. 

  4041.         <a href="#Events-once">once</a>.
    4042. 

  4042.       </li>
    4043. 

  4043.       <li>
    4044. 

  4044.         Added the <a href="#Collection-findWhere">findWhere</a> method to Collections,
    4045. 

  4045.         similar to <a href="#Collection-where">where</a>.
    4046. 

  4046.       </li>
    4047. 

  4047.       <li>
    4048. 

  4048.         Added the <tt>keys</tt>, <tt>values</tt>, <tt>pairs</tt>, <tt>invert</tt>,
    4049. 

  4049.         <tt>pick</tt>, and <tt>omit</tt> Underscore.js methods to Backbone Models.
    4050. 

  4050.       </li>
    4051. 

  4051.       <li>
    4052. 

  4052.         The routes in a Router's route map may now be function literals,
    4053. 

  4053.         instead of references to methods, if you like.
    4054. 

  4054.       </li>
    4055. 

  4055.       <li>
    4056. 

  4056.         <tt>url</tt> and <tt>urlRoot</tt> properties may now be passed as options
    4057. 

  4057.         when instantiating a new Model.
    4058. 

  4058.       </li>
    4059. 

  4059.     </ul>
    4060. 

  4060. 

  4061.     <b class="header">0.9.10</b> &mdash; <small><i>Jan. 15, 2013</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.9.9...0.9.10">Diff</a><br />
    4062. 

  4062.     <ul style="margin-top: 5px;">
    4063. 

  4063.       <li>
    4064. 

  4064.         A <tt>"route"</tt> event is triggered on the router in addition
    4065. 

  4065.         to being fired on <tt>Backbone.history</tt>.
    4066. 

  4066.       </li>
    4067. 

  4067.       <li>
    4068. 

  4068.         Model validation is now only enforced by default in
    4069. 

  4069.         <tt>Model#save</tt> and no longer enforced by default upon
    4070. 

  4070.         construction or in <tt>Model#set</tt>, unless the <tt>{validate:true}</tt>
    4071. 

  4071.         option is passed.
    4072. 

  4072.       </li>
    4073. 

  4073.       <li>
    4074. 

  4074.         <tt>View#make</tt> has been removed. You'll need to use <tt>$</tt> directly to
    4075. 

  4075.         construct DOM elements now.
    4076. 

  4076.       </li>
    4077. 

  4077.       <li>
    4078. 

  4078.         Passing <tt>{silent:true}</tt> on change will no longer delay individual
    4079. 

  4079.         <tt>"change:attr"</tt> events, instead they are silenced entirely.
    4080. 

  4080.       </li>
    4081. 

  4081.       <li>
    4082. 

  4082.         The <tt>Model#change</tt> method has been removed, as delayed attribute
    4083. 

  4083.         changes as no longer available.
    4084. 

  4084.       </li>
    4085. 

  4085.       <li>
    4086. 

  4086.         Bug fix on <tt>change</tt> where attribute comparison uses <tt>!==</tt>
    4087. 

  4087.         instead of <tt>_.isEqual</tt>.
    4088. 

  4088.       </li>
    4089. 

  4089.       <li>
    4090. 

  4090.         Bug fix where an empty response from the server on save would not call
    4091. 

  4091.         the success function.
    4092. 

  4092.       </li>
    4093. 

  4093.       <li>
    4094. 

  4094.         <tt>parse</tt> now receives <tt>options</tt> as its second argument.
    4095. 

  4095.       </li>
    4096. 

  4096.       <li>
    4097. 

  4097.         Model validation now fires <tt>invalid</tt> event instead of
    4098. 

  4098.         <tt>error</tt>.
    4099. 

  4099.       </li>
    4100. 

  4100.     </ul>
    4101. 

  4101. 

  4102.     <b class="header">0.9.9</b> &mdash; <small><i>Dec. 13, 2012</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.9.2...0.9.9">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.9.9/index.html">Docs</a><br />
    4103. 

  4103.     <ul style="margin-top: 5px;">
    4104. 

  4104.       <li>
    4105. 

  4105.         Added <a href="#Events-listenTo">listenTo</a>
    4106. 

  4106.         and <a href="#Events-stopListening">stopListening</a> to Events. They
    4107. 

  4107.         can be used as inversion-of-control flavors of <tt>on</tt> and <tt>off</tt>,
    4108. 

  4108.         for convenient unbinding of all events an object is currently listening to.
    4109. 

  4109.         <tt>view.remove()</tt> automatically calls <tt>view.stopListening()</tt>.
    4110. 

  4110.       </li>
    4111. 

  4111.       <li>
    4112. 

  4112.         When using <tt>add</tt> on a collection, passing <tt>{merge: true}</tt>
    4113. 

  4113.         will now cause duplicate models to have their attributes merged in to
    4114. 

  4114.         the existing models, instead of being ignored.
    4115. 

  4115.       </li>
    4116. 

  4116.       <li>
    4117. 

  4117.         Added <a href="#Collection-update">update</a> (which is also available as
    4118. 

  4118.         an option to <tt>fetch</tt>) for "smart" updating of sets of models.
    4119. 

  4119.       </li>
    4120. 

  4120.       <li>
    4121. 

  4121.         HTTP <tt>PATCH</tt> support in <a href="#Model-save">save</a> by passing
    4122. 

  4122.         <tt>{patch: true}</tt>.
    4123. 

  4123.       </li>
    4124. 

  4124.       <li>
    4125. 

  4125.         The <tt>Backbone</tt> object now extends <tt>Events</tt> so that you can
    4126. 

  4126.         use it as a global event bus, if you like.
    4127. 

  4127.       </li>
    4128. 

  4128.       <li>
    4129. 

  4129.         Added a <tt>"request"</tt> event to <a href="#Sync">Backbone.sync</a>,
    4130. 

  4130.         which triggers whenever a request begins to be made to the server.
    4131. 

  4131.         The natural complement to the <tt>"sync"</tt> event.
    4132. 

  4132.       </li>
    4133. 

  4133.       <li>
    4134. 

  4134.         Router URLs now support optional parts via parentheses, without having
    4135. 

  4135.         to use a regex.
    4136. 

  4136.       </li>
    4137. 

  4137.       <li>
    4138. 

  4138.         Backbone events now supports <tt>once</tt>, similar to Node's <tt>once</tt>,
    4139. 

  4139.         or jQuery's <tt>one</tt>.
    4140. 

  4140.       </li>
    4141. 

  4141.       <li>
    4142. 

  4142.         Backbone events now support jQuery-style event maps <tt>obj.on({click: action})</tt>.
    4143. 

  4143.       </li>
    4144. 

  4144.       <li>
    4145. 

  4145.         While listening to a <tt>reset</tt> event, the list of previous models
    4146. 

  4146.         is now available in <tt>options.previousModels</tt>, for convenience.
    4147. 

  4147.       </li>
    4148. 

  4148.       <li>
    4149. 

  4149.         <a href="#Model-validate">Validation</a> now occurs even during "silent"
    4150. 

  4150.         changes. This change means that the <tt>isValid</tt> method has
    4151. 

  4151.         been removed. Failed validations also trigger an error, even if an error
    4152. 

  4152.         callback is specified in the options.
    4153. 

  4153.       </li>
    4154. 

  4154.       <li>
    4155. 

  4155.         Consolidated <tt>"sync"</tt> and <tt>"error"</tt> events within
    4156. 

  4156.         <a href="#Sync">Backbone.sync</a>. They are now triggered regardless
    4157. 

  4157.         of the existence of <tt>success</tt> or <tt>error</tt> callbacks.
    4158. 

  4158.       </li>
    4159. 

  4159.       <li>
    4160. 

  4160.         For mixed-mode APIs, <tt>Backbone.sync</tt> now accepts
    4161. 

  4161.         <tt>emulateHTTP</tt> and <tt>emulateJSON</tt> as inline options.
    4162. 

  4162.       </li>
    4163. 

  4163.       <li>
    4164. 

  4164.         Collections now also proxy Underscore method name aliases (collect,
    4165. 

  4165.         inject, foldl, foldr, head, tail, take, and so on...)
    4166. 

  4166.       </li>
    4167. 

  4167.       <li>
    4168. 

  4168.         Removed <tt>getByCid</tt> from Collections. <tt>collection.get</tt> now
    4169. 

  4169.         supports lookup by both <tt>id</tt> and <tt>cid</tt>.
    4170. 

  4170.       </li>
    4171. 

  4171.       <li>
    4172. 

  4172.         After fetching a model or a collection, <i>all</i> defined <tt>parse</tt>
    4173. 

  4173.         functions will now be run. So fetching a collection and getting back new
    4174. 

  4174.         models could cause both the collection to parse the list, and then each model
    4175. 

  4175.         to be parsed in turn, if you have both functions defined.
    4176. 

  4176.       </li>
    4177. 

  4177.       <li>
    4178. 

  4178.         Bugfix for normalizing leading and trailing slashes in the Router
    4179. 

  4179.         definitions. Their presence (or absence) should not affect behavior.
    4180. 

  4180.       </li>
    4181. 

  4181.       <li>
    4182. 

  4182.         When declaring a View, <tt>options</tt>, <tt>el</tt>, <tt>tagName</tt>,
    4183. 

  4183.         <tt>id</tt> and <tt>className</tt> may now be defined as functions, if
    4184. 

  4184.         you want their values to be determined at runtime.
    4185. 

  4185.       </li>
    4186. 

  4186.       <li>
    4187. 

  4187.         Added a <tt>Backbone.ajax</tt> hook for more convenient overriding of
    4188. 

  4188.         the default use of <tt>$.ajax</tt>. If AJAX is too passé, set it to your
    4189. 

  4189.         preferred method for server communication.
    4190. 

  4190.       </li>
    4191. 

  4191.       <li>
    4192. 

  4192.         <tt>Collection#sort</tt> now triggers a <tt>sort</tt> event, instead
    4193. 

  4193.         of a <tt>reset</tt> event.
    4194. 

  4194.       </li>
    4195. 

  4195.       <li>
    4196. 

  4196.         Calling <tt>destroy</tt> on a Model will now return <tt>false</tt> if
    4197. 

  4197.         the model <tt>isNew</tt>.
    4198. 

  4198.       </li>
    4199. 

  4199.       <li>
    4200. 

  4200.         To set what library Backbone uses for DOM manipulation and Ajax calls,
    4201. 

  4201.         use <tt>Backbone.$ = ...</tt> instead of <tt>setDomLibrary</tt>.
    4202. 

  4202.       </li>
    4203. 

  4203.       <li>
    4204. 

  4204.         Removed the <tt>Backbone.wrapError</tt> helper method. Overriding
    4205. 

  4205.         <tt>sync</tt> should work better for those particular use cases.
    4206. 

  4206.       </li>
    4207. 

  4207.       <li>
    4208. 

  4208.         To improve the performance of <tt>add</tt>, <tt>options.index</tt>
    4209. 

  4209.         will no longer be set in the `add` event callback.
    4210. 

  4210.         <tt>collection.indexOf(model)</tt> can be used to retrieve the index
    4211. 

  4211.         of a model as necessary.
    4212. 

  4212.       </li>
    4213. 

  4213.       <li>
    4214. 

  4214.         For semantic and cross browser reasons, routes will now ignore search
    4215. 

  4215.         parameters.  Routes like <tt>search?query=…&amp;page=3</tt> should become
    4216. 

  4216.         <tt>search/…/3</tt>.
    4217. 

  4217.       </li>
    4218. 

  4218.       <li>
    4219. 

  4219.         <tt>Model#set</tt> no longer accepts another model as an argument.  This leads
    4220. 

  4220.         to subtle problems and is easily replaced with <tt>model.set(other.attributes)</tt>.
    4221. 

  4221.       </li>
    4222. 

  4222.     </ul>
    4223. 

  4223. 

  4224.     <b class="header">0.9.2</b> &mdash; <small><i>March 21, 2012</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.9.1...0.9.2">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.9.2/index.html">Docs</a><br />
    4225. 

  4225.     <ul style="margin-top: 5px;">
    4226. 

  4226.       <li>
    4227. 

  4227.         Instead of throwing an error when adding duplicate models to a collection,
    4228. 

  4228.         Backbone will now silently skip them instead.
    4229. 

  4229.       </li>
    4230. 

  4230.       <li>
    4231. 

  4231.         Added <a href="#Collection-push">push</a>,
    4232. 

  4232.         <a href="#Collection-pop">pop</a>,
    4233. 

  4233.         <a href="#Collection-unshift">unshift</a>, and
    4234. 

  4234.         <a href="#Collection-shift">shift</a> to collections.
    4235. 

  4235.       </li>
    4236. 

  4236.       <li>
    4237. 

  4237.         A model's <a href="#Model-changed">changed</a> hash is now exposed for
    4238. 

  4238.         easy reading of the changed attribute delta, since the model's last
    4239. 

  4239.         <tt>"change"</tt> event.
    4240. 

  4240.       </li>
    4241. 

  4241.       <li>
    4242. 

  4242.         Added <a href="#Collection-where">where</a> to collections for simple
    4243. 

  4243.         filtering.
    4244. 

  4244.       </li>
    4245. 

  4245.       <li>
    4246. 

  4246.         You can now use a single <a href="#Events-off">off</a> call
    4247. 

  4247.         to remove all callbacks bound to a specific object.
    4248. 

  4248.       </li>
    4249. 

  4249.       <li>
    4250. 

  4250.         Bug fixes for nested individual change events, some of which may be
    4251. 

  4251.         "silent".
    4252. 

  4252.       </li>
    4253. 

  4253.       <li>
    4254. 

  4254.         Bug fixes for URL encoding in <tt>location.hash</tt> fragments.
    4255. 

  4255.       </li>
    4256. 

  4256.       <li>
    4257. 

  4257.         Bug fix for client-side validation in advance of a <tt>save</tt> call
    4258. 

  4258.         with <tt>{wait: true}</tt>.
    4259. 

  4259.       </li>
    4260. 

  4260.       <li>
    4261. 

  4261.         Updated / refreshed the example
    4262. 

  4262.         <a href="examples/todos/index.html">Todo List</a> app.
    4263. 

  4263.       </li>
    4264. 

  4264.     </ul>
    4265. 

  4265. 

  4266.     <b class="header">0.9.1</b> &mdash; <small><i>Feb. 2, 2012</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.9.0...0.9.1">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.9.1/index.html">Docs</a><br />
    4267. 

  4267.     <ul style="margin-top: 5px;">
    4268. 

  4268.       <li>
    4269. 

  4269.         Reverted to 0.5.3-esque behavior for validating models. Silent changes
    4270. 

  4270.         no longer trigger validation (making it easier to work with forms).
    4271. 

  4271.         Added an <tt>isValid</tt> function that you can use to check if a model
    4272. 

  4272.         is currently in a valid state.
    4273. 

  4273.       </li>
    4274. 

  4274.       <li>
    4275. 

  4275.         If you have multiple versions of jQuery on the page, you can now tell
    4276. 

  4276.         Backbone which one to use with <tt>Backbone.setDomLibrary</tt>.
    4277. 

  4277.       </li>
    4278. 

  4278.       <li>
    4279. 

  4279.         Fixes regressions in <b>0.9.0</b> for routing with "root", saving with
    4280. 

  4280.         both "wait" and "validate", and the order of nested "change" events.
    4281. 

  4281.       </li>
    4282. 

  4282.     </ul>
    4283. 

  4283. 

  4284.     <b class="header">0.9.0</b> &mdash; <small><i>Jan. 30, 2012</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.5.3...0.9.0">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.9.0/index.html">Docs</a><br />
    4285. 

  4285.     <ul style="margin-top: 5px;">
    4286. 

  4286.       <li>
    4287. 

  4287.         Creating and destroying models with <tt>create</tt> and <tt>destroy</tt>
    4288. 

  4288.         are now optimistic by default. Pass <tt>{wait: true}</tt> as an option
    4289. 

  4289.         if you'd like them to wait for a successful server response to proceed.
    4290. 

  4290.       </li>
    4291. 

  4291.       <li>
    4292. 

  4292.         Two new properties on views: <tt>$el</tt> &mdash; a cached jQuery (or Zepto)
    4293. 

  4293.         reference to the view's element, and <tt>setElement</tt>, which should
    4294. 

  4294.         be used instead of manually setting a view's <tt>el</tt>. It will
    4295. 

  4295.         both set <tt>view.el</tt> and <tt>view.$el</tt> correctly, as well as
    4296. 

  4296.         re-delegating events on the new DOM element.
    4297. 

  4297.       </li>
    4298. 

  4298.       <li>
    4299. 

  4299.         You can now bind and trigger multiple spaced-delimited events at once.
    4300. 

  4300.         For example: <tt>model.on("change:name change:age", ...)</tt>
    4301. 

  4301.       </li>
    4302. 

  4302.       <li>
    4303. 

  4303.         When you don't know the key in advance, you may now call
    4304. 

  4304.         <tt>model.set(key, value)</tt> as well as <tt>save</tt>.
    4305. 

  4305.       </li>
    4306. 

  4306.       <li>
    4307. 

  4307.         Multiple models with the same <tt>id</tt> are no longer allowed in a
    4308. 

  4308.         single collection.
    4309. 

  4309.       </li>
    4310. 

  4310.       <li>
    4311. 

  4311.         Added a <tt>"sync"</tt> event, which triggers whenever a model's state
    4312. 

  4312.         has been successfully synced with the server (create, save, destroy).
    4313. 

  4313.       </li>
    4314. 

  4314.       <li>
    4315. 

  4315.         <tt>bind</tt> and <tt>unbind</tt> have been renamed to <tt>on</tt>
    4316. 

  4316.         and <tt>off</tt> for clarity, following jQuery's lead.
    4317. 

  4317.         The old names are also still supported.
    4318. 

  4318.       </li>
    4319. 

  4319.       <li>
    4320. 

  4320.         A Backbone collection's <tt>comparator</tt> function may now behave
    4321. 

  4321.         either like a <a href="http://underscorejs.org/#sortBy">sortBy</a>
    4322. 

  4322.         (pass a function that takes a single argument),
    4323. 

  4323.         or like a <a href="https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Array/sort">sort</a>
    4324. 

  4324.         (pass a comparator function that expects two arguments). The comparator
    4325. 

  4325.         function is also now bound by default to the collection &mdash; so you
    4326. 

  4326.         can refer to <tt>this</tt> within it.
    4327. 

  4327.       </li>
    4328. 

  4328.       <li>
    4329. 

  4329.         A view's <tt>events</tt> hash may now also contain direct function
    4330. 

  4330.         values as well as the string names of existing view methods.
    4331. 

  4331.       </li>
    4332. 

  4332.       <li>
    4333. 

  4333.         Validation has gotten an overhaul &mdash; a model's <tt>validate</tt> function
    4334. 

  4334.         will now be run even for silent changes, and you can no longer create
    4335. 

  4335.         a model in an initially invalid state.
    4336. 

  4336.       </li>
    4337. 

  4337.       <li>
    4338. 

  4338.         Added <tt>shuffle</tt> and <tt>initial</tt> to collections, proxied
    4339. 

  4339.         from Underscore.
    4340. 

  4340.       </li>
    4341. 

  4341.       <li>
    4342. 

  4342.         <tt>Model#urlRoot</tt> may now be defined as a function as well as a
    4343. 

  4343.         value.
    4344. 

  4344.       </li>
    4345. 

  4345.       <li>
    4346. 

  4346.         <tt>View#attributes</tt> may now be defined as a function as well as a
    4347. 

  4347.         value.
    4348. 

  4348.       </li>
    4349. 

  4349.       <li>
    4350. 

  4350.         Calling <tt>fetch</tt> on a collection will now cause all fetched JSON
    4351. 

  4351.         to be run through the collection's model's <tt>parse</tt> function, if
    4352. 

  4352.         one is defined.
    4353. 

  4353.       </li>
    4354. 

  4354.       <li>
    4355. 

  4355.         You may now tell a router to <tt>navigate(fragment, {replace: true})</tt>,
    4356. 

  4356.         which will either use <tt>history.replaceState</tt> or
    4357. 

  4357.         <tt>location.hash.replace</tt>, in order to change the URL without adding
    4358. 

  4358.         a history entry.
    4359. 

  4359.       </li>
    4360. 

  4360.       <li>
    4361. 

  4361.         Within a collection's <tt>add</tt> and <tt>remove</tt> events, the index
    4362. 

  4362.         of the model being added or removed is now available as <tt>options.index</tt>.
    4363. 

  4363.       </li>
    4364. 

  4364.       <li>
    4365. 

  4365.         Added an <tt>undelegateEvents</tt> to views, allowing you to manually
    4366. 

  4366.         remove all configured event delegations.
    4367. 

  4367.       </li>
    4368. 

  4368.       <li>
    4369. 

  4369.         Although you shouldn't be writing your routes with them in any case &mdash;
    4370. 

  4370.         leading slashes (<tt>/</tt>) are now stripped from routes.
    4371. 

  4371.       </li>
    4372. 

  4372.       <li>
    4373. 

  4373.         Calling <tt>clone</tt> on a model now only passes the attributes
    4374. 

  4374.         for duplication, not a reference to the model itself.
    4375. 

  4375.       </li>
    4376. 

  4376.       <li>
    4377. 

  4377.         Calling <tt>clear</tt> on a model now removes the <tt>id</tt> attribute.
    4378. 

  4378.       </li>
    4379. 

  4379.     </ul>
    4380. 

  4380. 

  4381.     <p>
    4382. 

  4382.       <b class="header">0.5.3</b> &mdash; <small><i>August 9, 2011</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.5.2...0.5.3">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.5.3/index.html">Docs</a><br />
    4383. 

  4383.       A View's <tt>events</tt> property may now be defined as a function, as well
    4384. 

  4384.       as an object literal, making it easier to programmatically define and inherit
    4385. 

  4385.       events. <tt>groupBy</tt> is now proxied from Underscore as a method on Collections.
    4386. 

  4386.       If the server has already rendered everything on page load, pass
    4387. 

  4387.       <tt>Backbone.history.start({silent: true})</tt> to prevent the initial route
    4388. 

  4388.       from triggering. Bugfix for pushState with encoded URLs.
    4389. 

  4389.     </p>
    4390. 

  4390. 

  4391.     <p>
    4392. 

  4392.       <b class="header">0.5.2</b> &mdash; <small><i>July 26, 2011</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.5.1...0.5.2">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.5.2/index.html">Docs</a><br />
    4393. 

  4393.       The <tt>bind</tt> function, can now take an optional third argument, to specify
    4394. 

  4394.       the <tt>this</tt> of the callback function.
    4395. 

  4395.       Multiple models with the same <tt>id</tt> are now allowed in a collection.
    4396. 

  4396.       Fixed a bug where calling <tt>.fetch(jQueryOptions)</tt> could cause an
    4397. 

  4397.       incorrect URL to be serialized.
    4398. 

  4398.       Fixed a brief extra route fire before redirect, when degrading from
    4399. 

  4399.       <tt>pushState</tt>.
    4400. 

  4400.     </p>
    4401. 

  4401. 

  4402.     <p>
    4403. 

  4403.       <b class="header">0.5.1</b> &mdash; <small><i>July 5, 2011</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.5.0...0.5.1">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.5.1/index.html">Docs</a><br />
    4404. 

  4404.       Cleanups from the 0.5.0 release, to wit: improved transparent upgrades from
    4405. 

  4405.       hash-based URLs to pushState, and vice-versa. Fixed inconsistency with
    4406. 

  4406.       non-modified attributes being passed to <tt>Model#initialize</tt>. Reverted
    4407. 

  4407.       a <b>0.5.0</b> change that would strip leading hashbangs from routes.
    4408. 

  4408.       Added <tt>contains</tt> as an alias for <tt>includes</tt>.
    4409. 

  4409.     </p>
    4410. 

  4410. 

  4411.     <p>
    4412. 

  4412.       <b class="header">0.5.0</b> &mdash; <small><i>July 1, 2011</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.3.3...0.5.0">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.5.0/index.html">Docs</a><br />
    4413. 

  4413.       A large number of tiny tweaks and micro bugfixes, best viewed by looking
    4414. 

  4414.       at <a href="https://github.com/jashkenas/backbone/compare/0.3.3...0.5.0">the commit diff</a>.
    4415. 

  4415.       HTML5 <tt>pushState</tt> support, enabled by opting-in with:
    4416. 

  4416.       <tt>Backbone.history.start({pushState: true})</tt>.
    4417. 

  4417.       <tt>Controller</tt> was renamed to <tt>Router</tt>, for clarity.
    4418. 

  4418.       <tt>Collection#refresh</tt> was renamed to <tt>Collection#reset</tt> to emphasize
    4419. 

  4419.       its ability to both reset the collection with new models, as well as empty
    4420. 

  4420.       out the collection when used with no parameters.
    4421. 

  4421.       <tt>saveLocation</tt> was replaced with <tt>navigate</tt>.
    4422. 

  4422.       RESTful persistence methods (save, fetch, etc.) now return the jQuery deferred
    4423. 

  4423.       object for further success/error chaining and general convenience.
    4424. 

  4424.       Improved XSS escaping for <tt>Model#escape</tt>.
    4425. 

  4425.       Added a <tt>urlRoot</tt> option to allow specifying RESTful urls without
    4426. 

  4426.       the use of a collection.
    4427. 

  4427.       An error is thrown if <tt>Backbone.history.start</tt> is called multiple times.
    4428. 

  4428.       <tt>Collection#create</tt> now validates before initializing the new model.
    4429. 

  4429.       <tt>view.el</tt> can now be a jQuery string lookup.
    4430. 

  4430.       Backbone Views can now also take an <tt>attributes</tt> parameter.
    4431. 

  4431.       <tt>Model#defaults</tt> can now be a function as well as a literal attributes
    4432. 

  4432.       object.
    4433. 

  4433.     </p>
    4434. 

  4434. 

  4435.     <p>
    4436. 

  4436.       <b class="header">0.3.3</b> &mdash; <small><i>Dec 1, 2010</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.3.2...0.3.3">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.3.3/index.html">Docs</a><br />
    4437. 

  4437.       Backbone.js now supports <a href="http://zeptojs.com">Zepto</a>, alongside
    4438. 

  4438.       jQuery, as a framework for DOM manipulation and Ajax support.
    4439. 

  4439.       Implemented <a href="#Model-escape">Model#escape</a>, to efficiently handle
    4440. 

  4440.       attributes intended for HTML interpolation. When trying to persist a model,
    4441. 

  4441.       failed requests will now trigger an <tt>"error"</tt> event. The
    4442. 

  4442.       ubiquitous <tt>options</tt> argument is now passed as the final argument
    4443. 

  4443.       to all <tt>"change"</tt> events.
    4444. 

  4444.     </p>
    4445. 

  4445. 

  4446.     <p>
    4447. 

  4447.       <b class="header">0.3.2</b> &mdash; <small><i>Nov 23, 2010</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.3.1...0.3.2">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.3.2/index.html">Docs</a><br />
    4448. 

  4448.       Bugfix for IE7 + iframe-based "hashchange" events. <tt>sync</tt> may now be
    4449. 

  4449.       overridden on a per-model, or per-collection basis. Fixed recursion error
    4450. 

  4450.       when calling <tt>save</tt> with no changed attributes, within a
    4451. 

  4451.       <tt>"change"</tt> event.
    4452. 

  4452.     </p>
    4453. 

  4453. 

  4454.     <p>
    4455. 

  4455.       <b class="header">0.3.1</b> &mdash; <small><i>Nov 15, 2010</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.3.0...0.3.1">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.3.1/index.html">Docs</a><br />
    4456. 

  4456.       All <tt>"add"</tt> and <tt>"remove"</tt> events are now sent through the
    4457. 

  4457.       model, so that views can listen for them without having to know about the
    4458. 

  4458.       collection. Added a <tt>remove</tt> method to <a href="#View">Backbone.View</a>.
    4459. 

  4459.       <tt>toJSON</tt> is no longer called at all for <tt>'read'</tt> and <tt>'delete'</tt> requests.
    4460. 

  4460.       Backbone routes are now able to load empty URL fragments.
    4461. 

  4461.     </p>
    4462. 

  4462. 

  4463.     <p>
    4464. 

  4464.       <b class="header">0.3.0</b> &mdash; <small><i>Nov 9, 2010</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.2.0...0.3.0">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.3.0/index.html">Docs</a><br />
    4465. 

  4465.       Backbone now has <a href="#Controller">Controllers</a> and
    4466. 

  4466.       <a href="#History">History</a>, for doing client-side routing based on
    4467. 

  4467.       URL fragments.
    4468. 

  4468.       Added <tt>emulateHTTP</tt> to provide support for legacy servers that don't
    4469. 

  4469.       do <tt>PUT</tt> and <tt>DELETE</tt>.
    4470. 

  4470.       Added <tt>emulateJSON</tt> for servers that can't accept <tt>application/json</tt>
    4471. 

  4471.       encoded requests.
    4472. 

  4472.       Added <a href="#Model-clear">Model#clear</a>, which removes all attributes
    4473. 

  4473.       from a model.
    4474. 

  4474.       All Backbone classes may now be seamlessly inherited by CoffeeScript classes.
    4475. 

  4475.     </p>
    4476. 

  4476. 

  4477.     <p>
    4478. 

  4478.       <b class="header">0.2.0</b> &mdash; <small><i>Oct 25, 2010</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.1.2...0.2.0">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.2.0/index.html">Docs</a><br />
    4479. 

  4479.       Instead of requiring server responses to be namespaced under a <tt>model</tt>
    4480. 

  4480.       key, now you can define your own <a href="#Model-parse">parse</a> method
    4481. 

  4481.       to convert responses into attributes for Models and Collections.
    4482. 

  4482.       The old <tt>handleEvents</tt> function is now named
    4483. 

  4483.       <a href="#View-delegateEvents">delegateEvents</a>, and is automatically
    4484. 

  4484.       called as part of the View's constructor.
    4485. 

  4485.       Added a <a href="#Collection-toJSON">toJSON</a> function to Collections.
    4486. 

  4486.       Added <a href="#Collection-chain">Underscore's chain</a> to Collections.
    4487. 

  4487.     </p>
    4488. 

  4488. 

  4489.     <p>
    4490. 

  4490.       <b class="header">0.1.2</b> &mdash; <small><i>Oct 19, 2010</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.1.1...0.1.2">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.1.2/index.html">Docs</a><br />
    4491. 

  4491.       Added a <a href="#Model-fetch">Model#fetch</a> method for refreshing the
    4492. 

  4492.       attributes of single model from the server.
    4493. 

  4493.       An <tt>error</tt> callback may now be passed to <tt>set</tt> and <tt>save</tt>
    4494. 

  4494.       as an option, which will be invoked if validation fails, overriding the
    4495. 

  4495.       <tt>"error"</tt> event.
    4496. 

  4496.       You can now tell backbone to use the <tt>_method</tt> hack instead of HTTP
    4497. 

  4497.       methods by setting <tt>Backbone.emulateHTTP = true</tt>.
    4498. 

  4498.       Existing Model and Collection data is no longer sent up unnecessarily with
    4499. 

  4499.       <tt>GET</tt> and <tt>DELETE</tt> requests. Added a <tt>rake lint</tt> task.
    4500. 

  4500.       Backbone is now published as an <a href="http://npmjs.org">NPM</a> module.
    4501. 

  4501.     </p>
    4502. 

  4502. 

  4503.     <p>
    4504. 

  4504.       <b class="header">0.1.1</b> &mdash; <small><i>Oct 14, 2010</i></small> &mdash; <a href="https://github.com/jashkenas/backbone/compare/0.1.0...0.1.1">Diff</a> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.1.1/index.html">Docs</a><br />
    4505. 

  4505.       Added a convention for <tt>initialize</tt> functions to be called
    4506. 

  4506.       upon instance construction, if defined. Documentation tweaks.
    4507. 

  4507.     </p>
    4508. 

  4508. 

  4509.     <p>
    4510. 

  4510.       <b class="header">0.1.0</b> &mdash; <small><i>Oct 13, 2010</i></small> &mdash; <a href="http://htmlpreview.github.com/?https://raw.github.com/jashkenas/backbone/0.1.0/index.html">Docs</a><br />
    4511. 

  4511.       Initial Backbone release.
    4512. 

  4512.     </p>
    4513. 

  4513. 

  4514.     <p>
    4515. 

  4515.       <br />
    4516. 

  4516.       <a href="http://documentcloud.org/" title="A DocumentCloud Project" style="background:none;">
    4517. 

  4517.         <img src="http://jashkenas.s3.amazonaws.com/images/a_documentcloud_project.png" alt="A DocumentCloud Project" style="position:relative;left:-10px;" />
    4518. 

  4518.       </a>
    4519. 

  4519.     </p>
    4520. 

  4520. 

  4521.   </div>
    4522. 

  4522. 

  4523.   <script src="test/vendor/underscore.js"></script>
    4524. 

  4524.   <script src="test/vendor/jquery.js"></script>
    4525. 

  4525.   <script src="docs/js/jquery.lazyload.js"></script>
    4526. 

  4526.   <script src="test/vendor/json2.js"></script>
    4527. 

  4527.   <script src="backbone.js"></script>
    4528. 

  4528. 

  4529.   <script>
    4530. 

  4530.     // Set up the "play" buttons for each runnable code example.
    4531. 

  4531.     $(function() {
    4532. 

  4532.       $('.runnable').each(function() {
    4533. 

  4533.         var code = this;
    4534. 

  4534.         var button = '<div class="run" title="Run"></div>';
    4535. 

  4535.         $(button).insertBefore(code).bind('click', function(){
    4536. 

  4536.           eval($(code).text());
    4537. 

  4537.         });
    4538. 

  4538.       });
    4539. 

  4539.       $('[data-original]').lazyload();
    4540. 

  4540.     });
    4541. 

  4541.   </script>
    4542. 

  4542. 

  4543. </body>
    4544. 

  4544. </html>
    4545. 

  4545.