Using Custom Ui Controls In Extensions - MACROMEDIA DREAMWEAVER 8-EXTENDING DREAMWEAVER Manual

In most cases,
DOCTYPE
conflicts with extension-specific directives that, in previous versions, were required to be on
the first line of a file (such as the comment at the top of a Property inspector file, or the
directive in a command),
LOCATION=NONE
any order as long as they appear before the opening
In addition to letting you make extension UIs more closely match the built-in dialog boxes
and panels, the new
DOCTYPE
Dreamweaver Design view so that you can see them as they would appear when viewed by
users.
The following examples show the Base Property inspector without the
which improves form-control rendering, and then with the
The Base Property inspector as it appears in Design view without the
The Base Property inspector as it appears in Design view with the
few adjustments to accommodate the new rendering).

Using custom UI controls in extensions

In addition to the standard HTML form elements, Dreamweaver supports custom controls to
help you create flexible, professional-looking interfaces, as described in the following list:
Editable select lists (also known as combo boxes) that let you combine the functionality of
a select list with that of a text box
Database controls that facilitate the display of data hierarchies and fields
Tree controls that organize information into expandable and collapsible nodes
Color button controls that let you add color picker interfaces to your extensions
statements must go on the first line of a document. However, to avoid
DOCTYPE
statements also let you view your extensions in the
statements and directives can now be in
tag.
html
DOCTYPE
statement.
DOCTYPE
DOCTYPE
statement (and after a
DOCTYPE
Using custom UI controls in extensions
MENU-
statement,
statement.
113