This is the second part of our Dojo and jQuery side by side series. If you’re not following allowing with the series, do be sure to check out Part 1: Dom Basics.
As mentioned in the previous article, the aim here is to provide a simple unbiased side by side comparison of common jQuery operations and how they are achieved in Dojo.
Today, we’re looking at animation and as a quick reminder you should assume that all the calls below are called when the DOM is ready. If you’re not sure how to do this, checkout Part 1.
Dojo is a fantastic toolkit that we have used on many projects here at moresoda. Although we still love and use jQuery nearly everyday, we use Dojo on projects where the front end requirements are more complicated than your average DOM manipulation and HTML5 shims.
This article isnt about preaching Dojos benefits though. If you have a read of the features and benefits of Dojo you can make up your own mind. That being said, Dojo can be harder to get into since is it a much larger than jQuery.
Hence my aim here is to provide a simple, unbiased side by side comparison of common jQuery operations and how they are achieved in Dojo.
A few weeks ago Mike Boyink posted a great article entitled Show, Don’t Tell, where he put out a plea to all those writing articles about ExpressionEngine (EE) addons to show how they implement their must have addon as opposed to simply writing about how great they are.
We totally agree with Mike on this one, and as part of our initiative here at moresoda to "open up” about how we develop EE sites, we decided to start by writing about one of our must-have addons, morePreview.
Currently the web development world is alive with discussion surrounding technologies like HTML5, CSS3. I won’t go into what those technologies are, since that’s not the focus of this post, but I do want to bring attention to a dilemma surrounding what is known as Progressive Enhancement, which is currently how many web developers are (quite rightly) tackling the transition to these two new technologies.
Progressive enhancement is not a technology like HTML5 and CSS3, but merely an ideology. It allows you as a developer to ensure your website/application works across all browsers, however, certain features (such as drag and drop, animations etc) and only shown to browsers that support them. Many developers refer to this as graceful degradation.
