Developing Extensions for Macromedia Dreamweaver 8
Authors: Sandstrom A.,  Berry B.
 Published year: 2005
 Pages: 83-84/282
Buy this book on amazon.com >>
 < Day Day Up > 

Chapter 14. Behaviors

Behaviors let users make their HTML pages interactive. They offer web designers an easy way to assign actions to page elements by filling in an HTML form.

The term behavior refers to the combination of an event (such as onClick , onLoad , or onSubmit ) and an action (such as Check Plugin, Go to URL, Swap Image). The browser determines which HTML elements accept which events. Files that list events that each browser supports are stored in the Configuration/Behaviors/Events folder within the Macromedia Dreamweaver 8 application folder.

Actions are the part of a behavior that you can control; when you write a behavior, you're really writing an Action file. Actions are HTML files. The BODY section of an Action file generally contains an HTML form that accepts parameters for the action (for example, parameters that indicate which layers to display or hide). The HEAD section of an Action file contains JavaScript functions that process form input from the BODY content and control the functions, arguments, and event handlers that are inserted into a user 's document.

You should write behavior actions when you want to share functions with users or when you want to insert the same JavaScript function repeatedly, but change the parameters each time.

NOTE

You cannot use behaviors to insert VBScript functions directly; however, you can add a VBScript function indirectly by editing the Document Object Model (DOM) in the applyBehavior() function.


The following table lists the files you use to create behavior actions:

Path

File

Description

Configuration/Behaviors/Actions/

behavior action .htm

The BODY of the file contains an HTML form for the action's parameters. The HEAD of the file contains the JavaScript functions.


NOTE

For information about server behaviors that provide web application functionality, see Chapter 15, "Server Behaviors," on page 321.


 < Day Day Up > 
 < Day Day Up > 

How Behaviors work

When a user selects an HTML element in a Dreamweaver document and clicks the Plus (+) button on the Behaviors panel, the following events occur:

1.

Dreamweaver calls the canAcceptBehavior() function in each Action file to see whether this action is appropriate for the document or the selected element.

If the return value of this function is false , Dreamweaver dims the action in the Actions pop-up menu. (For example, the Control Shockwave action is dimmed when the user's document has no SWF files.) If the return value is a list of events, Dreamweaver compares each event with the valid events for the currently selected HTML element and target browser until it finds a match. Dreamweaver populates the Events pop-up menu with the matched event from the canAcceptBehavior() function at the top of the list. If no match exists, the default event for the HTML element ( marked in the Event file with an asterisk [*]) becomes the top item. The remaining events in the menu are assembled from the Event file.

2.

The user selects an action from the Actions pop-up menu.

3.

Dreamweaver calls the windowDimensions() function to determine the size of the Parameters dialog box. If the windowDimensions() function is not defined, the size is determined automatically.

A dialog box always appears, with OK and Cancel buttons at the right edge, regardless of the contents of the BODY element.

4.

Dreamweaver displays a dialog box that contains the BODY elements of the Action file. If the Action file's BODY tag contains an onLoad handler, Dreamweaver executes it.

5.

The user fills in the parameters for the action. Dreamweaver executes event handlers that are associated with the form fields as the user encounters them.

6.

The user clicks OK.

7.

Dreamweaver calls the behaviorFunction() and applyBehavior() functions in the selected Action file. These functions return strings that are inserted into the user's document.

8.

If the user later double-clicks the action in the Actions column, Dreamweaver reopens the Parameters dialog box and executes the onLoad handler. Dreamweaver then calls the inspectBehavior() function in the selected Action file, which fills in the fields with the data that the user previously entered.

Inserting multiple functions in the user's file

Actions can insert multiple functions—the main behavior function plus any number of helper functions—into the HEAD section. Two or more behaviors can even share helper functions as long as the function definition is exactly the same in each Action file. One way of ensuring that shared functions are identical is to store each helper function in an external JavaScript file and insert it into the appropriate Action files using <SCRIPT SRC=" externalFile .js"> .

When the user deletes a behavior, Dreamweaver attempts to remove any unused helper functions that are associated with the behavior. If other behaviors are using a helper function, it is not deleted. Because the algorithm for deleting helper functions errs on the side of caution, Dreamweaver might occasionally leave an unused function in the user's document.

What to do when an action requires a return value

Sometimes an event handler must have a return value (for example, onMouseOver="window.status='This is a link'; return true" ). But if Dreamweaver inserts the "return behaviorName(args)" action into the event handler, behaviors later in the list are skipped .

To get around this limitation, set the document.MM_returnValue variable to the desired return value within the string that the behaviorFunction() function returns. This setting causes Dreamweaver to insert return document.MM_returnValue at the end of the list of actions in the event handler. For an example that uses the MM_returnValue variable, see the Validate Form.js file in the Configuration/Behaviors/Actions folder within the Dreamweaver application folder.

 < Day Day Up > 
Developing Extensions for Macromedia Dreamweaver 8
Authors: Sandstrom A.,  Berry B.
 Published year: 2005
 Pages: 83-84/282
Buy this book on amazon.com >>

Similar books