Section C. Separation of behavior and structure

C. Separation of behavior and structure

Separation of behavior and structure is easy to understand: just don't put any JavaScript code in your HTML page. This takes two steps:

1.	Put all JavaScript functions in a separate .js file that's linked to from all HTML pages that need it.
2.	Remove all event handlers from the HTML and put them in the same .js file.

Functions in separate file

JavaScript code belongs in the .js file, and not in HTML files.

Therefore, this is wrong:

   <script type="text/javascript">  function doAllKindsOfNiftyThings()  {      // JavaScript code  }  </script>  </head>  <body>  <h1>My HTML page</h1>  [etc.]

But this is right:

<script type="text/javascript" src="/books/1/521/1/html/2/nifty.js"></script> </head> <body> <h1>My HTML page</h1> [etc.] // in nifty.js function doAllKindsOfNiftyThings() {     // JavaScript code }

We'll discuss the technical aspects of <script> tags in 4D.

Remove event handlers from HTML

The second step in separating behavior and structure is to move all JavaScript calls within your HTML to the separate .js file. In fact, 99% of the JavaScript code in HTML pages consists of inline event handlers.

Here, the handlers are in the HTML, where they don't belong:

   <a href="home.html"     onMouseOver="mOv('home')"     onMouseOut="mOut('home')">Home</a>

Instead, define them in the separate .js file:

<a href="home.html">Home</a> // in separate .js file var nav = document.getElementById('navigation'); var navLinks = nav.getElementsByTagName('a'); for (var i=0;i<navLinks.length;i++) {     navLinks[i].onmouseover = [code];     navLinks[i].onmouseout = [code]; }

The script takes the element with id="navigation" (a <ul>, for instance) and accesses all of its links, then assigns onmouseover and onmouseout event handlers to them one by one.

Hooks and Event-Handler Registration

In order to fully understand the code on the previous page, you have to understand JavaScript hooksthe hook here is the ID that says "deploy the behavior here"and the various ways of registering event handlers. We'll discuss hooks in 4B and event-handler registration in 7C.

All example scripts separate behavior and structure, so you can take a look at the way they define event handlers if you prefer to study some practical examples right away.

The `JavaScript`: pseudo-protocol

Occasionally you'll see javascript: pseudo-protocol links like the following one:

   <a href="javascript:doAllKindsOfNiftyThings()">Do Nifty!</a>

This complicated and dirty code is secretly meant as an onclick event handler: when the user clicks on this link, we want to execute doAllKindsOfNiftyThings(). Therefore you should remove the javascript: call from the link and replace it with an onclick event handler in the separate .js file:

<a href="somepage.html" >Do Nifty!</a> // in separate .js file document.getElementById('nifty').onclick = doAllKindsOfNiftyThings;

As to the href, it should contain either a URL that noscript users can follow, or the entire link should be generated in JavaScript. We'll get back to this in 2F.

Noscript Users

When I talk about "noscript users" I mean those users whose browser, for whatever reason, does not support enough JavaScript to use a scripted interface. This may be because their browser doesn't support JavaScript at all, or because their browser supports some JavaScript, but not enough. Netscape 4 is a good example of the latter category.