Specifications

C-Level Extensibility 261
Dreamweaver MX creates the user configuration folder in a location where the user has full read
and write access. The following table shows the specific location of the user configuration folder
for each of the supported platforms:
There are many cases where JavaScript extensions open files and write to the configuration folder.
JavaScript extensions can access the file system by using DWFile, MMNotes, or passing a URL to
dw.getDocumentDOM(). When an extension accesses the file system in a configuration folder, it
generally uses
dw.getConfigurationPath() and adds the filename, or it gets the path by
accessing the
dom.URL of an open document and adding the filename. An extension can also get
the path by accessing the
dom.URL and stripping the filename. The
dw.getConfigurationPath() function and the dom.URL always return a URL in the
Dreamweaver MX configuration folder, even if the document is located in the user configuration
folder.
Any time a JavaScript extension opens a file in the Dreamweaver MX configuration folder
Dreamweaver MX traps the access and checks the user configuration folder first. If a JavaScript
extension saves data to disk in the Dreamweaver MX configuration folder through DWFile or
MMNotes, Dreamweaver MX intercepts the call and redirects it to the user configuration folder.
For example, in Windows 2000 or Windows XP, if the user asks for "
file:///C|/Program
Files/Macromedia/Dreamweaver MX/Configuration/Objects/Common/Table.htm
",
Dreamweaver MX first looks to see if there is a file called file:///C|/Documents and Settings/
username/Macromedia/Dreamweaver MX/Configuration/Objects/Common/Table.htm and, if it
exists, uses it instead.
C-level extensions, or shared libraries, must use the File Access and Multiuser Configuration API
to read and write to the configuration folder. Using the File Access and Multiuser Configuration
API lets Dreamweaver read and write to the user configuration folder and ensures that the file
operations do not fail due to insufficient access privileges. If your C-level extension accesses files
in the configuration folder that were created through JavaScript with DWFile, MMNotes, or
DOM manipulations, it is essential that you use the File Access and Multiuser Configuration API
because these files might be located in the user configuration folder.
Note: Most JavaScript extensions will not need to be changed to write to the user Configuration folder. Only C
shared libraries that write to the Configuration folder need to be updated to use the File Access and Multiuser
Configuration API functions.
When you delete a file from Dreamweaver Configuration folder, Dreamweaver MX adds an entry
to a mask file to indicate which files in the Configuration folder should not appear in the user
interface. A masked file or folder will appear not to exist to Dreamweaver although it might
physically exist in the folder.
Platform User Configuration Folder
Macintosh OS X
MacHD:Users:username:Library:Application Support:Macromedia: ¬
Dreamweaver MX:Configuration
Windows 2000,
Windows XP
C:\Documents and Settings\
username\Application Data\Macromedia\ ¬
Dreamweaver MX\Configuration
Windows NT C:\WinNT\profiles\
username\Application Data\Macromedia\ ¬
Dreamweaver MX\Configuration