Historically, we've added a significant amount of new material in every new edition. The 2nd edition was 195 pages, the 3rd edition was 304 pages, the 4th edition was 430 pages, and the 5th edition was 498 pages.
The 6th edition is also 498 pages but it actually contains much more than the 5th. That's because we rewrote the book to conform to current best practices, which let us cut out much of the old browser-dependent code. That is, by cutting out separate tasks on how to do something in Netscape 4 or Netscape 6+ or IE, we could instead add full coverage of Ajax (two full chapters of coverage, in fact: Introducing Ajax and Ajax Toolkits).
In the 6th edition, we also removed some chapters (Working with Visual Tools and Debugging Common Errors) and combined some others (Image Basics and More Fun with Images became Working with Images, for example).
One big change appeared in the 4th edition and has remained in subsequent editions: in the reference section in the back of the book, the Object Flowchart and the Object Table are now printed in glorious color, making it lots easier to see which objects work in which browsers.
The Student Edition was a special version of the 5th edition that includes everything in that edition, plus exercises and review materials for each chapter. Peachpit Press asked us to do it because the book is in such widespread use in colleges and universities. Each chapter contains the following:
Yes. You'll find a link to it on the Scripts page of this site. Of course, you can still copy and paste individual scripts.
We haven't made scripts available for download when they're straight HTML files. That is, those which are referenced in the book and by other scripts, but where the contents aren't given in the book. These are all just normal vanilla HTML files, and can be linked to any files that you have already.
Between teaching and working on our next books, we're not taking on any consulting projects at this time. Thanks for asking, though.
No. If we did, we would never have time to write our next books. And you wouldn't learn as much.
Sorry, no. Go talk to the author of the other book.
Again, we can't, because we get so much mail that we would never get new work done. We can recommend a really good HTML book, though; it's HTML, XHTML, and CSS: Visual QuickStart Guide, 6th edition, by our friend Elizabeth Castro. Clicking that link and buying that book from Amazon makes both us and Liz happy. Special note for the cat fancier: our cat Pixel is prominently featured on Page 105.
Sure you can. We just can't promise to answer individual questions, because of the time it takes. We will put frequently asked questions (and their answers!) here on this page as they come in.
Use the email address found in the book at the end of the Introduction. We read all mail sent to that address, though we can't guarantee a personal reply to every message. We regret that because of the large volume of email that we get, we cannot answer email about the book sent to our personal email addresses.
Not in this world of viruses being spread with email attachments. We've already been sent viruses by accident (or at least, they said it was an accident); we don't want any more. So we never open any files sent to us by people we don't know. Instead, you should post your pages on the Web, then send us the URL so we can take a look at the problem. We trust you, of course; it's the other guys that made us come up with this rule.
Most of the questions we get have to do with image manipulation: rollovers, banners, etc. It's difficult to debug scripts that involve images without having the images available, as quite often, the problem has to do with the way the images are referenced (e.g., directory structure issues, proper capitalization issues). So again, please, send us a URL of the problem page, and we'll be happy to take a look at it.
If you use the code from our book, we're happy to help you. However, if you use the code from our book and ask Microsoft or Adobe for help, they'll require you to start using their products first.
We have to ask the same thing. If you have a problem with an Adobe product, please contact Adobe. If you have a problem with a Microsoft product, please contact Microsoft. And if you have a problem with our code, please contact us. But the two of us can't afford to give multi-million dollar software companies free support for their products.
If you use Dreamweaver, you also might consider purchasing Adobe Dreamweaver CS4: Visual QuickStart Guide, which we also wrote.
The scripts in Chapter 17 are not standalone scripts; they are bookmarklets. If you go to the page for each individual script, you can drag each bookmarklet by clicking and dragging on its name to either the personal toolbar or Favorites bar in your browser.