Resumen Backbone.js en Ingles
•
1 like•471 views
Backbone.js is a lightweight JavaScript framework that provides structure to web applications through models, collections, views, and a RESTful JSON interface. It allows separation of data from presentation through models that handle data synchronization with a backend server, while views listen to model changes and update the HTML. Backbone.js gives structure to applications in an MVC pattern through core classes like Model, Collection, View, and Controller. It is well-suited for creating front-end heavy, data-driven applications.
Convert to study materialsBETA
Transform any presentation into ready-made study material—select from outputs like summaries, definitions, and practice questions.
![Model
Models can mean different things in different implementations of MVC. In Backbone, a model
represents a singular entity a record in a database if you will. But there are no hard and fast
rules here.
Models are the heart of any JavaScript application, containing the interactive data as well as a
large part of the logic surrounding it: conversions, validations, computed properties, and access
control.
Example
var Game = Backbone.Model.extend({});
var Game = Backbone.Model.extend({
initialize: function(){
alert("Oh hey! ");
},
defaults: {
name: 'Default title',
releaseDate: 2011,
}
});
Collection
Collections in Backbone are essentially just a collection of models. Going with our database
analogy from earlier, collections are the results of a query where the results consists of a
number of records [models]. You can define a collection like so:
var GamesCollection = Backbone.Collection.extend({
model : Game,
}
});
View
A view handles two duties fundamentally:
● Listen to events thrown by the DOM and models/collections.
● Represent the application's state and data model to the user.
Documento creado por Francisco Quintero](https://image.slidesharecdn.com/backbone-140725214657-phpapp01/85/Resumen-Backbone-js-en-Ingles-4-320.jpg)
Resumen Backbone.js en Ingles
- 1. Backbone.js Tomado de Stack Overflow y Tuts Backbone.js gives structure to web applications by providing models with keyvalue binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing API over a RESTful JSON interface. Backbone is a super lightweight library that lets you create easy to maintain front ends. It's backend agnostic and works well with any of the modern JavaScript libraries you're already using. Key-value binding and custom events When a model's contents or state is changed, other objects that have subscribed to the model are notified so they can proceed accordingly. Here, the views listen to changes in the model, and update themselves accordingly instead of the model having to deal with the views manually. Rich API of enumerable functions Backbone ships with a number of very useful functions for handling and working with your data. Unlike other implementation, arrays in JavaScript are pretty neutered, which really is a hampering problem when you have to deal with data. Views with declarative event handling Your days of writing spaghetti bind calls are over. You can programmatically declare which callback needs to be associated with specific elements. RESTful JSON interface Even though the default method is to use a standard AJAX call when you want to talk to the server, you can easily switch it out to anything you need. A number of adapters have sprung up covering most of the favorites including Websockets and local storage. Backbone provides a clean way to surgically separate your data from your presentation. The model that works with the data is only concerned with synchronizing with a server while the view's primary duty is listening to changes to the subscribed model and rendering the HTML. Does it replace jQuery? No. They're pretty complementary in their scopes with almost no overlaps in functionality. Backbone handles all the higher level abstractions, while jQuery or similar libraries work with the DOM, normalize events and so on. Documento creado por Francisco Quintero
- 2. Their scopes and use cases are pretty different and because you know one doesn't mean that you shouldn't learn the other. As a JavaScript developer, you should know how to effectively work with both. Where should I be using this? Backbone is ideally suited for creating front end heavy, data driven applications. Think the GMail interface, new Twitter or any other revelation of the past few years. It makes creating complex apps easier. While you can shoehorn it for more mainstream web pages, this is really a library that is tailored for web apps. I can still use other libraries on the page, right? Absolutely. Not only your typical DOM accessing, AJAX wrapping kind, but also the rest of your templating and script loading kind. It's very, very loosely coupled, which means you can use almost all of your tools in conjunction with Backbone. Answers from Stack Overflow 1. Backbone.js is basically an uberlight framework that allows you to structure your Javascript code in an MVC(Model, View, Controller) fashion where... Model is part of your code that retrieves and populates the data, View is the HTML representation of this model(views change as models change, etc) and Controller that in this case allows you to save the state of your javascript application via a hashbang url, for example: http://twitter.com/#search?q=backbone.js Some pros that I discovered with Backbone: ● No more Javascript Spaghetti: code is organized and broken down into semantically meaningful .js files which are later combined using JAMMIT ● No more jQuery.data(bla, bla): no need to store data in DOM, store data in models instead ● event binding just works ● extremely useful underscore utility library ● backbone.js code is well documented and a great read. opened my eyes to a number of JS code techniques. Cons: Documento creado por Francisco Quintero