When a Dreamweaver user creates a new blank template of type DWTemplate_PHP, Dreamweaver lets the user create PHP server behaviors in the file. Furthermore, when the user creates instances of the new template, the user can create PHP server behaviors in the instance. In the previous example, when the user saves the template, Dreamweaver automatically adds a.php.dwt extension to the file. When the user saves an instance of the template, Dreamweaver adds the.php extension to the file.
Document extensions and file types By default, Dreamweaver shows all the file types it recognizes in the File > Open dialog box. After creating a new document type, extension developers need to update the appropriate Extensions.txt file. If the user is on a multiuser system (such as Windows XP, Windows 2000, or Mac OS X), the user has another Extensions.txt file in their Configuration folder. The user must update the Extensions.txt file because it is the instance that Dreamweaver looks for and parses. The location of the users Configuration folder depends on the users platform. For Windows 2000 and Windows XP platforms:
<drive>:Users:<username>:Library:Application Support: Macromedia:Dreamweaver MX 2004:Configuration
If Dreamweaver cannot find the Extensions.txt file in the users Configuration folder, Dreamweaver looks for it in the Dreamweaver Configuration folder.
Note: On multiuser platforms, if you edit the copy of Extensions.txt that resides in the Dreamweaver Configuration folder and not the one in the users Configuration folder, Dreamweaver is not aware of the changes because Dreamweaver parses the copy of the Extensions.txt file in the users Configuration folder, not the file in the Dreamweaver Configuration folder.
Suppose you want to create a new document extension. To create a new document extension, you can either add the new extension to an existing document type or create a new document type.
To add a new extension to an existing document type:
1 Edit MMDocumentTypes.xml. 2 Add the new extension to the winfileextension and macfileextension attributes of the

existing document type.

To add a new document type:
new file type can have, separated by commas; then add a colon and a brief descriptive phrase to show in the pop-up menu for file types that appears in the File > Open dialog box. For example, for JPEG files, enter JPG,JPEG,JFIF:JPEG Image Files 4 Save the Extensions.txt file. 5 Restart Dreamweaver. To see the changes, select File > Open and click the pop-up menu of file types.
To change the Dreamweaver default File > 0pen file type:
1 Make a backup copy of the Extensions.txt file in the Configuration folder. 2 Open Extensions.txt in Dreamweaver or a text editor. 3 Cut the line that corresponds to the new default, and paste it at the beginning of the file, to

The Insert bar definition file
The Configuration/Objects/insertbar.xml file defines the Insert bar properties. This XML file contains definitions for each individual object, in the order that the objects appear. The first time a user starts Dreamweaver, the Insert bar appears horizontally above the document. After that, its visibility and position are saved in the registry. Insertbar.xml tag hierarchy The following example shows the format and hierarchy of nested tags in the insertbar.xml file:
<?xml version="1.0" ?> <!DOCTYPE insertbarset SYSTEM "-//Macromedia//DWExtension insertbar 5.0"> <insertbar xmlns:MMString="http://www.macromedia.com/schemes/data/string/"> <category id="DW_Insertbar_Common" MMString:name="insertbar/categorycommon" folder="Common"> <button id="DW_Hyperlink" image="Common\Hyperlink.png" MMString:name="insertbar/hyperlink" file="Common\Hyperlink.htm" /> <button id="DW_Email" image="Common\E-Mail Link.png" MMString:name="insertbar/email" file="Common\E-Mail Link.htm" /> <separator /> <menubutton id="DW_Images" MMString:name="insertbar/images" image="Common\Image.png"> <button id="DW_Image" image="Common\Image.png" MMString:name="insertbar/image" file="Common\Image.htm" />. </menubutton> <separator /> <button id="DW_TagChooser" MMString:name="insertbar/tagChooser" image="Common\Tag Chooser.gif" command="dw.showTagChooser()" codeOnly="TRUE"/> </category>. </insertbar>
Chapter 6: Insert Bar Objects
Note: Although the insertbar and category tags use </insertbar> and </category> closing tags to denote the end of their content, the tags button, checkbutton, and separator do not have related closing tags. Instead button, checkbutton, and separator use a slash (/) before the closing bracket to denote the end of their attributes and content.
Insert bar definition tags The insertbar.xml file contains the following tags and attributes: <insertbar>

To create a submenu while moving a menu item:
1 Place the insertion point inside a menu (somewhere between a menu tag and the
corresponding /menu tag).
2 Insert a new menu tag and /menu tag pair inside the menu. 3 Add new menu items to the new submenu.
To insert a separator between two menu items:
Place a separator/ tag between the two menuitem tags.
To remove an existing separator:
Delete the corresponding separator/ line.

To move a menu:

in Dreamweaver.)
4 Cut an entire menu and its contents, from the opening menu tag to the closing /menu tag. 5 Place the insertion point at the new location for the menu. (Make sure its between a menubar
tag and the corresponding /menubar tag.) 6 Paste the menu into its new location.
Changing the name of a menu item or menu You can easily change the name of any menu item or menu by editing the menus.xml file.
To change the name of a menu item or menu:
1 Quit Dreamweaver. 2 Make a backup copy of the menus.xml file. 3 Open menus.xml in a text editor such as HomeSite, BBEdit, or Wordpad. (Dont open it
in Dreamweaver.) 4 If youre changing a menu item, find the appropriate menuitem tag, and change the value of its name attribute. If you are changing a menu, find the appropriate menu tag, and change the value of its name attribute. In either case, do not change the id attribute. 5 Save and close menus.xml; then start Dreamweaver again to see your changes. Changing keyboard shortcuts If the default keyboard shortcuts arent convenient for you, you can change or remove existing shortcuts or add new ones. The easiest way to do this is to use the Keyboard Shortcut Editor. (For more information, see Dreamweaver Help). However, you can also modify keyboard shortcuts directly in menus.xml if you prefer, but its much easier to make mistakes entering shortcuts in menus.xml than in the Keyboard Shortcut Editor.
To change a keyboard shortcut:
4 Look at the Keyboard Shortcut Matrix (available from the Dreamweaver Support Center) and
find a shortcut thats not being used or one that you want to reassign. If you reassign a keyboard shortcut, change it on a printed copy of the matrix for future reference. 5 If youre reassigning a keyboard shortcut, find the menu item that the shortcut is assigned to, and remove the key="shortcut" attribute from that menu item. 6 Find the menu item to assign or reassign the keyboard shortcut. 7 If the menu item already has a keyboard shortcut, find the key attribute on that line. If it doesnt already have a shortcut, add key="" anywhere between attributes inside the menuitem tag.

function getDynamicContent(){ var stringArray= new Array(); var i=0; var numItems = 4; for (i=0; i<numItems;i++) stringArray[i] = new String("My Menu Item " + i + "; id=My-MenuItem" + i + ); return stringArray; }

isCommandChecked()

Determines whether to display a check mark next to the menu item.
specifies is the only argument. Otherwise, if the arguments attribute is defined for a menuitem tag, the value of that attribute passes to the isCommandChecked() function (and to the canAcceptCommand(), receiveArguments(), and setMenuText() functions) as one or more arguments. The arguments attribute is useful for distinguishing between two menu items that call the same menu command.
Dreamweaver expects a Boolean value: true if a check mark should appear next to the menu item; false otherwise.
Example function isCommandChecked() { var bChecked = false; var cssStyle = arguments[0]; if (dw.getDocumentDOM() == null) return false; if (cssStyle == "(None)") { return dw.cssStylePalette.getSelectedStyle() == ''; } else { return dw.cssStylePalette.getSelectedStyle() == cssStyle; } return bChecked; }

receiveArguments()

Processes any arguments passed from a menu item or from the dw.runCommand() function. If it is a dynamic menu item, it processes the dynamic menu item ID.
specifies is the only argument. Otherwise, if the arguments attribute is defined for a menuitem tag, the value of that attribute passes to the receiveArguments() function (and to the canAcceptCommand(), isCommandChecked(), and setMenuText() functions) as one or more arguments. The arguments attribute is useful for distinguishing between two menu items that call the same menu command.
Example function receiveArguments() { var styleName = arguments[0]; if (styleName == "(None)") dw.getDocumentDOM('document').applyCSSStyle('',''); else dw.getDocumentDOM('document').applyCSSStyle('',styleName); }

setMenuText()

Specifies the text that should appear in the menu.

id="unique_id"

As with the initiallyVisible attribute, the initialPosition attribute applies only the first time that Dreamweaver loads the toolbar. After that, the toolbars position is saved to the registry or the Dreamweaver Preferences file. You can reset the position of the toolbar by using the dom.setToolbarPosition() function. For more information on the dom.setToolbarPosition() function, see the Dreamweaver API Reference. If you do not specify the initialPosition attribute, Dreamweaver positions the toolbar in the order that it is encountered during loading. relativeTo="toolbar_id" This attribute is required if the initialPosition attribute specifies below. Otherwise, it is ignored. Specifies the ID of the toolbar below which this toolbar should be positioned.
The toolbar tag contains include, itemref, and separator tags as well as individual item definitions such as button, combobox, dropdown, and so on. For descriptions of the item definitions that you can specify, see Toolbar item tags on page 177.

The toolbarset tag.

Example <toolbar id="MyDWedit_toolbar" label="Edit">

<include/>

Loads toolbar items from the specified file before continuing to load the current file. Toolbar items that are defined in the included file can be referenced in the current file. If a file attempts to recursively include another file, Dreamweaver displays an error message and ignores the recursive include. Any toolbar tags in the included file are skipped, although toolbar items in those toolbars are available for reference in the current file.
The file path, relative to the Toolbars folder, of the toolbar XML file to include.
The toolbar tag or the toolbarset tag.
Example <include file="mine/editbar.xml"/>

<itemtype/>

Defines a single toolbar item. Toolbar items include buttons, radio buttons, check buttons, combo boxes, pop-up menus, and so on. For a list of the types of toolbar items that you can define, see Toolbar item tags on page 177.

2 Verify the cfweather tag now appears in the Tag Chooser by performing the following steps:
Select Insert > Tag. Expand the CFML Tags group. Select the Third Party Tags group that appears at the bottom of the Tag Chooser. The cfweather tag appears in the list box on the right. Select cfweather, and click the Insert button. The tag editor should appear.

Tag editor APIs

In order to create a new tag editor, you must provide an implementation for the inspectTag(), validateTag(), and applyTag() functions. For an example of an implementation, see Creating a tag editor UI on page 212. inspectTag()
The function is called when the tag editor first appears. The function receives as an argument the tag that the user is editing, which is expressed as a dom object. The function extracts attribute values from the tag that is being edited and uses these values to initialize form elements in the tag editor.

Arguments tag

The tag argument is the DOM node of the edited tag.
Suppose the user edits the following tag:
<crfweather zip = 94065/>
If the editor contains a text field for editing the zip attribute, the function needs to initialize the form element so that the user sees the actual ZIP code in the text field, rather than an empty field. The following code performs the initialization:
function inspectTag(tag) { document.forms[0].zip.value = tag.zip }

validateTag()

When a user clicks on a node in the tree control or clicks OK, the function performs input validation on the currently displayed HTML form elements.
Dreamweaver expects a Boolean value: true if the input for HTML form elements is valid; false if input values are not valid.
When the user creates a table, a negative integer is entered for the number of table rows. The validateTag() function detects the invalid input, displays an alert message, and returns a false value.

applyTag()

When the user clicks OK, Dreamweaver calls the validateTag() function. If the validateTag() function returns a true value, Dreamweaver calls this function and passes the dom object that represents the current tag (the tag that is being edited). The function reads the values out of the form elements and writes them into the dom object.
The tag argument is the DOM node of the tag being edited.
Continuing the cfweather example, in the following code, if the user changes the ZIP code from 94065 to 53402, in order to update the users document to use the new ZIP code, the dom object must be updated:
function applyTag(tag) { tag.zip = document.forms[0].zip.value }
CHAPTER 12 Property Inspectors
The Property inspector is perhaps the most familiar floating panel in the Macromedia Dreamweaver MX 2004 interface. It is indispensable for defining, reviewing, and changing the name, size, appearance, and other attributes of the selection as well as for launching internal and external editors for the selected element. Dreamweaver has several built-in interfaces for the Property inspector that let you set properties for many standard HTML tags. These built-in inspectors are part of the core Dreamweaver code; for this reason, you cannot find corresponding Property inspector files for them in the Configuration folder. Custom Property inspector files let you override these built-in interfaces or create new ones to inspect custom tags. Custom Property inspector files are HTML files that reside in the Configuration/Inspectors folder inside the Dreamweaver application folder. Property inspector files must contain a comment (in addition to the doctype comment) immediately preceding the opening HTML tag, as shown in the following example:

<!-- tag:INTJ,priority:5,selection:exact,vline,hline --> <!DOCTYPE HTML SYSTEM "-//Macromedia//DWExtension layout-engine5.0//pi"> <HTML> <HEAD> <TITLE>Interjection Inspector</TITLE> <SCRIPT LANGUAGE="JavaScript"> function canInspectSelection(){ return true; }
function inspectSelection(){ // Get the DOM of the current document var // theDOM = dw.getDocumentDOM(); // Get the selected node var theObj = theDOM.getSelectedNode(); // Get the value of the TYPE attribute on the INTJ tag var // theType = theObj.getAttribute('type'); // Initialize a variable called typeIndex to -1. This will be // used to store the menu index that corresponds to // the value of the TYPE attribute var typeIndex = -1; // If there was a TYPE attribute if (theType){ // If the value of TYPE is "jeepers", set typeIndex to 0 if (theType.toLowerCase() == "jeepers"){ typeIndex = 0; // If the value of TYPE is "jinkies", set typeIndex to 1 }else if (theType.toLowerCase() == "jinkies"){ typeIndex = 1; // If the value of TYPE is "zoinks", set typeIndex to 2 }else if (theType.toLowerCase() == "zoinks"){ typeIndex = 2; } } // // // if } } function setInterjectionTag(){ // Get the DOM of the current document var theDOM = dw.getDocumentDOM(); // Get the selected node var theObj = theDOM.getSelectedNode(); // Get the index of the selected option in the pop-up menu // in the interface var typeIndex = document.topLayer.document. topLayerForm.intType.selectedIndex; // Get the value of the selected option in the pop-up menu // in the interface var theType = document.topLayer.document. topLayerForm.intType.options[typeIndex].value; // Set the value of the TYPE attribute to theType theObj.setAttribute('type',theType); } </SCRIPT> </HEAD> <BODY> <SPAN ID="image" STYLE="position:absolute; width:23px; height:17px; z-index:16; left: 3px; top: 2px"> <IMG SRC="interjection.gif" WIDTH="36" HEIGHT="36" If the value of the TYPE attribute was "jeepers", "jinkies", or "zoinks", choose the corresponding option from the pop-up menu in the interface (typeIndex != -1){ document.topLayer.document.topLayerForm.intType. selectedIndex = typeIndex;
NAME="interjectionImage"> </SPAN> <SPAN ID="label" STYLE="position:absolute; width:23px; height:17px; z-index:16; left: 44px; top: 5px">Interjection</SPAN> <!-- If your form fields are in different layers, you must create a separate form inside each layer and reference it as shown in the inspectSelection() and setInterjectionTag() functions above. --> <SPAN ID="topLayer" STYLE="position:absolute; z-index:1; left: 125px; top: 3px; width: 431px; height: 32px"> <FORM NAME="topLayerForm"> <TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0"> <TR> <TD VALIGN="baseline" ALIGN="right">Type:</TD> <TD VALIGN="baseline" ALIGN="right"> <SELECT NAME="intType" STYLE="width:86" onChange="setInterjectionTag()"> <OPTION VALUE="jeepers">Jeepers</OPTION> <OPTION VALUE="jinkies">Jinkies</OPTION> <OPTION VALUE="zoinks">Zoinks</OPTION> </SELECT> </TR> </TABLE> </FORM> </SPAN> </BODY> </HTML>

<closeTag>

This optional tag should be inserted at the end of the translated section. This tag enables certain other extensions, such as custom Property inspectors, to find the translation.
The tagName value is a valid tag name; it should match a translation openTag tag.
If you specify the value <closeTag>MM_DYNAMIC_CONTENT</closeTag>, the dynamic data is translated to end with the </MM_DYNAMIC_CONTENT> tag.
Server behavior techniques
This section covers the common and advanced techniques that create and edit server behaviors. Most of the suggestions involve specific settings in the EDML files. Finding server behaviors
Writing search patterns In order to update or delete server behaviors, you must provide a way for Dreamweaver to find each instance in a document. This requires a quickSearch tag and at least one searchPattern tag, which is contained within the searchPatterns tag.
The quickSearch tag should be a string, not a regular expression, that indicates that the server behavior might exist on the page. It is not case-sensitive. It should be short and unique, and it should avoid spaces and other sections that can be changed by the user. The following example shows a participant that consists of the simple ASP JavaScript tag:
<% if (Recordset1.EOF) Response.Redirect("some_url_here") %>
In the following example, the quickSearch string checks for that tag:
For performance reasons, the quickSearch pattern is the beginning of the process of finding server behavior instances. If this string is found in the document and the participant identifies a server behavior (in the group file, partType="identifier" for this participant), the related server behavior files are loaded and the findServerBehaviors() function is called. If your participant has no reliable strings for which to search (or for debugging purposes), you can leave the quickSearch string empty, as shown in the following example:
<quickSearch></quickSearch>
In this example, the server behavior is always loaded and can search the document.
Next, the searchPattern tag searches the document more precisely than the quickSearch tag and extracts parameter values from the participant code. The search patterns specify where to search (the whereToSearch attribute) with a series of searchPattern tags that contain specific patterns. These patterns can use simple strings or regular expressions. The previous example code is an ASP directive, so the whereToSearch="directive" specification and a regular expression identifies the directive and extracts the parameters, as shown in the following example:

A JSVal structure that contains the Boolean value that passes to the function as an argument. JSVal JS_IntegerToValue()
This function converts a long integer value to JSVal structure.

Arguments lv

The lv argument is the long integer value that you want to convert to a jsval structure.
A JSVal structure that contains the integer that was passed to the function as an argument. JSVal JS_ObjectToValue()
This function stores an object return value in a JSVal. Use JS_ NewArrayObject() to create an array object; use JS_SetElement() to define its contents.

Arguments JSObject *obj

The obj argument is a pointer to the JSObject object that you want to convert to a JSVal

structure.

A JSVal structure that contains the object that you passed to the function as an argument. char *JS_ObjectType()
Given an object reference, the JS_ObjectType() function returns the class name of the object. For example, if the object is a DOM object, the function returns "Document". If the object is a node in the document, the function returns "Element". For an array object, the function returns "Array".
Note: Do not modify the returned buffer pointer or you might corrupt the data structures of the JavaScript interpreter.
Typically, this argument is passed in and converted using the JS_ValueToObject() function.
A pointer to a null-terminated string. The caller should not free this string when it finishes. JSObject *JS_NewArrayObject()
This function creates a new object that contains an array of JSVals.
Arguments JSContext *cx, unsigned int length, jsval *v
The cx argument is the opaque JSContext pointer that passes to the JavaScript function. The length argument is the number of elements that the array can hold. The v argument is an optional pointer to the jsvals to be stored in the array. If the return
value is not null, v is an array that contains length elements. If the return value is null, the initial content of the array object is undefined and can be set using the JS_SetElement() function.
A pointer to a new array object or the value null upon failure. long JS_GetArrayLength()
Given a pointer to an array object, this function gets the number of elements in the array.
Arguments JSContext *cx, JSObject *obj
The cx argument is the opaque JSContext pointer that passes to the JavaScript function. The obj argument is a pointer to an array object.
The number of elements in the array or -1 upon failure.

JSBool JS_GetElement()

This function reads a single element of an array object.
Arguments JSContext *cx, JSObject *obj, unsigned int index, jsval *v
The cx argument is the opaque JSContext pointer that passes to the JavaScript function. The obj argument is a pointer to an array object. The index argument is an integer index into the array. The first element is index 0, and the

There are many cases where JavaScript extensions open files and write to the Configuration folder. JavaScript extensions can access the file system by using DWFile, MMNotes, or passing a URL to the dreamweaver.getDocumentDOM() function. When an extension accesses the file system in a Configuration folder, it generally uses the dw.getConfigurationPath() function and adds the filename, or it gets the path by accessing the dom.URL property of an open document and adding the filename. An extension can also get the path by accessing the dom.URL and stripping the filename. The dw.getConfigurationPath() function and the dom.URL property always return a URL in the Dreamweaver Configuration folder, even if the document is located in the user Configuration folder. Any time a JavaScript extension opens a file in the Dreamweaver Configuration folder, Dreamweaver intercepts the access and checks the user Configuration folder first. If a JavaScript extension saves data to disk in the Dreamweaver Configuration folder through DWFile or MMNotes, Dreamweaver intercepts the call and redirects it to the user Configuration folder. For example, in Windows 2000 or Windows XP, if the user asks for "file:///C|/Program Files/Macromedia/Dreamweaver/Configuration/Objects/Common/Table.htm", Dreamweaver searches for a Table.htm file in the C:/Documents and Settings/username/ Macromedia/Dreamweaver/Configuration/Objects/Common folder and, if it exists, uses it instead.
C-level extensions, or shared libraries, must use the File Access and Multiuser Configuration API to read and write to the Dreamweaver Configuration folder. Using the File Access and Multiuser Configuration API lets Dreamweaver read and write to the user Configuration folder and ensures that the file operations do not fail due to insufficient access privileges. If your C-level extension accesses files in the Dreamweaver Configuration folder that were created through JavaScript with DWFile, MMNotes, or DOM manipulations, it is essential that you use the File Access and Multiuser Configuration API because these files might be located in the user Configuration folder.
Note: Most JavaScript extensions do not need to be changed to write to the user Configuration folder. Only C shared libraries that write to the Configuration folder need to be updated to use the File Access and Multiuser Configuration API functions.

The Class folder

The Class folder contains the following utility functions:
classCheckbox.js FileClass.js Helps manipulate a checkbox control in your HTML extension. Contains class that represents a file in the file system. The paths are represented by URLs for cross-platform compatibility. Methods include toString(), getName(), getSimpleName(), getExtension(), getPath(), setPath(), isAbsolute(), getAbsolutePath(), getParent(), getAbsoluteParent(), exists(), getAttributes(), canRead(), canWrite(), isFile(), isFolder(), listFolder(), createFolder(), getContents(), setContents(), copyTo(), and remove(). Contains class that manages MM:TREECONTROL. Older version of the GridControlClass in the Common folder. See the GridControlClass.js file in the Shared/Common/Scripts folder. Older version of the ImageButtonClass in the Common folder. See the ImageButtonClass.js file in the Shared/Common/Scripts folder. Older version of the ListControlClass in the Common folder. See the Shared/Common/Scripts/ListControlClass.js file. Creates and manages a list of name/value pairs. Names can contain any character. Values can be blank, but cannot be set to null, which is the same as deleting them. Example of a page class to be used with the TabControl class. See TabControl class. Contains an object and methods that contain all the preference information for a command. Older version of the RadioGroupClass in the Common folder. See the RadioGroupClass.js file in the Shared/Common/Scripts folder. Helps build an extension that has multiple tab views,

page.lastUnload()

GridClass.js GridControlClass.js
ListControlClass.js NameValuePairClass.js
PageControlClass.js PreferencesClass.js RadioGroupClass.js

TabControlClass.js

The CMN folder
The CMN folder contains the following utility functions:
dateID.js Contains two functions, createDateID() and decipherDateID(). Given three strings, dayFormat, dateFormat, and timeFormat, createDateID() creates an ID for them. Given a date array, decipherDateID() returns an array with three items: the dayFormat, the dateFormat, and the timeFormat. Contains one function that displays the specified Help document. Contains functions that provide information about the users document. Operations performed by functions include returning an array of object references for a specified browser type and tag, returning all instances of a specified tag name, searching for a tag that wraps the current selection, and so on, Contains general helper functions for working with the Dreamweaver DOM. Includes functions that get the root node of the active document, find a tag of a given name, create a list of nodes from the specified starting node, check whether a given tag is contained inside another tag, perform various operations on behavior functions, and more. Contains one function, SetEnabled(), which enables or disables a control based on the arguments it receives. It is OK to enable a control that is already enabled or disable a control that is already disabled. Contains logging functions for accumulating tracing output into an array of log pages that appear in a dialog box. Contains functions pertaining to file operations. Functions let the user browse for local filename, convert the relative path to the file URL path, return filename for current document, determine if a specified document has been saved in current site and return the document-relative path, or determine if a specified file is currently open. Contains functions that add a form around a given text string if a form does not already exist in the current document or layer. Includes functions that determine if an object is a layer and determine if the cursor is inside a form. Contains functions that get a function for an event handler, add a function to an event handler, and delete a function for an event handler. Contains a handful of useful functions that replace encoding, unescape quotation marks ("), check whether a node is inside a selection range, and checks for duplicate object names.

Using the Shared folder

Look first in the Dreamweaver Configuration/Shared/Common folder for useful extension code because this folder contains the most current and commonly used functionality. Extensions can leverage the resources in the Shared folder for their own functionality. An object, command, or other extension can specify one of the JavaScript files in the Shared folder as a source file in a script tag, and then use the function in the body of the file or in another included JavaScript file. Objects and commands can even link several JavaScript files together, and those JavaScript files can leverage Shared folder resources. For example, open the Hypertext object file (Hyperlink.htm) in the application folder Configuration/Objects/Common. Notice that the head tag of the file contains the following lines:
<script language="javascript" src="././Shared/Common/Scripts/ ListControlClass.js"></script> <script language="javascript" src="Hyperlink.js"></script>
And, if you open the related Hyperlink.js file, you can see the following lines:
LIST_LINKS = new ListControl('linkPath');
LIST_TARGETS = new ListControl('linkTarget');
With the new listControl declarations, Hyperlink.js defines two new ListControl objects. The code in the Hyperlink.htm file then attaches them to the SELECT controls in the form, as follows:
<td align="left"> <input name="linkText" type="text" class="basicTextField" value="">
<td align="left" nowrap><select name="linkPath" class="basicTextField" editable="true">
Now, the Hyperlink.js script can call methods or get properties for the LIST_LINKS or LIST_TARGETS objects to interact with the SELECT controls in the form.
A action files 235 addDynamicSource() 295 alert() 68 analyzeServerBehavior() 253 APIs, types of Behaviors 237 C-level extensibility 356 Commands 136 Component panel 316 data formatting 307 Data Sources 295 Data Translator 335 Floating panel 224 Menu Commands 156 Objects 122 Property inspector 219 Reports 199 Server Behavior 253 Server Formats 310 Server Model 327 Tag editor 214 toolbar command 187 appearance of dialog boxes 32 applyBehavior() 237 applyFormat() 310 applyFormatDefinition() 310 applySB() 259 applyServerBehavior() 254 applyTag() 216 appName property 74 appVersion property 74 arguments passed from menuitem 155 receiveArguments() 159 arguments attribute 186 array object 68
attribute translators about 339 creating 340 debugging 352 sample code 341 attributes arguments 186 checked 185 colorRect 184 command 186 disabledImage 183 domRequired 184 enabled 185 file 184 id 182 image 182 label 183 menu_ID 184 overImage 183 showIf 182 toolbar item tags 182 tooltip 183 update 185 value 185 width 184 attributes property 72 attributes tag 284 B beginReporting() 199 behavior extensions, definition 22 behaviorFunction() 238 behaviors API 237 helper functions 236 inserting multiple functions with 236 required functions 237

getServerSupportsCharset() 333 getSetupSteps() 319 getTranslatedAttribute() 72 getTranslatorInfo() 336 getUpdateFrequency() 191 getVersionArray() 334 group file tags 262 group files 248 groupParticipant tag 266 groupParticipants tag 265 groupParticipants tag attributes 266 H handleDoubleClick() 322 hasChildNodes() for comment objects 74 for document objects 71 for tag objects 72 for text objects 73 hasTranslatedAttributes() 72 helper functions, in behaviors 236 hidden (field) object 68 hline 217 HTML default formatting, changing 110 inner/outer properties 72 I id attribute 117, 182 idChar1 tag, code coloring 92 idCharRest tag, code coloring 92 identifyBehaviorArguments() 240 ignoreCase tag, code coloring 92 ignoreMMTParams tag, code coloring 92 ignoreTags tag, code coloring 93 image attribute 117, 182 image object 68 include/ tag 175 initialPosition() 226 initialTabs() 226 innerHTML property 72 innerTag value, blockStart 99 innerText value, blockStart 97 Insert bar adding objects 121 definition file 114 modifying 29
Insert bar object example 126 files 113 reordering 121 Insert bar object extensions, definition 21 insertbar tag 115 insertbar.xml file 113, 121 insertObject() 123 insertText tag 269, 270 inspectBehavior() 242 inspectDynamicDataRef() 299 inspectFormatDefinition() 312 inspector extensions, definition 22 inspectServerBehavior() 257 inspectTag() 214 installing an extension 14 isATarget() 227 isAvailableInCodeView() 227 isCommandChecked() 158, 191 isDOMRequired() 192 isDomRequired() 123, 137 isLocked tag, code coloring 93 isOptional attribute 276 isResizable() 228 item tag 31 item tags, in toolbars 177 item() 68 itemref/ tag 176 itemtype/ tag 176 J JavaScript controls 55 external files 26 URLs 26 JS_BooleanToValue() 360 JS_DefineFunction() 356 JS_DoubleToValue() 359 JS_ExecuteScript() 363 JS_GetArrayLength() 361 JS_GetElement() 362 JS_IntegerToValue() 360 JS_NewArrayObject() 361 JS_ObjectToValue() 360 JS_ObjectType() 360 JS_ReportError() 363 JS_SetElement() 362 JS_StringToValue() 359 JS_ValueToBoolean() 358 JS_ValueToDouble() 358
JS_ValueToInteger() 357 JS_ValueToObject() 358 JS_ValueToString() 357 JSBool 355 JSContext 355 JSNative 356 JSObject 355 jsval 355 K keyboard shortcuts, changing 152 keyword tag, code coloring 93 keywords tag, code coloring 94 L label attribute 183 language information 74 layer object 68 limitSearch attribute 276, 283 liveDataTranslateMarkup() 338 localized strings 45 location attribute 270 locked content, inspecting 349 *LOCKED* keyword 349 M manipulating tree control content 62 math object 68 menu command extensions, definition 21 menu commands about 154 sample code 161 user experience 155 Menu Commands API canAcceptCommand() 156 commandButtons() 156 getDynamicContent() 157 isCommandChecked() 158 receiveArguments() 159 setMenuText() 159 windowDimensions() 160 menu folder, placing command file 164 menu tag 80, 147 MENU-LOCATION 252 menu_ID attribute 184 menubar tag 146 menubutton tag 116, 179 menugroup tag 79 menuitem tag 81, 147