How Property Inspector Files Work - Adobe 38040334 - Dreamweaver CS3 User Manual

• The element specifies that Dreamweaver should load this Property inspector only when the server
serverModel
model specified is active.
• The
tagNameOrKeyword
comments),
*LOCKED*
• The element is the priority of the Property inspector file:
1to10
when no others can inspect the selection;
inspect the selection.
• The
element indicates whether the selection can be within the tag (
exactOrWithin
contain the tag ( ).
exact
• The
element (optional) indicates that a horizontal gray line should appear between the upper and lower
hline
halves of the inspector in expanded mode.
• The element (optional) indicates that a vertical gray line should appear between the tag name field and the
vline
rest of the properties in the inspector.
• The
element (optional) indicates the server model of the Property inspector. If the server model of
serverModel
the Property inspector is not the same as the server model for the document, Dreamweaver does not use the
Property inspector to display the properties of the current selection. For example, if the server model of the
document is Macromedia ColdFusion, but the server model of the Property inspector is ASP, Dreamweaver does
not use that Property inspector for selections in the document.
The following comment is appropriate for an inspector that is designed to inspect the
<!-- tag:happy, priority:8,selection:exact,hline,vline,serverModel:ASP -->
In some cases, you might want to specify that your extension uses only Dreamweaver extension rendering (and not
the previous rendering engine) by inserting the following line immediately before the tag comment, as shown in the
following example:
<!--DOCTYPE HTML SYSTEM "-//Macromedia//DWExtension layout-engine 5.0//pi"-->
The body section of a Property inspector file contains an HTML form. Instead of displaying the form contents in a
dialog box, however, Dreamweaver uses the form to define the input areas and layout of the Property inspector.
The head section of a Property inspector file contains JavaScript functions or a reference to the JavaScript file or files.

How Property inspector files work

At start-up, Dreamweaver reads the first line of each HTM and HTML file in the Configuration/Inspectors folder,
searching for the comment string that defines the type, priority, and selection type of a Property inspector. Files that
do not have this comment as their first line are ignored.
When the user makes a selection in Dreamweaver or moves the insertion point to a different location, the following
events occur:
Dreamweaver searches for any inspectors that have a
1
2 If there are any
within
to check whether there are inspectors for any tags that surround the selection. If there are no
Dreamweaver searches for any inspectors that have a selection type of
element is the tag to be inspected or one of the following keywords:
(for locked regions), or
*ASP*
indicates that this inspector takes precedence over all others that can
10
inspectors, Dreamweaver searches up the document tree from the currently selected tag
(for tags).
ASP
indicates that this inspector should be used only
1
selection type.
within
.
exact
DREAMWEAVER CS3
Extending Dreamweaver
(for
*COMMENT*
) or must exactly
within
tag:
happy
inspectors,
within
211