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.
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.
Many people start their website development with what’s known as a base stylesheet, this tends to include a reset, then some base styles, and then a few specific definitions. In this post I’m going to run through our base stylesheet (which tends to get amended every few weeks)