MACROMEDIA DREAMWEAVER 8-EXTENDING DREAMWEAVER Manual page 106

How Dreamweaver processes JavaScript in
extensions
Dreamweaver checks the Configuration/extension_type folder during startup. If it encounters
an extension file within the folder, Dreamweaver processes the JavaScript by completing the
following steps:
Compiling everything between the beginning and ending
Executing any code within
This procedure is necessary during startup because some extensions might require
global variables to initialize.
Dreamweaver performs the following actions for any external JavaScript files that are specified
in the attributes of
SRC
Reads in the file
Compiles the code
Executes the procedures
If any JavaScript code in your extension file contains the string
JavaScript interpreter reads the string as an ending
unterminated string literal error. To avoid this problem, break the string into pieces
and concatenate them like this:
Dreamweaver executes code in the
when the user selects the command or action from a menu for the Command and Behavior
action extension types.
Dreamweaver executes code in the
document contains a form for object extensions.
Dreamweaver ignores the
Data translator
Property inspector
Floating panel
For all extensions, Dreamweaver executes code in other event handlers (for example,
onBlur="alert('This is a required field.')"
fields to which they are attached.
106 Extending Dreamweaver
tags that is not part of a function declaration
SCRIPT
tags:
SCRIPT
"<' + '/SCRIPT>"
event handler (if one appears in the
onLoad
event handler on the
onLoad
handler on the
onLoad
tags
SCRIPT
tag and reports an
SCRIPT
.
tag if the body of the
BODY
tag in the following extensions:
BODY
) when the user interacts with the form
, the
"</SCRIPT>"
tag)
BODY