Dojo: The Definitive Guide

Summary

After reading this chapter, you should understand:

• The basic philosophy behind the design of Dijit

• The importance of low coupling and high cohesion in developing a complex application and the way that Dijit leverages these concepts to encapsulate functionality in dijits

• The importance of accessibility (a11y) in an application, as well as W3C Web Accessibility Initiative for Accessible Rich Internet Applications, and the basic a11y approach taken by Dijit

• That dijits can be implemented in markup such that they provide the same functionality as they would had they been created programmatically, and how to apply dojo/method and dojo/connect SCRIPT tags to a dijit in markup

• The difference between a DOM node and a dijit; the difference between dojo.byId and dijit.byId ; the difference between DOM events and dijit events

• The basic steps the parser takes to instantiate a dijit that is defined in markup

• The basic architectural breakdown of Dijit into form dijits, layout dijits, and general purpose application dijits, as well as where to start looking for a particular kind of dijit

Next we're going to take a look at Dijit's anatomy and lifecycle.