Home » Adobe Manuals » Computer Software » Adobe 38040334 » Manual Viewer

Adobe 38040334 API Reference - Page 251

dom.showInfoMessagePopup, Returns, Example, Availability, Description

UPC - 883919090467

Add to My Manuals
Save this manual to your list of manuals

Page 251 highlights

DREAMWEAVER CS3 246 API Reference • If the argument is an empty string, the Validator performs a default validation. If the argument is "xml", the Validator validates the document as XML. • If the argument is "auto-explicit" or "auto-implicit", Dreamweaver performs an automatic validation (also known as an inline validation), which underlines errors in the Code view instead of opening the Validation results window (see "dom.source.getValidationErrorsForOffset()" on page 422 and "dom.getAutoValidationCount()" on page 416). • If the controlString argument is "auto-explicit", Dreamweaver prompts the user to save an unsaved document before running the validation. • If the controlString argument is "auto-implicit", the validation fails without notifying the user that the current document is unsaved. Note: An automatic validation (that the controlString value "auto-explicit" or "auto-implicit" defines) is currently available only for a browser compatibility check. • The bOpenResultsWindow argument is an optional Boolean value: true opens the Validation results window; false otherwise. The default value is true. • The bShowInfoMessage argument is used only when the controlString argument is defined as "auto- explicit" or "auto-implicit". The bShowInfoMessage argument is a Boolean value: true shows an informational message under the toolbar item, DW_ValidatorErrors, with the number of errors found; false displays nothing. The default value is false. Returns The Validation results window object. Example The following example runs a regular validation when the user selects the File > Check Page > Validate Markup menu option (or Validate Current Document in the Validation panel): dw.getDocumentDOM().runValidation(''); The following example prompts the user to save an unsaved document, runs an automatic validation, does not open the Validation results window, but does show the total number of errors over the document toolbar button for DW_ValidatorErrors: dw.getDocumentDOM().runValidation('auto-explicit', false, true); The following example does not prompt the user to save an unsaved document. If the document has not been saved, the validation will not start. If the document has been saved, Dreamweaver runs an automatic validation, does not open the Validation results window, and does not indicate the total number of errors encountered on the document toolbar: dw.getDocumentDOM().runValidation('auto-implicit', false); dom.showInfoMessagePopup() Availability Dreamweaver MX 2004. Description Shows a tooltip-like message in the document window or under a toolbar item.

Section	Page
Contents	3
Chapter 1: Introduction	6
Background	7
Extending Dreamweaver	7
Additional resources for extension writers	7
New functions in Dreamweaver CS3	7
Removed functions	9
Errata	10
Conventions used in this guide	10
Chapter 2: The file I/O API	11
Accessing configuration folders	11
The file I/O API	11
Chapter 3: The HTTP API	20
How the HTTP API works	20
The HTTP API	21
Chapter 4: The Design Notes API	27
How Design Notes work	27
The Design Notes JavaScript API	28
The Design Notes C API	32
Chapter 5: Fireworks integration	39
The FWLaunch API	39
Chapter 6: Flash integration	46
How Flash elements work	46
Inserting Flash elements	46
The Flash Objects API	47
Chapter 7: The database API	51
How database API functions work	51
Database connection functions	52
Database access functions	64
Chapter 8: The database connectivity API	76
How to develop a new connection type	76
The Connection API	78
The generated include file	80
The definition file for your connection type	82
Chapter 9: The JavaBeans API	84
The JavaBeans API	84
Chapter 10: The source control integration API	89
How source control integration with Dreamweaver works	90
Adding source control system functionality	90
The source control integration API required functions	90
The source control integration API optional functions	96
Enablers	104
Chapter 11: Application	109
External application functions	109
Global application functions	117
Bridge communication functions	122
Chapter 12: Workspace	124
History functions	124
Insert object functions	132
Keyboard functions	135
Menu functions	141
Results window functions	143
Toggle functions	154
Toolbar functions	173
Window functions	178
Code collapse functions	188
Code view toolbar functions	194
Chapter 13: Site	198
Report functions	198
Site functions	199
Chapter 14: Document	232
Conversion functions	232
Command functions	233
File manipulation functions	235
Global document functions	249
Path functions	258
Selection functions	260
String manipulation functions	267
Translation functions	270
XSLT functions	272
Chapter 15: Page content	275
Assets panel functions	275
Behavior functions	285
Clipboard functions	293
Library and template functions	298
Snippets panel functions	303
Spry widget editing functions	306
Inserting Spry widgets functions	308
Browser compatibility check functions	311
Chapter 16: Dynamic documents	319
Server components functions	319
Data source functions	320
Extension Data Manager functions	321
Live data functions	324
Server behavior functions	328
Server model functions	330
Chapter 17: Design	337
CSS layout functions	337
Frame and frameset functions	356
Layer and image map functions	358
Layout environment functions	360
Layout view functions	365
Zoom functions	374
Guide functions and properties	377
Table editing functions	384
Chapter 18: Code	393
Code functions	393
Find and replace functions	397
General editing functions	402
Print function	417
Quick Tag Editor functions	418
Code view functions	420
Tag editor and tag library functions	436
Chapter 19: Enablers	440
Enabler functions	440

Match case Limit results 1 per page

DREAMWEAVER CS3

API Reference

246

•

If the argument is an empty string, the Validator performs a default validation. If the argument is

"xml"

, the

Validator validates the document as XML.

•

If the argument is

"auto-explicit"

"auto-implicit"

, Dreamweaver performs an automatic validation

(also known as an

inline

validation), which underlines errors in the Code view instead of opening the Validation

results window (see

“dom.source.getValidationErrorsForOffset()” on page 422

and

“dom.getAutoValidation-

Count()” on page 416

•

If the

controlString

argument is

"auto-explicit"

, Dreamweaver prompts the user to save an unsaved

document before running the validation.

•

If the

controlString

argument is

"auto-implicit"

, the validation fails without notifying the user that the

current document is unsaved.

Note:

An automatic validation (that the

controlString

value

"auto-explicit"

"auto-implicit"

defines) is

currently available only for a browser compatibility check.

•

The

bOpenResultsWindow

argument is an optional Boolean value:

true

opens the Validation results window;

false otherwise. The default value is

true

•

The

bShowInfoMessage

argument is used only when the

controlString

argument is defined as

"auto-

explicit"

"auto-implicit"

. The

bShowInfoMessage

argument is a Boolean value:

true

shows an infor-

mational message under the toolbar item,

DW_ValidatorErrors

, with the number of errors found;

false

displays nothing. The default value is

false

Returns

The Validation results window object.

Example

The following example runs a regular validation when the user selects the File > Check Page > Validate Markup menu

option (or Validate Current Document in the Validation panel):

dw.getDocumentDOM().runValidation('');

The following example prompts the user to save an unsaved document, runs an automatic validation, does not open

the Validation results window, but does show the total number of errors over the document toolbar button for

DW_ValidatorErrors:

dw.getDocumentDOM().runValidation('auto-explicit', false, true);

The following example does not prompt the user to save an unsaved document. If the document has not been saved,

the validation will not start. If the document has been saved, Dreamweaver runs an automatic validation, does not

open the Validation results window, and does not indicate the total number of errors encountered on the document

toolbar:

dw.getDocumentDOM().runValidation('auto-implicit', false);

dom.showInfoMessagePopup()

Availability

Dreamweaver MX 2004.

Description

Shows a tooltip-like message in the document window or under a toolbar item.