Gaslight Software Blog, Backbone.js Views Done the Right Way. As soon as you build an interesting application in backbone, one of the challenges you are likely to encounter is wanting to have composite views, or views that are contained within a larger view.
I’ve solved this problem several ways in different projects and I thought it would be fun to walk through the progression and how I’ve arrived at what I currently see as a preferred solution. Let’s start by talking about what might seem to be the most obvious solution and why it doesn’t actually work. We’ll use as an example a view that displays a collection of people. Let’s assume we’d like to have a view for the table and within it, views for each row. You might end up with a TableView like so: 004 JSJ Backbone.js with Jeremy Ashkenas. Podcast: Play in new window | Download (Duration: 54:33 — 74.9MB) Panel Discussion IRC log of Jeremy and Yehuda’s chatIce libraryDocument CloudBackbone.jsCoffeeScriptDropshareclient-side MVCserver persistingjQueryIs backbone really MVC?
Backbone CollectionsEmberConvention over ConfigurationHandlebarsjQuery is an opinionated libraryMustacheDOM only approachTemplates in other languagesBenefits of templates on the serverConsistency/bindingCore patternsjQuery deferredsWhen to add features to your libraryBackbone.ModelBindingBackbone.MarionetteRESTAdding onto BackboneAdding hooks Picks Transcript. Sample App with Backbone.js and Twitter Bootstrap. Backbone.js is a lightweight JavaScript framework that provides the basic infrastructure (Model, Collection, View, and Router classes) to bring structure to your Web applications.
Twitter Bootstrap is a UI toolkit that provides simple and flexible HTML, CSS, and Javascript to implement popular user interface components and interactions. In other words, Backbone.js and Twitter Bootstrap focus on different areas of your application: core architecture and user interface respectively. Sample App with Backbone.js and Twitter Bootstrap.
Backbone: Dealing with stateful applications. Backbone.js by Example. Developing Backbone.js Applications - By Addy Osmani (@addyosmani) Available free for open-source reading below or for purchase via the O'Reilly store.
Pull requests and comments always welcome. Prelude Not so long ago, “data-rich web application” was an oxymoron. Today, these applications are everywhere and you need to know how to build them. Traditionally, web applications left the heavy-lifting of data to servers that pushed HTML to the browser in complete page loads. Think of the Ajax shopping cart which doesn’t require a refresh on the page when adding an item to your basket. The rise of arbitrary code on the client-side which can talk to the server however it sees fit has meant an increase in client-side complexity. Thankfully, there are a growing number of JavaScript libraries that can help improve the structure and maintainability of your code, making it easier to build ambitious interfaces without a great deal of effort. Target Audience Acknowledgements Credits Target Version Reading.
Testing Backbone.js Best Practices. BackboneFU, Resources for the Backbone.js developerBackboneFU, Resources for the Backbone.js developer. Before using backbone when working with a list of html nodes I always made it my duty to append them only in one big chunk of text.
Manipulating the dom is slow, it triggers a reflow of the page, this is costly even on small lists, specially on mobile. So being not sure what to do with backbone I decided to append each view directly in my container like this. Of course this solution made me grind my teets, I did not want to append each view individually. document.createDocumentFragment() Fortunately, there is another solution than parsing the views as a string and then merging them together.
The cool thing about document fragments is that until it is added to the page it does not trigger a browser reflow, which is the really expensive thing here. Update. Backbone.js Training - A Multi-Day, Hands-On, Training Class. Notice Of Course Discontinuation Please note that as of January 2013 I am no longer offering my Backbone training class on a regular basis.
I have exited the consulting world in favor of a full time position working with Kendo UI as a Developer Advocate. While I will continue to be a part of the Backbone community with my new position, offering a private, on-site training class is not something I will be able to do right now. I may bring this back out at some point in the future, but I don't know when (if at all). Organizing Your Backbonejs Application With Modules. If you have spent any time looking at Backbone.js, like many others, you are probably amazed by how lightweight, flexible and elegant it is.
Backbone.js is incredibly powerful, but not prescriptive in how it should be used. With great power comes great responsibility, and if you’ve tried to use Backbone.js for a large project you might be asking yourself: how do I organize my code? When thinking about “code organization” the questions you might be asking are: How do I declare and invoke Backbone types? How do I manage a separation of concerns? All good questions! There’s been a lot of debate about this issue in the Backbone.js community for several reasons. Having said all this, let’s dive into some of the details. Here’s how you might layout your application structure: Static Assets Your static assets such as CSS, images and JavaScript libraries required by your code should go under a parent directory, such as the assets directory in our example above.
Application code. Backbone.js Tutorials. Thomasdavis/backbonetutorials - GitHub. Addyosmani/backbone-fundamentals - GitHub.