- Shopping Bag ( 0 items )
PART I: Building Killer Web Pages for Fun and Profit.
Chapter 2: Writing Your Very First Script.
PART II: Adding Intelligence to Your Web Pages.
Chapter 4: Spy! Detecting Your Users' Browser Environment.
Chapter 5: Making Every Date Count.
Chapter 6: That's How the Cookie Crumbles.
PART III: Making Your Web Pages Interactive.
Chapter 7: Button Up!
Chapter 8: Picture Perfect.
Chapter 9: Roll Over, Boy! Good Mouse!
Chapter 10: Hunting and Gathering (And Validating) User Input.
Chapter 11: Framed Again!
PART IV: Automating Your Web Site.
Chapter 12: DHTML Dyn-o-mite!
Chapter 13: Timing Is Everything.
PART V: The Part of Tens.
Chapter 17: Ten (Or So) Tips for Debugging Your Scripts.
Appendix C: Document Object Model Reference.
Appendix D: Special Characters.
Appendix E: About the CD.
End-User License Agreement.
Book Registration Information.
In This Chapter
The beauty of an interpreted language is that if you've made a mistake halfway through your script, the first part still runs; creating a script is not an all-or-nothing proposition, the way it is with a compiled language. Unfortunately, using an interpreted language also means that if you don't test your script thoroughly, it may look fine when it loads and even run fine -- until a user does something that you didn't test!
Join the club!
So what's all the fuss? Just this: The number of computers hooked up to the Internet is rising about 10 percent each month. A recent Consumer Online Services report estimates that online industry revenues, which reached $2.2 billion in 1995, will top $14 billion by the year 2000. Yes, folks, there's a great deal of money to be made. And for some unspecified length of time because we all know that the tax man will find a way to take all the fun out of it before long, it's there for the taking -- and you don't need a degree in computer science to take advantage of it, either.
Professional marketing and sales types especially love the Web because
Non-business folks love the Web because
Brave new world
<SCRIPT>...</SCRIPT> tag, which you become intimate with in Chapter 3.
It's to everyone's advantage if extensions become part of the standard or at the very least are adopted by lots of vendors and so become a de facto standard. Therefore, folks who come up with HTML extensions typically submit their extensions to the WWW Consortium the committee responsible for the HTML standard for approval as soon as possible.
If Web clients and servers are different machines -- and they typically are -- some indeterminate amount of phone line connects them. Thus, every time a client asks a server for a favor usually to check a database or run some complicated program that the client doesn't want to bother cluttering up its disk space with, the client has to wait for the message to travel to the server and for the answer to make the return trip home. The potential for some slowed-down processing is found here, to say nothing of the expense somebody's paying the phone bill for all this chitchatting.
Besides, CGI programs run on the server, not the client, so even if you bribe the nearest code jockey and succeed in obtaining a CGI program, that CGI program can potentially slow down the response that your Web page viewers experience each time it the CGI program is invoked. Maybe this delayed response isn't a problem for the Web pages you're going to write -- but maybe it is. Remember, we live in a culture that would rather squeeze a processed cheese-like substance from a tube than take five minutes to microwave real cheddar.
A keyboard event occurs when someone types some information into a form you have provided them. See, this isn't so tough now, is it? If you've used a search engine such as Yahoo! or Magellan on the Web, you've had firsthand experience with initiating keyboard events, because in all likelihood you've typed the name of a subject into an entry field to search for related Web pages. Each keystroke that you typed represented a keyboard event.
If, after you type armadillo, you press the Enter key to begin the search process, you initiate another keyboard event. On the other hand, if you put your mouse pointer also called a cursor, but this is a family-values kind of book, so I say pointer instead over a button marked Search and click the mouse button, you initiate a mouse event, which is described in more detail in the following section.
The place on the screen where a user is most likely to interact with your page is called a control. Controls, as shown in Figure 1-1, include such things as text fields, push buttons, checkboxes, and radio buttons. Radio buttons are so called because they resemble buttons on the kind of old-style radio on which, when you pushed down one button, all the other buttons popped up. A user can initiate a mouse event by clicking on a control with the mouse or by dragging the mouse pointer around on the screen.
onUnload event handlers, which are used to implement page navigation events, are discussed in detail in Chapter 14.
For example, when a Netscape Communicator user clicks on File-->Open Page
You also need hardware installed that lets you connect to the Internet. This hardware usually consists of a modem and a phone line. Depending on your computer, you may have an internal modem installed IBM Thinkpads, for example, come complete with a built-in modem. If not, you can buy a modem at your local computer discount store. Something to look for is the modem line speed: the faster, the better. Netscape suggests a modem speed of 14.4 Kbps or faster. If you don't already have a modem and need to purchase one, consider buying the fastest modem in your price range; you'll be very glad you did when you try to look at spiffy Web pages with many graphics, each of which takes a loooong time to load because graphics files are typically so large.
If you're already connected to the Internet, disregard this section
First off, you need software that enables you to connect to the Internet. I won't even begin to pretend that I have the magical powers to spell out precisely what you need to accomplish this, but in general terms, you need
Unfortunately, instructions for installing communications software rarely involve plain English. So if you get stuck, you may want to take a look at The Internet For Dummies®, 4th Edition, by John R. Levine, Carol Baroudi, and Margaret Levine Young published by IDG Books Worldwide, Inc., for a really great detailed explanation of how to get set up.
Four choices for Navigator client browsers are currently available: Netscape Navigator 3.0x, Netscape Navigator Gold 3.0x, Netscape Navigator Personal Edition, and the prerelease 3 version of Netscape Navigator 4.0 available with Communicator.
You can download a copy of Navigator for a free trial period by visiting the following site:
assuming, unfortunately, that you already have a Web browser installed or that you have access to FTP. FTP is short for file transfer protocol, which is an Internet application that enables you to nab files from other people's machines. Of course, you can also run right out and buy a copy of Navigator at pretty much any store that sells software.
On the Microsoft side, you need to get version 3.0x of Internet Explorer or higher I recommend Version 4.0. Internet Explorer is a Web browser that's tightly integrated with Windows 95 and boasts integration with a lot of really cool technologies, including Java applets and something called ActiveX. At the time I'm writing this, the latest release is available for all versions of Windows and Macs. You can download it for free from
Chapter 2 is devoted to helping you get the correct version of Navigator or Internet Explorer, installing it, and using it. Skip ahead and check this chapter out right now if you want. I'll wait for you.
For Netscape Navigator and Microsoft Internet Explorer documentation, respectively, check out the following URLs:
For clarification on HTML issues, you may want to take a look at the following URL. It points to the WWW Consortium's huge overview of HTML-related materials.
Posted December 1, 2002
Posted May 8, 2001
Posted April 4, 2001
Posted September 26, 2000
I gave this book a fair chance (about 40 hrs) and gave up. This book uses keywords in its examples that are not defined in the book!!!!. Its pretty hard to program something when you have to guess keywords.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted June 30, 2000
Posted March 19, 2000
Posted March 3, 2000
Posted March 3, 2000
This was very much so a waist of money. I read the book and never figured out what was going on and how I would do it. This might be a good book if you are experienced, but for a novice, this book is way to confusing.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted February 28, 2000
Contrary to popular belief, this book is very coherent and descriptive in giving the reader what they expect. Why other people have commented negatively on the subject of this book, I do not, and never will, know. Excellent - Highly ReccomendedWas this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted March 17, 2010
No text was provided for this review.