MACROMEDIA DREAMWEAVER MX 2004-EXTENDING DREAMWEAVER Spécifications Page 425

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 504
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 424
The Server Model API functions 425
getFileExtensions()
Availability
Dreamweaver UltraDev 1, deprecated in Dreamweaver MX.
Description
Returns the document file extensions with which a server model can work. For example, the
ASP server model supports .asp and .htm file extensions. This function returns an array of
strings, and Dreamweaver uses these strings to populate the Default Page Extension list that is
found in the App Server category in the Site Definition dialog box.
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() function helps map generic
signature mapping to language-specific mapping for the following elements:
The function
Constructors
Drop code (return values)
Arrays
Exceptions
Data type mappings for primitive data types
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
documenttype 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 35.)
Vue de la page 424
1 2 ... 420 421 422 423 424 425 426 427 428 429 430 ... 503 504

Commentaires sur ces manuels

Pas de commentaire