Recent Blog PostsNo sooner than I wrote about how to control a JavaScript function’s context with the Prototype Function.bind(), jQuery 1.4 is released and one of its new tricks is $.proxy(), which we can use for exactly the same purpose.
Keeping your JavaScript code organized and readable can be a bit of a task. Since I started with jQuery, most of the JavaScript for my applications has just been inside a giant $(function() { }) block, and as the code grows longer and more complex, it becomes much harder to find the thing you’re looking for and edit it later. I was searching for a design pattern that would help me organize my code in a way such that I wouldn’t dread looking at my JavaScript files in the future. My solution came in the form of namespacing and building modules with function prototypes.
It’s been a while since I posted so I thought I’d do a general update. At the start of November I started a new position as a front end developer for Eventful, a site which maintains a listing of various local events. Of course this means that I’ve had much less time to work on JCWS projects, but it also means I’ve been gaining a truckload of valuable experience with things I haven’t done before.
This past Saturday, HTML5 Gallery featured the Jimmy Cuadra Web Services site. HTML5 Gallery states its purpose as being twofold:
When I first heard about CSS3 transitions and CSS3 animations, I didn’t really think it was a good idea. One of the main purposes of CSS has been to separate presentational information from structural markup and data. This seemed like a good set up: HTML for structure and data, CSS for presentation, and JavaScript for behavior. Adding behavioral elements to CSS that should be done in JavaScript seemed like it was blurring the lines in a bad way.