Part 4: Backbone.js Collections Video Tutorial is here now. We’ve already discussed models, views, and routers in Backbone.js so far, but now we’re on to collections. Collections are pretty much exactly what their name implies: collections of models. Many times, data is displayed in lists, not just singular items. This is where collections come in - to keep every model in order and synchronized with the database on the back end.
Due to scheduling conflicts and inaccessibility to proper equipment, no post will be released today. Instead Part 3 of the Backbone.js Video series will be released on Tuesday, April 10th. If you missed any of the series thus far, I recommend catching up before the new one comes out, by using the links below.
Last week you saw a video tutorial on using Models in Backbone.js. This week we’ve moved right along to part 2: learning about Views in Backbone.js. As usual, Backbone.js has made things super simple, yet you get a lot for how little code you write. You’ll see how to attach events (super easy) and utilize models (also super easy) to give your views some data to work with.
It’s been a little while since I’ve taken a look at JZ Publish/Subscribe, but recently I had a great idea to fix a problem I was having trouble solving. Mix that in with a few more bits of context capability and you have the version 1.3 release of JZ Publish/Subscribe. Go ahead and read a little more to get the scoop on this great idea and how it will make using JZ Publish/Subscribe more stable.
jQuery UI is one of the cooler things to come out with jQuery. It allows you to easily install widgets and simple capabilities onto your site quickly and easily. ThemeRoller makes it even more fun by allowing you to style the widgets in nearly limitless ways. There is one place where jQuery UI is lacking though: the number of widgets it provides. This is where Wijmo comes in.
jQuery plugins are popping up all over the place and just about everyone is trying to get in on the action. What determines whether a plugin is good or bad for you is largely up to your opinion and your requirements, but there are few things that you can do when writing your plugins to guarantee at least a bit of quality and standardization in your plugins that everyone who looks at your plugin code will be thankful for.