Both books are exactly what they need to be. Nonetheless, I had the feeling that there is a market for a book that's somewhere in between: a book that explains more of the technical details than Keith's does, but not quite as much as Flanagan's does.
Therefore right now the best way to describe my book is as the sequel to Jeremy's. Once you really understand all that he explains, the time has come to immerse yourself in the more advanced features and problems of the language, as well as some nasty browser incompatibilities that can ruin your day (and your hair).
Does that mean that you should treat these three vastly different topics in the course of one chapter? On the pro side, in order to explain the script well you should explain Core, Events and DOM, because your readers need that knowledge. On the con side, if you keep doing that the book will quickly become a confused jumble of topics and subjects, where Events basics are explained in one chapter, a few more basics in another, and some advanced topics in yet another.
My solution is to strictly separate all these subjects, and to make every chapter treat all the important aspects of its topic. However, to be able to do so I had to do some serious thinking on the example scripts themselves. As I said, even the tiniest example script uses Core, Events, and DOM. How can the reader understand the entire script when the chapter he's reading only explains the Core features, but not Events and DOM?
This is the blog of Peter-Paul Koch, web developer, consultant, and trainer.
You can also follow
him on Twitter or Mastodon.
If you like this blog, why not donate a little bit of money to help me pay my bills?
Comments are closed.
1 Posted by Small Paul on 27 June 2006 | Permalink
Just one question: what's BOM? Browser Object Model?
2 Posted by Scott Dowding on 29 June 2006 | Permalink
I second that question! What's BOM?
3 Posted by aaron on 29 June 2006 | Permalink
ahhhh i was hoping to get the advanced and dense stuff from you, but i'll prob get it anyway. Yes, BOM is browser object model.
4 Posted by Ross Bruniges on 29 June 2006 | Permalink
You mentioned Jeremy and David's books in comparison to yours - how would you that it compares to Stuart Langridges DHTML Utopia book???
5 Posted by ppk on 3 July 2006 | Permalink
Chapter 5, especially, is quite dense enough, thank you. Some other chapters feature a bit of lighter stuff.
As to Stuart's book, I'm not sure how to compare it to mine. It's really hard, this comparison stuff.
6 Posted by gusc on 6 July 2006 | Permalink
7 Posted by Carlton on 12 July 2006 | Permalink
Hope it sells well!
8 Posted by Tadeusz Szewczyk on 14 July 2006 | Permalink
9 Posted by Brayn Flexeril on 17 July 2006 | Permalink
Plz tell me where can I find more info about Browser Object Model?
10 Posted by ppk on 18 July 2006 | Permalink
In chapter 6 of my book, obviously.
11 Posted by Alex on 20 July 2006 | Permalink
The main thing I use my current JS bible (Quickstart Guide - http://www.amazon.com/gp/product/0201735172/104-8909427-5091136?v=glance&n=283155) for is JS and CSS object tables. The tables in the back of that are pretty cool- does you book have that kind of thing?
12 Posted by ppk on 20 July 2006 | Permalink
No, all compatibility tables will remain on this site, where they belong. A compatibility table in a book is outdated the moment the book is printed, and I want to continue updating mine.
13 Posted by Frederick C. Lee on 30 July 2006 | Permalink
We have all these versions but I don't know what browsers cover which versions of what.
What's the difference between versions 1.5 and 1.6?
Do you cover XAJAX technologies? I want to know how to process DOMs between PHP and Javascipt. And which browser best supports the W3C standands of these technologies.
... Looking forward to reviewing your book.
14 Posted by ppk on 2 August 2006 | Permalink
The book doesn't cover JS 1.6, just plain old 1.5 . Remember that at the moment 1.6 is supported only by Mozilla.
So the answer is: No, my book doesn't treat all that.