This week's widget is a real-time chat application that demonstrates sending and receiving messages using Socket.IO and can.Model. This article shows how to integrate Socket.IO to can.Model's events system.

This week's widget demonstrates the awesome power of jQuery++'s range helper. Text ranges are notoriously a pain in the butt, with major differences in API and implementation across browsers. Similar to jQuery with DOM elements, $.Range provides a simpler API and cross browser methods to create, move, and compare text ranges. If you need to create a custom text editor, text highlighter, or other functionality that understands text, $.Range can be a huge help. For example:

This weekly widget was suggested by @Cherif_b. The article covers how to create a basic paginated grid. But even more important, it gives a glipse at how we organize large applications.

I, @justinbmeyer, am going to post a weekly widget made with CanJS. I hope to continue this for as long as I have widgets to write. If you want to see something, please tweet it to @canjs. These posts are going to be quick and dirty. Eventually, I will put these up on CanJS's recipe page with a full description.

Hello, my name is jQuery++. It's wonderful to meet you. Have you ever found yourself wishing jQuery had just one more feature or wanted it to be a tiny bit faster? I know I have, but I understand jQuery can't do everything. This is why the team at Bitovi created me, a collection of extremely useful DOM helpers and special events that complement jQuery.

This article is the second of a two part series (part1) on CanJS's hashchange routing system - can.route. This part walks through through can.route's advanced functionality. Specifically, it covers:

This article is the first of a two part series on CanJS's hashchange routing system - can.route. This part walks through the basics of hashchange routing and how can.route can be used for basic patterns. Specifically, it covers:

If you turn on a profiler in most of the apps we've built and click around like a user, after a while you'll notice jQuery.event.fix is often taking the most time (in the video below, it takes 6.34% of the total time). Following the logic behind Amdahl's law, it makes sense that making jQuery.event.fix faster would have the greatest impact on our apps. This article walks through: