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.
We’ve all heard of Templating, heck I’ve written about templating. Templating is a great way to write HTML that is designed to be manipulated and inserted into a document via JavaScript, but it has a very annoying caveat: it’s a huge pain to make templates external. They pretty much have to be inline, which doesn’t allow you to maintain them separately. That’s all about to change.
As JavaScript moves further and further away from the playground programming language that it used to be, and is used more and more as the core for large-scale applications, managing the code starts to become extremely difficult. Splitting the code into multiple files helps with that, though it also adds more complexity in a different way. One way to fight this new complexity is with dependency management libraries, but which one is right for you?
It’s taken too long, but it’s finally completed. The project page for JZ Parse URL is up with full documentation. You can also find it listed on the projects page. Along with this new project comes a few minor changes to the way the project pages are done: files will no longer be directly downloadable from the site, but instead everything is done on GitHub. Also, I’ve decided to make the documentation in the JavaScript files more minimal and instead just link to the project pages. This update will happen soon and will not bring a new version number.
Everyone has their own style when coding. For some people, the style they use might be so inconsistent that it looks like they used a program to randomize the code layout so it would confuse everyone as much as possible. In general it’s best to use a consistent coding style, for your own sake, and for the sake of everyone else who might look at your code. To keep things consistent you can use a style guide, which will help you remember and use your rules.