Adobe 38040334 - Dreamweaver CS3 User Manual page 327

Note: The Default Page Extension list exists only in Dreamweaver 4 and earlier. For Dreamweaver MX, and later, the
Site Definition dialog box does not list file extension settings. Instead, Dreamweaver reads the Extensions.txt file and
parses the element in the mmDocumentTypes.xml file. (For more information on these two files and the
documenttype
element, see "Extensible document types in Dreamweaver" on page 15.)
documenttype
Arguments
None.
Returns
Dreamweaver expects an array of strings that represent the allowed file extensions.
getLanguageSignatures()
Availability
Dreamweaver MX.
Description
This function returns an object that describes the method and array signatures that the scripting language uses. The
getLanguageSignatures()
following elements:
• The function
• Constructors
• Drop code (return values)
• Arrays
• Exceptions
• Data type mappings for primitive data types
The
getLanguageSignatures()
use this map to generate language-specific code blocks that Dreamweaver drops on the page (based on the appro-
priate server model for the page) when the user drags and drops a Web Services method, for example.
For examples of how to write this function, see the HTML implementation files for the JSP and the ASP.Net server
models. Server model implementation files are located in the Configuration/ServerModels folder.
Arguments
None.
Returns
Dreamweaver expects an object that defines the scripting language signatures. This object should map the generic
signatures to language-specific ones.
getServerExtension()
Availability
Dreamweaver UltraDev 4, deprecated in Dreamweaver MX.
function helps map generic signature mapping to language-specific mapping for the
function returns a map of these signature declarations. Extension developers can
DREAMWEAVER CS3 321
Extending Dreamweaver