Why move away from Backbone and into React and Angular2?

Dear Backbone, it's not you...it's us. We still love you. by Cloudoki team The environment Here at Cloudoki we take pride in trying to work with as many technologies and frameworks possible. So much that we even have that guy, that usually gets all the tricky projects (shout out to Delio, the Hero). All fun and games, really. Despite having a curious and naturally dynamic team, we still rely on some good "old" reliable pieces of code and frameworks to get some things going, like Backbone. Let me just stop here and say something. It's not that Backbone is »

Grow your Backbone App without going insane

Backbone's philosophy consists in finding the balance between giving structure to your data and remaining a flexible tool. That is what makes Backbone great, but in order to grow your application you will need to lay down the law and start stacking bricks. Decoupling your application When looking at a larger program in its entirety, individual functions start to blend into the background. Such a program can be made more readable if we have a larger unit of organization. Modules divide programs into clusters of code that, by some criterion, belong together. Eloquent Javascript The Module Pattern is a great »

Extending backbone's requests with custom headers

We have all but love for backbone around here. But although it's pretty flexible and complete, sometimes you just need that something that doesn't quite work the way you need, like adding custom headers to every single request. You could be tempted to add a sync function on every model and collection and add your custom headers there, but besides multiplying your code many times, if your project is going on for more than a few weeks you might have some serious copy pasting to do. There is a simpler, easier and prettier way of adding for example, a bearer »

Backbone App - End to End: Connecting to an external API

This article is the third article in the Backbone App - End to End series. In the previous article we created a basic design pattern to structure your backbone app. In this article we shall hook our previous work with a live external API that contains movie data, and we will hook it up with our search page. Right now you should have: Movie Model: MovieApp.Models.Movies = Backbone.Model.extend({ initialize: function(options) {}, }); Movie Collection: var Movies = Backbone.Collection.extend({ initialize: function(options) {} }); Movie, home and search page Views: MovieApp.Views.MovieView = Backbone.View.extend({ initialize: function(options) {} }); MovieApp. »

Backbone App - End to End: Basic design pattern

In this article we apply the Model, Collection and View logic from the previous article on Backbone.js basics to an actual useable design pattern. It's a rather simple one but versatile enough to implement a SPA that connects to the IMDB's external API. From the previous article, one thing that jumps into mind is that if we keep adding logic to the index.html file, before we get anything remotely decent going on, we will have hundreds of lines of code straight, with no organization whatsoever. Sounds like a legacy nightmare. We shall fix that. Create the folder structure »