Mac os x platforms use the following location drive: Users/username/Library/Application Support/Macromedia/ Dreamweaver 8/ To install extensions that all users can use in a multiuser operating system, you must be logged in as Administrator(Windows )or root(Mac OS X) The first time you run Dreamweaver, it copies only some of the configuration files into your user Configuration folder. (The files that it copies are specified in the version. xml file in the Configuration folder. )When you customize Dreamweaver from within the application(for example, when you modify one of the predesigned code snippets in the Snippets panel), Dreamweaver copies the relevant files into your user Configuration folder. The version of a file in your user Configuration folder always takes precedence over the version in the Dreamweaver Configuration folder. To customize a configuration file that Dreamweaver d into your user Configuration folder, first copy the file from the Di reainweaver Configuration folder to the corresponding location inside your user Configuration folder. Then edit the copy in your user Configuration folder. Deleting configuration files in a multiuser environment When working in a multiuser operating system, if you do something within Dreamweaver that would delete a configuration file( for example, deleting a predesigned snippet from the Snippets panel), Dreamweaver creates a file in your user Configuration folder called mm deleted files. xml. When a file is listed in mm deleted files. xml. Dreamweaver behaves as if that file doesn't exist To deactivate a confiquration file 2. Using a text editor, edit mm_deleted_files. xml in your user Configuration folder; add an item tag to that file, giving the path(relative to the Dreamweaver Configuration folder)of the configuration file to deactivate. Do not edit mm deleted files. xml in Dreamweaver. 3. Save and close mm deleted files. xml 4. Start Dreamweaver again. 28 Customizing Dreamweaver
28 Customizing Dreamweaver Mac OS X platforms use the following location: drive:Users/username/Library/Application Support/Macromedia/Dreamweaver 8/ Configuration The first time you run Dreamweaver, it copies only some of the configuration files into your user Configuration folder. (The files that it copies are specified in the version.xml file in the Configuration folder.) When you customize Dreamweaver from within the application (for example, when you modify one of the predesigned code snippets in the Snippets panel), Dreamweaver copies the relevant files into your user Configuration folder. The version of a file in your user Configuration folder always takes precedence over the version in the Dreamweaver Configuration folder. To customize a configuration file that Dreamweaver has not copied into your user Configuration folder, first copy the file from the Dreamweaver Configuration folder to the corresponding location inside your user Configuration folder. Then edit the copy in your user Configuration folder. Deleting configuration files in a multiuser environment When working in a multiuser operating system, if you do something within Dreamweaver that would delete a configuration file (for example, deleting a predesigned snippet from the Snippets panel), Dreamweaver creates a file in your user Configuration folder called mm_deleted_files.xml. When a file is listed in mm_deleted_files.xml, Dreamweaver behaves as if that file doesn’t exist. To deactivate a configuration file: 1. Quit Dreamweaver. 2. Using a text editor, edit mm_deleted_files.xml in your user Configuration folder; add an item tag to that file, giving the path (relative to the Dreamweaver Configuration folder) of the configuration file to deactivate. 3. Save and close mm_deleted_files.xml. 4. Start Dreamweaver again. NOTE To install extensions that all users can use in a multiuser operating system, you must be logged in as Administrator (Windows) or root (Mac OS X). NOTE Do not edit mm_deleted_files.xml in Dreamweaver
About mm_deleted_files. xml tag syntax The mm_deleted_files. xml file contains a structured list of items that specify configuration files that Dreamweaver is to ignore. These items are specified by XMl tags, which you can edit The following sections describe the syntax of the mm_deleted_files. xml tags. Optional attributes are marked in the attribute lists with curly braces(( 1); all attributes not marked with curly braces are required <deleteditems> Description Container tag that holds a list of items that Dreamweaver should treat as deleted Attributes Contents This tag must contain one or more item tags Container Example <deleteditems> </deleteditems> <item Description onfiguration file that Dreamweaver should ignore. Attributes a name The path to the configuration file, relative to the Configuration folder. In Windows, use a backslash() to separate parts of the path; on the Macintosh, use a colon (:) None(empty Customizing Dreamweaver in a multiuser environment 29
Customizing Dreamweaver in a multiuser environment 29 About mm_deleted_files.xml tag syntax The mm_deleted_files.xml file contains a structured list of items that specify configuration files that Dreamweaver is to ignore. These items are specified by XML tags, which you can edit in a text editor. The following sections describe the syntax of the mm_deleted_files.xml tags. Optional attributes are marked in the attribute lists with curly braces ({}); all attributes not marked with curly braces are required. <deleteditems> Description Container tag that holds a list of items that Dreamweaver should treat as deleted. Attributes None. Contents This tag must contain one or more item tags. Container None. Example <deleteditems> <!-- item tags here --> </deleteditems> <item> Description Specifies a configuration file that Dreamweaver should ignore. Attributes name ■ name The path to the configuration file, relative to the Configuration folder. In Windows, use a backslash (\) to separate parts of the path; on the Macintosh, use a colon (:). Contents None (empty tag)
Container This tag must be contained in a deleteditems tag Example <item name="snippets \headers\5columnwi th4links csn"/> Reinstalling and uninstalling dreamweaver in a multiuser environment After you install Dreamweaver, if you later reinstall it or upgrade to a later version, Dreamweaver automatically makes backup copies of existing user configuration files, so that if you've customized those files, you can still access the changes you made. When you uninstall Dreamweaver from a multiuser system(which you can do only if you have administrative privileges), Dreamweaver can remove each user Configuration folder for Working with browser profiles Browser profiles are the files Dreamweaver uses to check your documents when you run a target browser check(see Using Dreamweaver). Each profile contains information about the HTML tags and attributes that a particular browser supports. a browser profile can also contain warnings, error messages, and suggestions for tag substitutions Browser profiles are stored in the Configuration/BrowserProfiles folder in the Dreamweaver application folder. You can edit existing profiles or create new ones using Dreamweaver or a text editor. It is not necessary to quit Dreamweaver before editing or creating browser profiles About browser-profile formatting Browser profiles follow a specific format. To avoid parsing errors during target browser checks, follow these rules when editing or creating profiles The first line is reserved for the name of the profile. It must be followed by a single carriage return. The name on this line appears in the Target Browser Check dialog box be a The second line is reserved for the designator PROFILE TYPE=BROWSER PROFILE. Dreamweaver uses this line to determine which documents are browser profiles. Do not this line Two hyphens(-) at the beginning of a line indicate a comment(that is, the line is ignored during the target check process). A comment must start at the beginning of a line; you can't put two hyphens in the middle of a line. 30 Customizing Dreamweaver
30 Customizing Dreamweaver Container This tag must be contained in a deleteditems tag. Example <item name="snippets\headers\5columnwith4links.csn" /> Reinstalling and uninstalling Dreamweaver in a multiuser environment After you install Dreamweaver, if you later reinstall it or upgrade to a later version, Dreamweaver automatically makes backup copies of existing user configuration files, so that if you’ve customized those files, you can still access the changes you made. When you uninstall Dreamweaver from a multiuser system (which you can do only if you have administrative privileges), Dreamweaver can remove each user Configuration folder for you. Working with browser profiles Browser profiles are the files Dreamweaver uses to check your documents when you run a target browser check (see Using Dreamweaver). Each profile contains information about the HTML tags and attributes that a particular browser supports. A browser profile can also contain warnings, error messages, and suggestions for tag substitutions. Browser profiles are stored in the Configuration/BrowserProfiles folder in the Dreamweaver application folder. You can edit existing profiles or create new ones using Dreamweaver or a text editor. It is not necessary to quit Dreamweaver before editing or creating browser profiles. About browser-profile formatting Browser profiles follow a specific format. To avoid parsing errors during target browser checks, follow these rules when editing or creating profiles: ■ The first line is reserved for the name of the profile. It must be followed by a single carriage return. The name on this line appears in the Target Browser Check dialog box and in the target check report. It must be unique. ■ The second line is reserved for the designator PROFILE_TYPE=BROWSER_PROFILE. Dreamweaver uses this line to determine which documents are browser profiles. Do not change or move this line. ■ Two hyphens (--) at the beginning of a line indicate a comment (that is, the line is ignored during the target check process). A comment must start at the beginning of a line; you can’t put two hyphens in the middle of a line
m You must use a space in the following places Before the closing angle bracket(>)on the ELEMENT line After the opening parentheses in a list of values for an attribute Before a closing parentheses in a list of values Before and after each pipe() in a list of values m You must include an exclamation point(@) without a space before each of the following ELEMENT, ATTLIST, Error, and msg(ELEMENT, !ATTLIST, ! Error, Imsg) a You can include Error, Warning, and Info within the ELEMENT or the!ATTLIST I msg messages can contain only plain text HTML comments(!---->)cannot be listed as tags in browser profiles because they interfere with parsing. Dreamweaver does not report an error for comments because all browsers support them The following example shows the syntax for a tag entry: <I ELEMENT html Tag NaMe="tagName " LATTLIST htmITag unsupportedAttributel ! Error !msg="The unsupportedAttributel attribute of the htmlTag tag is not supported. Try using supportedAttributel for a similar effect supportedAttributel supportedAttribute2 (validValuel IvalidValue2 I validValue3 unsupportedAttribute2 ! Er Don’ t ever use the unsupportedAttribute2 attribute of the htmITag tag! The elements shown in this syntax are defined as follows: htmI Tag is the tag as it appears in an HTML document. tagName is an explanatory name for the tag: for example, the name for the hR tag is Horizontal Rule. The NAME attribute is optional. If specified, tagName is used in error messages; if you do not supply a name, htmI Tag is used in error messages unsupportedAttribute is an attribute that is not supported. Any tags or attributes no specifically mentioned as supported attributes are assumed to be unsupported. Specify unsupported tags or attributes only when you want to create a custom error message supportedAttribute is an attribute that is supported by htm1 Tag Only tags listed without an Error designation are considered to be supported by the browser. validvalue indicates a value that is supported by the attribute Working with browser profiles 31
Working with browser profiles 31 ■ You must use a space in the following places: ■ Before the closing angle bracket (>) on the !ELEMENT line ■ After the opening parentheses in a list of values for an attribute ■ Before a closing parentheses in a list of values ■ Before and after each pipe (|) in a list of values. ■ You must include an exclamation point (!) without a space before each of the following words: ELEMENT, ATTLIST, Error, and msg (ELEMENT, !ATTLIST, !Error, !msg ). ■ You can include !Error, !Warning, and !Info within the !ELEMENT or the !ATTLIST area. ■ !msg messages can contain only plain text. ■ HTML comments (!---->) cannot be listed as tags in browser profiles because they interfere with parsing. Dreamweaver does not report an error for comments because all browsers support them. The following example shows the syntax for a tag entry: <!ELEMENT htmlTag NAME="tagName "> <!ATTLIST htmlTag unsupportedAttribute1 !Error !msg="The unsupportedAttribute1 attribute of the htmlTag tag is not supported.Try using supportedAttribute1 for a similar effect." supportedAttribute1 supportedAttribute2 (validValue1 |validValue2 |validValue3 ) unsupportedAttribute2 !Error !msg="Don’t ever use the unsupportedAttribute2 attribute of the htmlTag tag!" > The elements shown in this syntax are defined as follows: ■ htmlTag is the tag as it appears in an HTML document. ■ tagName is an explanatory name for the tag; for example, the name for the HR tag is “Horizontal Rule.” The NAME attribute is optional. If specified, tagName is used in error messages; if you do not supply a name, htmlTag is used in error messages. ■ unsupportedAttribute is an attribute that is not supported. Any tags or attributes not specifically mentioned as supported attributes are assumed to be unsupported. Specify unsupported tags or attributes only when you want to create a custom error message. ■ supportedAttribute is an attribute that is supported by htmlTag. Only tags listed without an !Error designation are considered to be supported by the browser. ■ validValue indicates a value that is supported by the attribute
The following example shows an entry for the APPLET tag that would be accurate for Netscape Navigator 3.0: < ELEMENT APPLET Name="Java Applet"> !ATTLIST APPLET Align (top middle bottom Ileft right labsmiddle I Itexttop Class Warning msg="This browser ignores the Class attribute for the APPlet ID Warning I msg="This browser ignores the id attribute for the applet tag Use name instead Style Warning ! msg="This browser ignores the style attribute for the APPlet VSpace Creating and editing a browser profile You can create a browser profile by modifying an existing profile. For example, to create a profile for a future version of Microsoft Internet Explorer, you can open the profile for the most recent version of Internet Explorer that has a profile, add any new tags or attributes introduced in the new version, and save it as a profile for the new version Before you create a browser profile for a new version of a browser,check the MAcromediaExchangeforDreamweaversiteatwww.macromedia.com/exchange/ dreamweaver to see if Macromedia has supplied a browser profile that you can download and install using the Extension Manager To create or edit a browser profile: Open an existing profile for editing If you're creating a new profile, open the profile that most closely resembles the profile you want to create, and save the file under a new filename. If you're creating a new profile, change the name that appears on the first line of text in the file (Two profiles cannot have the same name. 32 Customizing Dreamweaver
32 Customizing Dreamweaver The following example shows an entry for the APPLET tag that would be accurate for Netscape Navigator 3.0: <!ELEMENT APPLET Name="Java Applet"> <!ATTLIST APPLET Align (top |middle |bottom |left |right |absmiddle | absbottom |baseline |texttop ) Alt Archive Class !Warning !msg="This browser ignores the CLASS attribute for the APPLET tag." Code Codebase Height HSpace ID !Warning !msg="This browser ignores the ID attribute for the APPLET tag. Use NAME instead." Name Style !Warning !msg="This browser ignores the STYLE attribute for the APPLET tag." VSpace Width > Creating and editing a browser profile You can create a browser profile by modifying an existing profile. For example, to create a profile for a future version of Microsoft Internet Explorer, you can open the profile for the most recent version of Internet Explorer that has a profile, add any new tags or attributes introduced in the new version, and save it as a profile for the new version. To create or edit a browser profile: 1. Open an existing profile for editing. If you’re creating a new profile, open the profile that most closely resembles the profile you want to create, and save the file under a new filename. 2. If you’re creating a new profile, change the name that appears on the first line of text in the file. (Two profiles cannot have the same name.) NOTE Before you create a browser profile for a new version of a browser, check the Macromedia Exchange for Dreamweaver site at www.macromedia.com/exchange/ dreamweaver to see if Macromedia has supplied a browser profile that you can download and install using the Extension Manager