15.02.2013 Views

JavaScript Examples Bible - UserWorks Technologies

JavaScript Examples Bible - UserWorks Technologies

JavaScript Examples Bible - UserWorks Technologies

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

x<br />

<strong>JavaScript</strong> Example <strong>Bible</strong>: The Essential Companion to <strong>JavaScript</strong> <strong>Bible</strong><br />

count devil was all of the Example sections from the reference vocabulary. By being<br />

nondiscriminatory about these extractions — that is, extracting all of them instead<br />

of only selected sections — we could convey to readers a consistent organizational<br />

model.<br />

In the end, the extracted Example sections from Parts III and IV found their way into<br />

Appendix F on the CD-ROMs of both editions of the larger tome. I knew that as a<br />

reader of my own books (and one of a certain age at that) I would not enjoy having<br />

to flip back and forth between book and screen to refresh my memory about a term<br />

and see it in action. A more pleasing solution for many <strong>JavaScript</strong> <strong>Bible</strong> readers<br />

would be a separate volume containing a printed version of the <strong>Examples</strong> sections.<br />

The new volume would act as a companion to both the 4th and Gold editions of the<br />

<strong>JavaScript</strong> <strong>Bible</strong>.<br />

Using Appendix F as a starting point, I divided the content into chapters along the<br />

same lines as the <strong>JavaScript</strong> <strong>Bible</strong> reference sections. This also gave me a chance to<br />

study the examples for each chapter with fresh eyes. The examples haven’t<br />

changed, but I had the opportunity to direct the reader’s attention to examples that<br />

I thought were particularly helpful in mastering a document-level or core language<br />

object. Thus, each chapter of this book begins with a scene-setting introduction and<br />

a list of highlights to which you should pay special attention. Also, since you will<br />

likely be scanning through the book from time to time, I added many illustrations of<br />

the pages produced from the code listings. These figures will help you visualize what<br />

important listing code does when the page is loaded into a browser.<br />

Now you know the story behind the <strong>JavaScript</strong> <strong>Examples</strong> <strong>Bible</strong>. Some budgetconscious<br />

readers may not be thrilled to pay more for what appears to be a printout<br />

of content they already own in electronic format. If so, then please continue using<br />

the Acrobat version. But if, like me, you enjoy the portability and visual scanability<br />

of a printed work, then keeping this book near your <strong>JavaScript</strong> <strong>Bible</strong> volume will<br />

enhance your learning and research activities.<br />

Organization and Features of This Book<br />

Almost all chapters in this book correspond to similarly named chapters in Parts III<br />

and IV from the <strong>JavaScript</strong> <strong>Bible</strong> 4th and Gold editions. Although chapters in this<br />

book are consecutively numbered starting with Chapter 1, each chapter title<br />

includes a reference to the corresponding chapter number from the big books. For<br />

example, Chapter 1 of this book provides the <strong>Examples</strong> sections for terms related<br />

to generic HTML elements. That subject is covered in Chapter 15 of the big books.<br />

There is not always a one-to-one relationship between chapters. Several chapters of<br />

the big books have no <strong>Examples</strong> sections in them because sample code is embedded<br />

as part of the big book text. Therefore, don’t be surprised to see gaps in pointers<br />

to <strong>JavaScript</strong> <strong>Bible</strong> reference chapters.

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

Saved successfully!

Ooh no, something went wrong!