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
anddojo/connect
SCRIPT tags to a dijit in markupThe difference between a DOM node and a dijit; the difference between
dojo.byId
anddijit.byId
; the difference between DOM events and dijit eventsThe 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.
Get Dojo: The Definitive Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.