About this Book - Revision history

Neil: Text replacement - "" to "
"
2016-10-27T19:56:33Z
Text replacement - "<table border="0" cellspacing="0">" to "<table border="0" cellspacing="0" width="100%">"

← Older revision Revision as of 19:56, 27 October 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0">
+
<table border="0" cellspacing="0" width="100%">

<tr>

<tr>

<td width="20%">[[JavaScript Essentials|Previous]]<td align="center">[[JavaScript Essentials|Table of Contents]]<td width="20%" align="right">[[Intended Audience|Next]]</td>

<td width="20%">[[JavaScript Essentials|Previous]]<td align="center">[[JavaScript Essentials|Table of Contents]]<td width="20%" align="right">[[Intended Audience|Next]]</td>

Neil: Text replacement - "" to "
"
2016-05-05T14:36:21Z
Text replacement - "<table border="0" cellspacing="0" width="100%">" to "<table border="0" cellspacing="0">"

← Older revision Revision as of 14:36, 5 May 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0" width="100%">
+
<table border="0" cellspacing="0">

<tr>

<tr>

<td width="20%">[[JavaScript Essentials|Previous]]<td align="center">[[JavaScript Essentials|Table of Contents]]<td width="20%" align="right">[[Intended Audience|Next]]</td>

<td width="20%">[[JavaScript Essentials|Previous]]<td align="center">[[JavaScript Essentials|Table of Contents]]<td width="20%" align="right">[[Intended Audience|Next]]</td>

Neil: Text replacement - "BUY_JAVASCRIPT" to "jscript"

2016-02-01T22:24:38Z

Text replacement - "<google>BUY_JAVASCRIPT</google>" to "<htmlet>jscript</htmlet>"

Neil at 18:48, 15 April 2009

2009-04-15T18:48:11Z

Neil at 13:41, 15 April 2009

2009-04-15T13:41:38Z

Neil at 17:01, 12 June 2007

2007-06-12T17:01:17Z

Neil at 13:14, 30 May 2007

2007-05-30T13:14:45Z

Neil at 18:09, 21 May 2007

2007-05-21T18:09:58Z

Neil at 18:09, 21 May 2007

2007-05-21T18:09:43Z

Neil at 18:04, 18 May 2007

2007-05-18T18:04:33Z

← Older revision		Revision as of 22:24, 1 February 2016
Line 8:		Line 8:


−	<~~google~~>~~BUY_JAVASCRIPT~~</~~google~~>	+	<htmlet>jscript</htmlet>

@@ Line 6: / Line 6: @@
 </table>
 <hr>
 '''Welcome to JavaScript Essentials'''

@@ Line 11: / Line 11: @@
 Before JavaScript was created, a typical web browsing experience consisted largely of displaying static pages of information. Any type of user interaction with a web page usually involved the browser sending information back to the web server where some type of server based script or other program would validate the user's data input. The server would then send back either a static error page if the user had entered invalid data or, assuming successful validation, return a static page to the web browser containing the results of the transaction. In addition, the lack of a mechanism to implement dynamic web page content and behavior dictated that an entirely new web page be loaded in order to display new information.
-It quickly became clear that a way of perfoming "client-side" or "web browser-side" processing was needed. The original intent for JavaScript, therefore, was to address this need by allowing such tasks as validating user input before it is transmitted to the web server, and creating dynamic web page content and layouts independently of the web server (for example, displaying different text depending on a user's actions within the page).
+It quickly became clear that a way of performing "client-side" or "web browser-side" processing was needed. The original intent for JavaScript, therefore, was to address this need by facilitating such tasks as validating user input before it is transmitted to the web server, and creating dynamic web page content and layouts independently of the web server (for example, displaying different text depending on a user's actions within the page).
 JavaScript met and, indeed, exceeded these requirements by providing an extremely flexible and intuitive scripting language. The problem today is that, as with any useful technology, JavaScript has been used in ways never anticipated by its original authors. As a result, the potential uses of JavaScript have grown far beyond the needs of the average person looking to add dynamic behavior to web pages. The result of this is that JavaScript book authors also feel the need to cover every possible capability of JavaScript, often to the extent that the average JavaScript reference book now runs to over 1,000 pages.
-The purpose of this book, therefore, is to provide the essentials of JavaScript so that anyone with a web site can use this powerful scripting language quickly and effectively without having to learn things that, whilst within the capabilities of JavaScript, aren't actually needed by the average web designer. That said, this book does not take any shortcuts. It provides detailed and indepth knowledge of all aspects of JavaScript from language basics through to advanced topics.
+The purpose of this book, therefore, is to provide the essentials of JavaScript so that anyone with a web site can use this powerful scripting language quickly and effectively without having to learn things that, whilst within the capabilities of JavaScript, aren't actually needed by the average web designer. That said this book does not take any shortcuts. It provides detailed and in depth knowledge of all aspects of JavaScript from language basics through to advanced topics.
 This book is designed to provide a detailed and comprehensive, yet easy to follow, guide to developing powerful, dynamic web pages using JavaScript. It could be said that the object of '''JavaScript Essentials''' is to provide you with everything you need to use JavaScript, and nothing that you don't.

@@ Line 3: / Line 3: @@
 Before JavaScript was created, a typical web browsing experience consisted largely of displaying static pages of information. Any type of user interaction with a web page usually involved the browser sending information back to the web server where some type of server based script or other program would validate the user's data input. The server would then send back either a static error page if the user had entered invalid data or, assuming successful validation, return a static page to the web browser containing the results of the transaction. In addition, the lack of a mechanism to implement dynamic web page content and behavior dictated that an entirely new web page be loaded in order to display new information.
-It quickly became clear that a way of perfoming "client-side" or "web browser-side" processing was needed. The original intent for JavaScript, therefore, was to address this need by allowing such tasks as validating user input before it is transmitted to the web server, and creating dynamic web page content and layouts independently of the web server (for example displaying different text depending on a user's actions within the page).
+It quickly became clear that a way of perfoming "client-side" or "web browser-side" processing was needed. The original intent for JavaScript, therefore, was to address this need by allowing such tasks as validating user input before it is transmitted to the web server, and creating dynamic web page content and layouts independently of the web server (for example, displaying different text depending on a user's actions within the page).
 JavaScript met and, indeed, exceeded these requirements by providing an extremely flexible and intuitive scripting language. The problem today is that, as with any useful technology, JavaScript has been used in ways never anticipated by its original authors. As a result, the potential uses of JavaScript have grown far beyond the needs of the average person looking to add dynamic behavior to web pages. The result of this is that JavaScript book authors also feel the need to cover every possible capability of JavaScript, often to the extent that the average JavaScript reference book now runs to over 1,000 pages.
-The purpose of this book, therefore, is to provide the essentials of JavaScript so that anyone with a web site can use this powerful scripting language quickly and effectively without having to learn things that, whilst within the capabilities of JavaScript, aren't actually needed by the average web designer. That said, this book does not take any shortcuts. It provides detailed and indepth knowledge of all aspects of JavaScript from language basics through to advanced topics
+The purpose of this book, therefore, is to provide the essentials of JavaScript so that anyone with a web site can use this powerful scripting language quickly and effectively without having to learn things that, whilst within the capabilities of JavaScript, aren't actually needed by the average web designer. That said, this book does not take any shortcuts. It provides detailed and indepth knowledge of all aspects of JavaScript from language basics through to advanced topics.
 This book is designed to provide a detailed and comprehensive, yet easy to follow, guide to developing powerful, dynamic web pages using JavaScript. It could be said that the object of '''JavaScript Essentials''' is to provide you with everything you need to use JavaScript, and nothing that you don't.

← Older revision		Revision as of 18:09, 21 May 2007
Line 1:		Line 1:
−	Welcome to JavaScript Essentials.	+	'''Welcome to JavaScript Essentials'''

	Before JavaScript was created, a typical web browsing experience consisted largely of displaying static pages of information. Any type of user interaction with a web page usually involved the browser sending information back to the web server where some type of server based script or other program would validate the user's data input. The server would then send back either a static error page if the user had entered invalid data or, assuming successful validation, return a static page to the web browser containing the results of the transaction. In addition, the lack of a mechanism to implement dynamic web page content and behavior dictated that an entirely new web page be loaded in order to display new information.		Before JavaScript was created, a typical web browsing experience consisted largely of displaying static pages of information. Any type of user interaction with a web page usually involved the browser sending information back to the web server where some type of server based script or other program would validate the user's data input. The server would then send back either a static error page if the user had entered invalid data or, assuming successful validation, return a static page to the web browser containing the results of the transaction. In addition, the lack of a mechanism to implement dynamic web page content and behavior dictated that an entirely new web page be loaded in order to display new information.

@@ Line 1: / Line 1: @@
-<table border="0" cellspacing="0">
+<table border="0" cellspacing="0" width="100%">
 <tr>
 <td width="20%">[[JavaScript Essentials|Previous]]<td align="center">[[JavaScript Essentials|Table of Contents]]<td width="20%" align="right">[[Intended Audience|Next]]</td>

← Older revision		Revision as of 17:01, 12 June 2007
Line 1:		Line 1:
		+	<table border="0" cellspacing="0" width="100%">
		+	<tr>
		+	<td width="20%">[[JavaScript Essentials\|Previous]]<td align="center">[[JavaScript Essentials\|Table of Contents]]<td width="20%" align="right">[[Intended Audience\|Next]]</td>
		+	<tr>
		+	<td width="20%">Table of Contents<td align="center"><td width="20%" align="right">Intended Audience</td>
		+	</table>
		+	<hr>
		+
	'''Welcome to JavaScript Essentials'''		'''Welcome to JavaScript Essentials'''

@@ Line 1: / Line 1: @@
 Welcome to JavaScript Essentials.
-Before JavaScript was created a typical web browsing experience consisted largely of displaying static pages of information. Any type of user interaction with a web page usually involved the browser sending information back to the web server where some type of server based script or other program would validate the user's data input. The server would then send back either a static error page if the user had entered invalid data or, assuming successful validation, return a static page to the web browser containing the results of the transaction. In addition, the lack of a mechanism to implement dynamic web page content and behavior dictated that an entirely new web page be loaded in order to display new information.
+Before JavaScript was created, a typical web browsing experience consisted largely of displaying static pages of information. Any type of user interaction with a web page usually involved the browser sending information back to the web server where some type of server based script or other program would validate the user's data input. The server would then send back either a static error page if the user had entered invalid data or, assuming successful validation, return a static page to the web browser containing the results of the transaction. In addition, the lack of a mechanism to implement dynamic web page content and behavior dictated that an entirely new web page be loaded in order to display new information.
 It quickly became clear that a way of perfoming "client-side" or "web browser-side" processing was needed. The original intent for JavaScript, therefore, was to address this need by allowing such tasks as validating user input before it is transimitted to the web server, and creating dynamic web page content and layouts independently of the web server (for example displaying different text depending on a user's actions within the page).