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.
I’ve been doing some playing with pseudo-elements recently on a personal project, and ended up doing a little bit of reading up about CSS gradients. I can’t remember where the article was, it’s not important really, but I wanted to share what I’ve managed to achieve with them.
For the second time in as many weeks, I have found myself talking to business owners about the lack of care they have been shown by their agency. I’m pleased to say neither related to projects we had delivered!
Looking for inspiration? Here are some website recommendations for you to feast your eyes on. This week’s selection includes an Oyster Restaurant and a Tasmanian Design Agency!
We send a variety of email marketing for various clients. Recent activity has prompted questions about ‘open rates’ and ‘click rates’ and what constitutes a successful campaign. ‘Open rates’ are expressed as a percentage of emails opened from total emails sent. ‘Bounces’ are different kettle of fish which can be discussed at greater length another time.
Although similar in terms of principle and process, there are different rules that should be observed when designing for the web as opposed to designing for print. These new rules came as a bit of a revelation after 10 years of designing with printed media in mind. Luckily, team moresoda have been on hand to gently suggest how I might better change my mindset from print to web.
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.
At some point in most web projects there comes a point where we have to present our designs to a client. This can be quite an emotional stage because, as a team, we feel we’ve arrived at a design that ticks all the boxes: it’s innovative, usable and will deliver on the project goals. We’ve become attached to this design and want everyone else to like it as much as we do. Ultimately however, we realise they just might not like it and this makes the whole process quite nerve-wracking.
