This is a great book for beginning web developers who learn through examples. Don’t plan on using this book as a reference, but rather get ready to get your hands dirty typing in code so that you can really learn it.
- Step-by-step instructions make it easy to move through the book.
- The length is good to get the chapters done in the alloted time (i.e. 1 hour per chapter for 24 hours total)
- Covers elements of scripting like best practices that are often left out of other programming books
- Lots of examples in every chapter to illustrate what you’re learning
- It is not written as a reference book, and so can be confusing if you’re not already familiar with the terms.
- You will be expected to read the scripts in the examples and try them out so that you understand them.
- The book is fairly short so some
- Publisher: Sams
- Price: $34.99
- Length: 442 pages
- Released: May 2010
- Section 3 introduces the DOM with chapters about responding to events, windows, forms, style sheets, the W3C, and advanced DOM features.
- Section 4 gets more advanced with chapters on scripting best practices, debugging, Ajax, and using Greasemonkey.
- Like the other Sams Teach Yourself books, each chapter is intended to be an hour of work to learn the language. The chapters end with a Q&A section, a quiz and some exercises to practice what you learned that hour.
Each chapter is intended to be consumed in about an hour with the reader following along at his or her computer—writing the scripts on web pages as the author presents them.
What I Like Best
This chapter includes information on progressive enhancement and recommends just like the W3C that you avoid doing things that are specific to one browser (no matter how tempting that may be). It also covers accessibility and usability which is great.
Of course, then this chapter goes into browser sniffing, with the implication that you can (and should?) test for browsers by reading their browser information. But then it redeems itself by covering feature sensing, where you test for a feature (like the
CANVAS element) and then run your script or not depending upon whether the user agent supports that feature.