15.02.2013 Views

JavaScript Examples Bible - UserWorks Technologies

JavaScript Examples Bible - UserWorks Technologies

JavaScript Examples Bible - UserWorks Technologies

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Preface<br />

Acommon thread running throughout most of my computer-book–writing<br />

career is that I tend to write a book I wish I had had in order to learn a new<br />

technology in the first place. Because I must write that book without the benefit of<br />

existing models, I begin by doing my best to master the technology, and then I write<br />

the book to help other newcomers learn as much as I did, but more quickly and<br />

with less pain, anguish, and confusion. To accomplish that goal, I write as much<br />

content as I feel is necessary to cover the topic in the depth that my readers<br />

require.<br />

When I started on what became the 4th and Gold editions of the <strong>JavaScript</strong> <strong>Bible</strong>,<br />

there were models to follow (my previous three editions) plus a substantial amount<br />

of brand new material, much of which had not yet been documented anywhere. I<br />

also assumed the responsibility of integrating the frequently conflicting and competing<br />

philosophies of the ways the <strong>JavaScript</strong> language is applied to a variety of<br />

browser brands and versions. Resolving these conflicts is a challenge that I face in<br />

my own programming work with clients, and I take great pleasure in sharing my<br />

solutions and approaches with other programmers floating in the same boat.<br />

As my editor and I began counting the pages I had assembled for these new editions,<br />

we discovered that the number of pages far outstripped the printer’s binding<br />

capabilities, even in a thicker volume made possible by using a hard cover (the<br />

Gold edition). Certainly not all of the words that I had written were so precious that<br />

some of them couldn’t be cut. But we were hundreds of pages beyond capacity. To<br />

cut that much content would have forced exclusion of coverage of language or document<br />

object model vocabulary.<br />

Fortunately, as had been done in previous editions, the plan for the new editions<br />

included Adobe Acrobat versions of the books on the accompanying CD-ROM.<br />

Although a significant compromise to ease of reading, it was possible to move some<br />

of the book’s content to the CD-ROM and leave the most important parts on the<br />

printed page. For the softcover 4th edition, reference chapters covering less-used or<br />

advanced subjects were pulled from print; for the hardcover Gold edition, which<br />

was longer and targeted more for professional scripters, the advanced chapters<br />

were put back into the book (along with 15 additional chapters for that edition),<br />

and the <strong>JavaScript</strong> tutorial was exiled to the CD-ROM.<br />

But even after making the difficult decisions about which chapters could go to the<br />

CD-ROMs, the page counts for both volumes were still excessive. Something else —<br />

something big — had to go. The remaining bundle that could free us from the page

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!