Finally! We’ve made it to the end of the Backbone.js Application Walkthrough video tutorial series. In this final video, we make few small adjustments for the sake of organization and a bunch of other changes that convert the application to work using RequireJS. Almost every file gets touched in this video, but each only receives minor changes in order to create an overall major change in modularity and optimization.
We’ve made it to part 4 of this Backbone application walkthrough series. This time we finally get the app to do something worthwhile… like work! The application finally lives as we implement the router and hit the “GO” button. Check out the power of the router and don’t forget that just because it’s running, does not mean we’re done. The next and final video in this series converts the application to work with AMD and RequireJS.
Moving on to part 3 of the Backbone Application Walkthrough video series, we work on moving all of the templates to external files to reduce the dependency on the templates being included in the index.html file and so that they might become available if we use these views on different pages. Also, I added an extra view that wasn’t in the original application because, as you’ll see in the video, it makes things a little nicer.
I suspect quite a few of those starting with Node are interested in using it for web development. Of the web frameworks available for Node, Express is leading the pack. And version 3 is in beta. I’m just getting started with Node and Express, so I thought I’d help you all get up and running that much more quickly. I won’t get into the boring details of installing Node and NPM. That part is especially easy now that they have Windows and Mac installers available on the Node website.
We’re moving right along in our video series of tutorials walking you through the process of writing a Backbone.js application. Today we cover the views and embedded templates. There are a number of views here, all pulling from the same models and collections of wine. You’ll see each view, what it’s for, and how it works its magic. Click on through for this long look at Backbone.js views and templates.
After spending 3 nights in a row creating one simple screencast (1 the recording failed, 2 the video was fine but the audio was quiet, 3 the audio was fixed), I didn’t feel like messing with videos another night. So, this time we’re going to do something a little different. Normally I (and now a few other contributors) write about whatever suits our fancy. This time, you – the audience and reason for the existence of this blog – all decide.
The day everyone has long been waiting for has finally arrived. I’ve just started the first part of a series of posts walking through how to build an actual application using the Backbone.js JavaScript MVC framework. With this first piece of the puzzle I cover the structure of the application and get you started with some HTML plus the model and collection JavaScript code. Let’s take a look!
Does anyone know any good FREE screencast recording software? I’ve been using Camstudio for a while and with my first 5 tutorials it seemed great. Now it randomly decides to hate me and flash black screens in the middle of recording. I’ve finally gotten to the point of starting the Backbone App video tutorial series but I can’t get the recording to work right, so it’s delayed until I can find something that works. If I can’t find something within 24 hours, you’ll receive written tutorial for something else instead until I can find a solution.
Keeping a blog maintained solo, while creating useful projects and making updates to the design of the site, can be quite the stressful for a husband and father. I’m having a hard time keeping up the pace. I started this blog because I love JavaScript and I wanted to help other JavaScripters keep up with the times and learn, but now I need some help fulfilling that dream. If you know anything about JavaScript and can write relatively well, I’d like to hear from you.
We’ve all heard time and time again that when you’re trying to determine the JavaScript capabilities of a browser you should avoid user agent string parsing like a horrible plague and instead put your trust in a little thing called feature detection. But why should we? What’s so bad about relying on user agent strings? Also, how do I even use feature detection anyway? Read on and you’ll find the answer to all of these questions.