Customizing Dreamweaver
537
Editing Dreamweaver commands
All the commands in Dreamweaver menus, including those you create and save
using the History panel (see “Creating new commands from history steps” on
page 165), are implemented in JavaScript. This JavaScript code usually consists
mostly of calls to functions provided by the Dreamweaver extensibility API. If you
know JavaScript and understand the Dreamweaver extensibility API, you can edit
the JavaScript to change the operation of Dreamweaver commands.
Note:
Don’t attempt to change any JavaScript code unless you’re certain you know what
you’re doing. Even if you do know what you’re doing, make a backup copy of the file
containing the code before you modify it.
To rename a command, move a command to a different menu, or add a keyboard
shortcut to a command, see “About customizing Dreamweaver menus” on page 517.
Customizing the interpretation of
third-party tags
Server-side processing technologies such as ASP, ColdFusion, JSP, and PHP use
special non-HTML code in HTML files; servers create and serve HTML content
based on that code. When Dreamweaver encounters non-HTML tags, it
compares them with information in its third-party tag files, which define how
Dreamweaver reads and displays non-HTML tags.
For example, ASP files contain—in addition to regular HTML—ASP code for the
server to interpret. ASP code looks something like a tag, but is marked by a pair of
delimiters: it begins with
<%
and ends with
%>
. The Dreamweaver Configuration/
ThirdPartyTags folder contains a file named ASP.xml, which describes the format
of ASP code and defines how Dreamweaver displays that code. Because of the way
ASP code is specified in ASP.xml, Dreamweaver doesn’t try to interpret anything
between the delimiters; instead, in the Design view of the Document window, it
simply displays an icon indicating ASP code.
You can define your own tags and create tag database files that define how
Dreamweaver reads and displays your tags. Creating tag database files is
particularly useful if you’re using a server-side markup system other than ASP, JSP,
ColdFusion, or PHP; create a new tag database file for each such markup system,
to tell Dreamweaver how to display the tags. (There is no separate JSP tag
database file; JSP code uses the same delimiters as ASP code, so Dreamweaver uses
the ASP tag database file for JSP.)
Note:
This section explains how to define the way Dreamweaver displays a custom tag, but
doesn’t describe how to provide a way to edit the content or properties of a custom tag. For
information on how to create a Property inspector to inspect and change the properties of
a custom tag, see “Property Inspectors” in
Extending Dreamweaver
.
Summary of Contents for 38028779 - Macromedia Dreamweaver - Mac
Page 1: ...macromedia Using Dreamweaver...
Page 148: ...Chapter 4 148...
Page 296: ...Chapter 12 296...
Page 472: ...Chapter 18 472...
Page 512: ...Chapter 21 512...
Page 562: ...Appendix 562...
