Configuring Dreamweaver to Edit IRPT Pages

Related Topics

By default, MacromediaŽ DreamweaverŽ will not recognize SAP xApp Manufacturing Integration and Intelligence (SAP xMII) Report pages (files with the .irpt extension) as html and will not provide color-contexting in code view and will not provide the design view capability.  The following procedure shows you how to configure Dreamweaver to recognize irpt pages as it does typical Web page extensions such as html, htm, jsp, etc.

Note: The directory paths specified in the following steps are for a default installation of Dreamweaver on the C:\ drive.  If you have installed Dreamweaver to a different location you will have to locate the necessary file in the appropriate location.

Step 1:

Open the file "CodeColoring.xml" located in "C:\Program Files\Macromedia\Dreamweaver MX\Configuration\CodeColoring\"

After the file is open you need to edit the code on line #13.  You need to add "IRPT" to the comma delimited list of file extensions.

Example:

Before: <scheme name="HTML" id="HTML" doctypes="ASP.NET_VB, ASP.NET_CSharp, ASP-JS, ASP-VB, ColdFusion, CFC, HTML, JSP, EDML, PHP_MySQL, LibraryItem, WML" priority="50">

After: <scheme name="HTML" id="HTML" doctypes="ASP.NET_VB, ASP.NET_CSharp, ASP-JS,ASP-VB, ColdFusion, CFC, HTML, IRPT, JSP, EDML, PHP_MySQL, LibraryItem, WML" priority="50">

Step 2:

Open the file "Extensions.txt" located in "C:\Program Files\Macromedia\Dreamweaver MX\Configuration\"

After the file is open you need to edit the code on line #1.  You need to add "IRPT" to the comma delimited list of file extensions.

Example:

Before: HTM,HTML,HTA,HTC,SHTM,SHTML,STM,SSI,INC,JS,XML,DTD,XSD,XSL,...

After: HTM,HTML,HTA,HTC,IRPT,SHTM,SHTML,STM,SSI,INC,JS,XML,DTD,XSD,XSL,...

Step 3:

Open the file "MMDocumentTypes.xml" located in "C:\Program Files\Macromedia\Dreamweaver MX\Configuration\DocumentTypes\"

After the file is open you need to edit the code on line #3.  You need to add "IRPT" to the comma delimited list of file extensions.

Example:

Before: <documenttype id="HTML" internaltype="HTML" winfileextension="htm,html,shtml,shtm,stm,lasso,xhtml" macfileextension="html,htm,shtml,shtm,lasso,xhtml" file="Default.html" writebyteordermark="false">

After:<documenttype id="HTML" internaltype="HTML" winfileextension="htm,html,irpt,shtml,shtm,stm,lasso,xhtml" macfileextension="html,htm,shtml,shtm,lasso,xhtml" file="Default.html" writebyteordermark="false">

Step 4:

The final step is to allow Dreamweaver to display .irpt files in Design view.  Open Dreamweaver MX and Select "Edit > Preferences" from the menubar.  Scroll down to the File Types/Editors preference settings and make sure that the ".irpt" file extension is not listed in the "Open in Code View" field.  By default, the .IRPT file extension appears in this list.  Remove ".irpt" from the Open in Code View list, and files with this extension should now be viewable in Design view.

Note: The files "CodeColoring.xml" and "Extensions.txt" can also be set at the user level.  Explicit user profile settings will override the system settings set by the procedures listed above.  In order to ensure that the user settings are the same as the default settings, the "CodeColoring.xml" and "Extensions.txt" will also need to be modified in the user profile.

The location of the "CodeColoring.xml" file is "C:\Documents and Settings\Administrator\Application Data\Macromedia\Dreamweaver MX\Configuration\CodeColoring\"

Note: By default Dreamweaver will only install user preferences under the actual user that installed Dreamweaver.  In this example, Dreamweaver was installed by the user "Administrator", therefore, the files are found under C:\Documents and Settings\Administrator.  Modify your path to navigate to the correct installation drive for Dreamweaver (C: in this case) and the correct User ("Adminstrator" in this example).

Modify the "CodeColoring.xml" file as specified in Step 1 above.

The location of the "Extensions.txt" file is "C:\Documents and Settings\Administrator\Application Data\Macromedia\Dreamweaver MX\Configuration"  

Modify the "Extensions.txt" file as specified in Step 2 above.