A list of file extensions recognized by Dreamweaver.

If you add an extension to this file, double-clicking a file with that extension in the Site window opens it in Dreamweaver.

Extensions.txt also determines what file types are shown in the File > Open dialog box. To show files of a particular type in that dialog box by default, add the appropriate extension to the first line of Extensions.txt. For more information, see "Customizing Dreamweaver" in Using Dreamweaver.

A list of file extensions and the transfer modes associated with them.

This file determines how files are uploaded and downloaded by Dreamweaver: in ASCII mode or Binary mode. You can add items to this list or change the mode of existing items. On the Macintosh, this file is also used to set the file type and creator of files that are downloaded from a non-Macintosh server.

HTML Format preferences reside in this file. Any changes you make to the HTML Format preferences (Edit > Preferences) are saved in this file when you close the Preferences dialog box. For finer control over HTML source formatting, you can edit this file directly. For more information about editing SourceFormat.txt, see "Customizing Dreamweaver" in Using Dreamweaver.

CFML and JSP tag formatting preferences also reside in this file. Add tag definitions to this file when you write server behaviors that insert custom tags into the user's document. Tag declarations should follow the Dreamweaver UltraDev syntax for tags:

<[tag name] [element information] [format options]>

For example, <jsp:setProperty break="1,0,0,1" namecase="jsp:setProperty">.

A list of tags and their attributes. Used by the Quick Tag Editor and the Find and Replace dialog boxes.

To make custom tags and attributes appear in the Quick Tag Editor or Find and Replace dialog boxes, add them to this file.

The following Attribute Flags have been defined for use in the TagAttributeList.txt file to define behavior of the Property Inspector List View.

Most of the flags are used for specifying which "convenience" buttons are placed next to an attribute.

Format

The format for specifying the attribute flags is a follows. Please see file for how to specify an attribute.

attribute-name "[" flags "]"

where:

"attribute-name" is the name of an attribute
flags = flags "," flag, OR
flag

flag = "FileBrowse", OR
"PointAndShoot", OR
"ColorPicker", OR
"QueryString", OR
"NoDynamicData", OR
"Event", OR
"Default"

The IMG tag entry from the TagAttributeList.txt file is shown
as an examples:

<!ELEMENT IMG name="Image" >
<!ATTLIST IMG
Align ( left | right | top | middle | bottom | center )
Alt
Border
Controls
DynSrc
Height
HSpace
ISMap
Loop
LowSrc [ FileBrowse , NoDynamicData , PointAndShoot ]
Name
onAbort [ Event ]
onAfterUpdate [ Event ]
onBeforeUpdate [ Event ]
onBlur [ Event ]
onClick [ Event ]
onDblClick [ Event ]
onError [ Event ]
onFocus [ Event ]
onHelp [ Event ]
onLoad [ Event ]
onMouseDown [ Event ]
onMouseMove [ Event ]
onMouseOut [ Event ]
onMouseOver [ Event ]
onMouseUp [ Event ]
onReadyStateChange [ Event ]
Src [ FileBrowse , NoDynamicData , PointAndShoot , Default ]
Start
UseMap
VRML
VSpace
Width
Class
ID
Style
Title
>

NOTE: The spaces between the "[", "]", and "," separators and the flags are required to simplify parsing of this file.

Items that appear in the Actions (+) pop-up menu in the Behavior inspector.

Each action is separated into two files (one .js file and one .htm file) for localization purposes. The HTML file contains the interface for the behavior: the text and form fields that appear in a dialog box when you select the action from the Actions pop-up menu. You can modify this file to make the form fields larger or smaller. The JavaScript file contains the JavaScript code that inserts the behavior into your document. Do not make changes to this file, unless you are proficient in JavaScript and familiar with the Behavior API as documented in Extending Dreamweaver and Dreamweaver UltraDev.

Items that appear in the Events For pop-up menu at the top of the Behavior inspector.

Each file is named for the browser or browsers it represents, and it contains a list of HTML elements and the events that are supported for each element by all of the browsers in the file name. For example, Microsoft Internet Explorer (IE) 3.0 supports the onMouseMove and onMouseOver events for the A tag, while Netscape Navigator 3.0 supports the onClick, onMouseOut, and onMouseOver events. The 3.0 and Later Browsers.htm file lists only onMouseOver for the A tag because it is the only event supported for that tag by both IE 3.0 and Netscape 3.0.

For each element, one event is marked with an asterisk (for example, onClick="*"). This is the default event for the element. Unless otherwise specified in an action file, this event appears in the Events column of the Behavior inspector when you apply a behavior to the element. For example, onClick is the default event for the A tag in the Netscape 3.0.htm file. If you select a link in the Document window, choose Netscape 3.0 from the Events For pop-up menu in the Behavior inspector, and choose Call JavaScript from the Actions pop-up menu, onClick appears automatically in the Events column when you click OK in the dialog box. If you would rather make onMouseOver the default event for links in Netscape 3.0, move the asterisk from onClick to onMouseOver in the Netscape 3.0.htm file.

Files used by the Check Target Browsers feature.

Each file in this folder is named for the browser it represents, and it contains information about the tags that are and are not supported by that browser. For more information about browser profiles, see "Customizing Dreamweaver" in Using Dreamweaver.

Files used to read JavaBeans as data sources.

Items that appear in the Commands menu (and other menus within Dreamweaver).

Many of the commands in this folder are separated into two files (one .js file and one .htm file) for localization purposes. The HTML file contains the interface for the command: the text and form fields that appear in a dialog box when you select the command from the menu. You can modify this file to make the form fields larger or smaller. The JavaScript file contains the JavaScript code that makes the command work; do not make changes to this file unless you are proficient in JavaScript.

You may notice that some of the items in the Commands folder have the same names as some of the items in the Objects folder. This is because some objects launch commands. Commands are more flexible than objects, but only objects can appear in the Object panel. By calling a command from an object file, Dreamweaver can get the best of both kinds of extensions.

Dreamweaver UltraDev uses the connections defined here to connect to a database or other data source.

The files used by the Dynamic Data dialog box and the Data Bindings inspector.

The dynamic data objects shown in the plus (+) popup menu of these user interfaces are based on the server model specified for the site. For more information about editing Data Sources files, see "The Data Sources API" in the Extending Dreamweaver and Dreamweaver UltraDev in the help system.

Note: The file "menus.xml" in the Menus folder contains the definition of what appears in the plus (+) menu.

Files associated with the ASP data source.

Files associated with the JSP data source.

The dictionaries used by the Check Spelling feature.

Additional dictionaries can be downloaded from the Macromedia Web site at http://www.macromedia.com/support/dreamweaver/dictionary.html.

Additional character encodings for Dreamweaver; used to populate the Document Encoding pop-up menu in the Page Properties dialog box.

Dreamweaver supports several encodings by default, including Western (Latin1), Japanese (Shift JIS, JIS, EUC), Traditional Chinese, Simplified Chinese, and Korean. These encodings always appear in the Document Encoding pop-up menu and cannot be removed. Support for additional languages and character sets (including Cyrillic, Greek, and Icelandic) is provided by the files in this folder.

XML metadata: Group and Participant data for extensions, including server behaviors.

XML Group and Participant extension data files that ship with Dreamweaver UltraDev.

The files used to create new Flash Objects. Flash Button and Flash Text features are built using this API.

Flash button template files.

Flash button previews of template files.

Flash text template file.

Custom floating panels.

If you create or download a custom floating panel, it should be stored in this folder.

Files required for using Flash Objects inside Dreamweaver, including a custom Generator object for integration with Dreamweaver.

Custom property inspectors.

Most of the property inspectors in Dreamweaver are hard-coded into the product. The inspectors for items in the HEAD (such as META, TITLE, and LINK tags), however, are custom inspectors written in HTML and JavaScript. The property inspectors in this folder are separated into two files (one .js file and one .htm file) for localization purposes. The HTML file contains the interface for the inspector: the text and form fields that appear in the Property inspector floating panel. The JavaScript file contains the JavaScript code that makes the inspector work; do not make changes to this file unless you are proficient in JavaScript and familiar with the Property inspector API as documented in Extending Dreamweaver and Dreamweaver UltraDev.

Custom shared libraries.

The custom shared libraries in this folder make Dreamweaver's extensions more powerful and flexible by adding new JavaScript functions. Because some of the files in the Translators and Commands files depend on these shared libraries, they should not be removed. To add your own shared libraries to Dreamweaver, see the section on C-level extensibility in Extending Dreamweaver and Dreamweaver UltraDev.

The file that defines the entire menu structure for Dreamweaver (menus.xml), and a backup copy of that file (menus.bak) to allow you to restore default menus.

The menus.xml file specifies the names and behavior of all menus and menu items in Dreamweaver. It also specifies all of the keyboard shortcuts and mnemonics used by Dreamweaver. For information about menus.xml, see "Customizing Dreamweaver" in Using Dreamweaver. For a list of keyboard shortcuts, see "Keyboard Shortcuts" in Using Dreamweaver.

To add your own menu commands, create a separate folder inside Menus and store your menu command files there. For more information about creating menu commands, see the Menu commands section of Extending Dreamweaver and Dreamweaver UltraDev.

Customizations of the menu.xml file that provide keyboard shortcuts similar to other products.

Files (called menu commands) that control the behavior of many of the menu items in Dreamweaver.

This folder is reserved for the menu commands that ship with Dreamweaver.

Items that appear in the Insert menu and Object panel.

To appear in the Object panel or Insert menu, all object files must be stored in a subfolder of the Objects folder. All of the objects in these subfolders are split into at least two files (an .htm file and a .gif file), and in some cases three (a .js file as well). The GIF file is the icon that appears in the Object panel. The HTML file contains the interface for the object: the text and form fields that appear in a dialog box (if necessary) when you select an object from the menu or panel. The TITLE tag in the HTML file determines the name that appears in the Insert menu and Object panel. The JavaScript file (or the HTML file if no .js file exists) contains the JavaScript code that inserts the object into your document. You can modify the HTML file to make the form fields larger or smaller, but do not make changes to the JavaScript unless you are proficient in JavaScript and familiar with the Object API as documented in Extending Dreamweaver and Dreamweaver UltraDev.

Items that appear in the Characters category of the Object panel.

Extensions installed using the Extension Manager.

This folder is for installed extensions. To install an extension, first save the extension package file (*.mxp) in the Dreamweaver UltraDev 4/Downloaded Extensions folder (which is at the same level as the Configuration folder). Then, launch the Extension Manager directly from Dreamweaver by choosing Manage Extensions from the Commands menu. In the Extension Manager, select File -> Install Extension (Ctrl-I). Extension Manager installs the extension file in this Configuration/Extensions folder.

A list of plugins that Dreamweaver does not support (UnsupportedPlugins.txt), plus any plugins that are to be used to play plugin content in Dreamweaver.

Dreamweaver automatically scans the plugins folders of any browsers on your hard drive for a suitable plugin when you opt to play plugin content, so storing plugins in this folder is not strictly necessary.

Search patterns that you save in the Find or Replace dialog box. By default, this folder is empty.

O'Reilly HTML Reference material that appears on the Dreamweaver Reference panel.

Extension for Dreamweaver reports.

Server Behaviors

The files used by the Server Behaviors inspector.

Server behaviors create the functionality that Web applications need, such as filtering records based on user criteria, paging through records, linking result lists to details pages, and inserting records into a result set. For more information about editing Server Behaviors files, see "The Server Behavior API" in Extending Dreamweaver and Dreamweaver UltraDev.

Note: The file "menus.xml" in the Menus folder contains the definition of what appears in the plus (+) menu.

Files associated with the ASP server behaviors.

Files associated with the JSP server behaviors.

Server Formats

The files used to format dynamic data. The file "Formats.xml" defines the Formats menu, and can be (carefully) hand edited.

Users can change the format of the dynamic data before using it in an HTML document using the Format pop-up menu in the Dynamic Data dialog box or Data Bindings inspector. If users wants to create a format, they can choose the Edit Format List item from the Format menu, then choose a format type from the plus (+) menu. The plus (+) menu of the Edit Format List dialog box contains a list of format types. Format types are basic categories of formats, such as, Currency, DateTime, or AlphaCase. Format types collect all common parameters for a category of format, allowing you to streamline the work you'd have to do to create a new format
For more information about editing Server Formats files, see "The Data Formatting API" in Extending Dreamweaver and Dreamweaver UltraDev.

Files associated with the ASP server formatting.

Files associated with the JSP server formatting.

The files that define available server models.

Identifies and describes the server technologies supported in UltraDev. Each server technology must fully support the Server API. The server models files have functions to retrieve the supported scripting languages, file extensions, and version name and number mappings of a specific server model.
For more information about editing Server Model files, see "The Server Model API" in Extending Dreamweaver and Dreamweaver UltraDev.

Shared

Files to be shared by multiple extensions.

This folder is reserved for the shared files that ship with Dreamweaver, but any extension can reference the files in this folder. To add your own shared files, create a separate folder inside Shared and store your files there.

Note: The contents of this folder may change in future versions of Dreamweaver.

Controls used to build a Server Behavior. These controls include interfaces for text and recordset menus.

The shared scripts, images, and classes used by the extensions that ship with Dreamweaver.

The shared scripts, images, and classes used by the extensions that ship with Dreamweaver UltraDev.

Files that contain lists of all incoming and outgoing links for the files in defined sites.

This folder is created the first time you use a site. By default, this folder is empty. It remains empty until you define a site and create a cache file.

Source control settings and scripts.

If you write an extension to integrate Dreamweaver with a new source control system, you place your C-level DLL/shared code in this folder. There is a minimum set of API functions that you must support. For more information, see "The Source Control API" in Extending Dreamweaver and Dreamweaver UltraDev.

Scripts that run when Dreamweaver starts up.

For more information on creating startup scripts, see "The Document Object Model" in Extending Dreamweaver and Dreamweaver UltraDev.

The file default.html is used to define the starting contents for new pages opened in Dreamweaver.

Files that define the syntax and tag names of third-party markup (such as ASP, PHP, and custom HTML).

Third-party tag definition files are XML files. Each XML file contains one or more tagspecs, and each tagspec may have an associated GIF file that defines the icon for the markup. For more information about third-party tags and tagspecs, see "Customizing Dreamweaver" in Using Dreamweaver.

Extension files that translate the visual appearance of specific markup text.

Do not edit the files in this folder unless you are proficient in JavaScript and familiar with the Data translator API as documented in Extending Dreamweaver and Dreamweaver UltraDev.