additions and revisions to tasks and ref pages and images RCL_2_4
authorfturovic <frank.turovich@nokia.com>
Thu, 18 Feb 2010 11:17:02 -0600
branchRCL_2_4
changeset 987 77469bd2d10b
parent 986 226789abed73
child 988 bf9a2104bee6
additions and revisions to tasks and ref pages and images
core/com.nokia.carbide.cpp.doc.user/html/reference/BasicSettings.html
core/com.nokia.carbide.cpp.doc.user/html/reference/NewMMP_wizard.html
core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectDirectories.html
core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectNameAndLocation.html
core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectOtherSettings.html
core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_filesys.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_project.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_env.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_paths.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_sis.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_project_settings.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/wnd_sis_properties.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/debugger_settings.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/images/MMP_wizard.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/MMP_wizard2.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/carbide_build_config.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/filter_launch_config.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_build_all_configs.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_freeze_exports.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/indexer.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/indexer_prop.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_build_config_env.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_build_config_paths.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_disassembly.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_disassembly_menu.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_disassm_breakpoint.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/wiz_name_and_location_page.png
core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_sis_properties.png
core/com.nokia.carbide.cpp.doc.user/html/reference/indexer.html
core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configuration_filter.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/menus/abld.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm
core/com.nokia.carbide.cpp.doc.user/html/reference/view_mem_array.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/AddingClasses.html
core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html
core/com.nokia.carbide.cpp.doc.user/html/tasks/AppInfoFile.html
core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html
core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html
core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html
core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_setting.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_viewing.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/images/wnd_chooseBaseClass.png
core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html
core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm
core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/BasicSettings.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/BasicSettings.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,55 +1,57 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Basic Settings in New Project Wizard</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-   <h2>Basic Settings</h2>
-   <p>
-		You can set some basic properties for the project in this page, like	   Application UID, Author and Copyright
-	 notice for the project. </p>
-	 <p class="note"><b>NOTE</b> Fields appearing in window vary depending upon the type of project being created. </p>
-    <p align="center" class="Image"><img src="../images/step5.png" width="438" height="389" /></p>
-     <table cellpadding="2" cellspacing="0"
-border="0">
-     <tr valign="top"><th width="147" class="Cell">Name</th><th width="699" class="Cell">Function</th></tr><tr valign="top"><td class="Cell">
-		  <p>
-			 <b>Application UID</b> 
-	      </p></td><td class="Cell">
-		    <p>
-	        Specifies a 32-bit ID to identify the project.</p></td></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Vendor ID</b> 
-			 </p></td><td class="Cell">
-			 <p>
-				Appears for projects that require a 32-bit unique ID to identify the vendor of the
-				executable. In versions of Symbian OS with platform security, a program can
-				read a VID at runtime to check that a binary comes from a particular source. In
-				most cases, the VID should be zero, meaning that source of the executable is
-				not required for any security checks. 
-			 </p></td></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Author</b> 
-			 </p></td><td class="Cell">
-			 <p>
-				Specifies the name of the Author, who is creating this project. 
-			 </p></td></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Copyright Notice</b> 
-			 </p></td><td class="Cell">
-			 <p>
-				Specifies the copyright notice to be added to the source code of the
-				project. 
-			 </p></td></tr>
-     </table>
-     <p class="note"><b>NOTE</b> Tooltips are available for the various fields. Simply hover the pointer over the field title to view the tooltip. </p>
-     <h5>Related tasks</h5>
-		<ul>
-		  <li><a href="../tasks/CreatingNewProjects.html">Creating New Projects</a>
-    
-	    </li>
-   </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-   </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+<title>Basic Settings in New Project Wizard</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+   <h2>Basic Settings</h2>
+   <p>
+		You can set some basic properties for the project in this page, like	   Application UID, Author and Copyright
+	 notice for the project. </p>
+	 <p class="note"><b>NOTE</b> Fields appearing in window vary depending upon the type of project being created. </p>
+    <p align="center" class="Image"><img src="../images/step5.png" width="500" height="567" /></p>
+   <table width="787"
+border="0" cellpadding="2" cellspacing="0">
+     <tr valign="top"><th width="206" class="Cell">Name</th>
+     <th width="765" class="Cell">Function</th>
+     </tr><tr valign="top"><td class="Cell">
+		  <p>
+			 <b>Application UID</b> 
+	      </p></td><td class="Cell">
+		    <p>
+	        Specifies a 32-bit ID to identify the project.</p></td></tr><tr valign="top"><td class="Cell">
+			 <p>
+				<b>Vendor ID</b> 
+			 </p></td><td class="Cell">
+			 <p>
+				Appears for projects that require a 32-bit unique ID to identify the vendor of the
+				executable. In versions of Symbian OS with platform security, a program can
+				read a VID at runtime to check that a binary comes from a particular source. In
+				most cases, the VID should be zero, meaning that source of the executable is
+				not required for any security checks. 
+			 </p></td></tr><tr valign="top"><td class="Cell">
+			 <p>
+				<b>Author</b> 
+			 </p></td><td class="Cell">
+			 <p>
+				Specifies the name of the Author, who is creating this project. 
+			 </p></td></tr><tr valign="top"><td class="Cell">
+			 <p>
+				<b>Copyright Notice</b> 
+			 </p></td><td class="Cell">
+			 <p>
+				Specifies the copyright notice to be added to the source code of the
+				project. 
+			 </p></td></tr>
+     </table>
+   <p class="note"><b>NOTE</b> Tooltips are available for the various fields. Simply hover the pointer over the field title to view the tooltip. </p>
+     <h5>Related tasks</h5>
+		<ul>
+		  <li><a href="../tasks/CreatingNewProjects.html">Creating New Projects</a>
+    
+	    </li>
+   </ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+   </html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/NewMMP_wizard.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/NewMMP_wizard.html	Thu Feb 18 11:17:02 2010 -0600
@@ -44,7 +44,7 @@
    </ul>
   
    
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
    </body>
 </html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectDirectories.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectDirectories.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,61 +1,61 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Project Directories in New Project Wizard</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-   <div class="Head1">
-<h2>Project Directories</h2>
-</div><div class="Bodytext">
-	  
-	 <p>
-		You can specify the name of the project directories, where the project
-		files are to be stored. 
-	 </p> 
-	 <div class="Figure">
-
-		<p align="center" class="Image"><img src="../images/step6.png" width="438" height="389" /></p>
-		<p class="Image">Figure 1 - Project Directories page </p>
-	 </div><table width="720"
-border="0" cellpadding="2" cellspacing="0">
-	   <tr valign="top"><th width="108" class="Cell">Name</th><th width="493" class="Cell">Function</th></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Include</b> 
-			 </p></td><td class="Cell">
-			 <p>
-				Specifies the name of the include folder, where all the header
-				files for the project are located. 
-			 </p></td></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Source</b> 
-			 </p></td><td class="Cell">
-			 <p>
-				Specifies the name of the source folder, where all the source files
-				for the project are located. 
-			 </p></td></tr>
-			 <tr valign="top">
-			   <td class="Cell"><b>Group</b></td>
-			   <td class="Cell">Specifies the name of the group folder, where all the group files for the project are located. </td>
-    </tr>
-			 <tr valign="top">
-               <td class="Cell"><b>Data</b></td>
-               <td class="Cell">Specifies the name of the data folder, where all the data files for the project are located. </td>
-	   </tr>
-			 <tr valign="top">
-               <td class="Cell"><b>Install</b></td>
-               <td class="Cell">Specifies the name of the Install folder, where all the .sis files for the project are located. </td>
-	   </tr>
-			 <tr valign="top">
-               <td class="Cell"><b>Graphics</b></td>
-               <td class="Cell">Specifies the name of the graphics folder, where all the graphic files for the project are located. </td>
-	   </tr>
-</table>
-</div>
-<h5>Related tasks</h5>
-<ul>
-  <li><a href="../tasks/CreatingNewProjects.html">Creating New Projects</a></i>
-</li></ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-   </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+<title>Project Directories in New Project Wizard</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+   <div class="Head1">
+<h2>Project Directories</h2>
+</div><div class="Bodytext">
+	  
+	 <p>
+		You can specify the name of the project directories, where the project
+		files are to be stored. 
+	 </p> 
+	 <div class="Figure">
+
+		<p align="center" class="Image"><img src="../images/step6.png" width="500" height="567" /></p>
+	   <p class="Image">Figure 1 - Project Directories page </p>
+	 </div><table width="720"
+border="0" cellpadding="2" cellspacing="0">
+	   <tr valign="top"><th width="108" class="Cell">Name</th><th width="493" class="Cell">Function</th></tr><tr valign="top"><td class="Cell">
+			 <p>
+				<b>Include</b> 
+			 </p></td><td class="Cell">
+			 <p>
+				Specifies the name of the include folder, where all the header
+				files for the project are located. 
+			 </p></td></tr><tr valign="top"><td class="Cell">
+			 <p>
+				<b>Source</b> 
+			 </p></td><td class="Cell">
+			 <p>
+				Specifies the name of the source folder, where all the source files
+				for the project are located. 
+			 </p></td></tr>
+			 <tr valign="top">
+			   <td class="Cell"><b>Group</b></td>
+			   <td class="Cell">Specifies the name of the group folder, where all the group files for the project are located. </td>
+    </tr>
+			 <tr valign="top">
+               <td class="Cell"><b>Data</b></td>
+               <td class="Cell">Specifies the name of the data folder, where all the data files for the project are located. </td>
+	   </tr>
+			 <tr valign="top">
+               <td class="Cell"><b>Install</b></td>
+               <td class="Cell">Specifies the name of the Install folder, where all the .sis files for the project are located. </td>
+	   </tr>
+			 <tr valign="top">
+               <td class="Cell"><b>Graphics</b></td>
+               <td class="Cell">Specifies the name of the graphics folder, where all the graphic files for the project are located. </td>
+	   </tr>
+</table>
+</div>
+<h5>Related tasks</h5>
+<ul>
+  <li><a href="../tasks/CreatingNewProjects.html">Creating New Projects</a>
+</li></ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+   </html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectNameAndLocation.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectNameAndLocation.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,36 +1,44 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Name and Location</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-   <div class="Head1">
-<h2>Name and Location</h2>
-</div>
-   <p>
-		You can specify the name of the class and  where the generated source and header 
-		files are to be stored. 
-   </p> 
-
-		<p align="center" class="Image"><img src="images/wiz_name_and_location_page.png" width="438" height="415" /></p>
-		<p align="center" class="figure">Figure 1 - Name and Location page </p>
-	 <h5>Table 1 - Name and Locations page options</h5>
-	 <table width="720"
-border="0" cellpadding="2" cellspacing="0">
-	   <tr valign="top"><th width="201" class="Cell">Name</th><th width="509" class="Cell">Function</th></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Class name </b></p></td><td class="Cell">
-			 <p>Class name to create. 
-				</p></td></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Source</b></p></td><td class="Cell">
-			 <p>Specify directory to store source information. </p></td></tr>
-			 <tr valign="top">
-			   <td class="Cell"><b>Include</b></td>
-			   <td class="Cell">Specify directory to store header information. </td>
-    </tr>
-</table>
-     <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-   </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+<title>Name and Location</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+   <div class="Head1">
+<h2>Name and Location</h2>
+</div>
+   <p>
+		You can specify the name of the class and  where the generated source and header 
+		files are to be stored. 
+   </p> 
+
+		<p align="center" class="Image"><img src="images/wiz_name_and_location_page.png" width="607" height="500" /></p>
+   <p align="center" class="figure">Figure 1 - Name and Location page </p>
+	 <h5>Table 1 - Name and Locations page options</h5>
+	 <table width="785"
+border="0" cellpadding="2" cellspacing="0">
+	   <tr valign="top"><th width="219" class="Cell">Name</th><th width="491" class="Cell">Function</th></tr><tr valign="top"><td class="Cell">
+			 <p>
+				<b>Class name </b></p></td><td class="Cell">
+			 <p>Class name to create.				</p></td></tr>
+	   <tr valign="top">
+	     <td class="Cell"><b>Use default</b></td>
+	     <td class="Cell">Checkmark to use the suggested default names, or uncheck to customize the names.</td>
+       </tr>
+	   <tr valign="top"><td class="Cell">
+		 <p>
+		 <b>Source</b></p></td><td class="Cell">
+		   <p>Specify directory to store source information. </p></td></tr>
+			 <tr valign="top">
+			   <td class="Cell"><b>Include</b></td>
+			   <td class="Cell">Specify directory to store header information. </td>
+    </tr>
+			 <tr valign="top">
+			   <td class="Cell"><b>Force files to lowercase</b></td>
+			   <td class="Cell">Checkmark to force all filenames to use lowercase letters. Uncheck to use mixed case.</td>
+	   </tr>
+</table>
+   <div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+   </html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectOtherSettings.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectOtherSettings.html	Thu Feb 18 11:17:02 2010 -0600
@@ -7,7 +7,7 @@
 <h2>Other Settings </h2>
 </div>
    <p>
-		Specify the name of the author and copyright notice information. 
+		Specify the name of the author, version, and copyright notice information. 
    </p> 
 
 		<p align="center" class="Image"><img src="../tasks/projects/images/wiz_add_sos_class_06.png" width="419" height="420" /></p>
@@ -18,13 +18,17 @@
 	   <tr valign="top"><th width="201" class="Cell">Name</th><th width="509" class="Cell">Function</th></tr><tr valign="top"><td class="Cell">
 			 <p>
 				<b>Author</b></p></td><td class="Cell">
-			 <p>Enter author information. 
-				</p></td></tr><tr valign="top"><td class="Cell">
-			 <p>
-				<b>Copyright notice </b></p></td><td class="Cell">
-			 <p>Enter copyright notice information.</p></td></tr>
+			 <p>Enter author information.				</p></td></tr>
+	   <tr valign="top">
+	     <td class="Cell"><b>Version</b></td>
+	     <td class="Cell">Enter version information.</td>
+       </tr>
+	   <tr valign="top"><td class="Cell">
+		 <p>
+		 <b>Copyright notice </b></p></td><td class="Cell">
+		   <p>Enter copyright notice information.</p></td></tr>
 </table>
-     <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+   <div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
    </body>
    </html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_filesys.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_filesys.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,53 +1,55 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html><head>
-<title>MBM/MIF Editor</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-
-<h2>Add Images From Filesystem</h2>
-	  
-	 <p>The Add Images from Filesystem dialog allows you to search for and add images currently available in the filesystem. Select an image and click Ok to add the image.</p>
-	 <p class="note"><b>NOTE</b> Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM,MIF, or AIF editor. </p>
-	 <p>&nbsp;</p>
-	 <p align="center" class="Image"><img src="images/add_images_from_filesys.png" width="640" height="700"></p>
-		<p class="figure">Figure 1 - Add Images from Filesystem </p>
-		<h5>Table 1. Add Images&mdash;Items</h5>
-		<table width="94%"  border="0" cellpadding="2" cellspacing="0">
-          <tr>
-            <th width="32%" scope="col">Item</th>
-            <th width="68%" scope="col">Explanation</th>
-          </tr>
-          <tr>
-            <td><b>Directory</b></td>
-            <td><p>Browse to the directory containing images you want to add. </p></td>
-          </tr>
-          <tr>
-            <td><b>Available directory images </b></td>
-            <td>Shows the images found in the directory. Select images to be added. </td>
-          </tr>
-          <tr>
-            <td><b>Detected image pairs </b></td>
-            <td><p>Lists the selected images and detected image pairs.</p>
-            </td>
-          </tr>
-          <tr>
-            <td><b>Copy images into project </b></td>
-            <td>Enable this option to make a copy of selected images in the selected project location. </td>
-          </tr>
-          <tr>
-            <td><b>Overwrite existing </b></td>
-            <td><p>Enable this option to overwrite existing images with the same name. </p></td>
-          </tr>
-          <tr>
-            <td><b>Project location </b></td>
-            <td>Click the Choose... button to display the Select a folder dialog, then select a project folder to store the images.</td>
-          </tr>
-        </table>
-		<p>&nbsp;</p>
-		<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html><head>
+<title>MBM/MIF Editor</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+
+<h2>Add Images From Filesystem</h2>
+	  
+	 <p>The <b>Add Images from Filesystem</b> dialog allows you to search for and add images currently available in the filesystem. Select an image and click <b>OK</b> to add the image.</p>
+   <p class="note"><b>NOTE</b> Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM, MIF, or AIF editor. </p>
+	 <p align="center" class="Image"><img src="images/add_images_from_filesys.png" width="640" height="700"></p>
+   <p class="figure">Figure 1 - Add Images from Filesystem </p>
+		<h5>Table 1. Add Images&mdash;Items</h5>
+		<table width="94%"  border="0" cellpadding="2" cellspacing="0">
+          <tr>
+            <th width="32%" scope="col">Item</th>
+            <th width="68%" scope="col">Explanation</th>
+          </tr>
+          <tr>
+            <td><b>Directory</b></td>
+            <td><p>Browse to the directory containing images you want to add. </p></td>
+          </tr>
+          <tr>
+            <td><b>Available directory images </b></td>
+            <td>Shows the images found in the directory. Select images to be added. </td>
+          </tr>
+          <tr>
+            <td><b>Detected image pairs </b></td>
+            <td><p>Lists the selected images and detected image pairs.</p>
+            </td>
+          </tr>
+          <tr>
+            <td><b>Copy images into project </b></td>
+            <td>Enable this option to make a copy of selected images in the selected project location. </td>
+          </tr>
+          <tr>
+            <td><b>Overwrite existing </b></td>
+            <td><p>Enable this option to overwrite existing images with the same name. </p></td>
+          </tr>
+          <tr>
+            <td><b>Project location </b></td>
+            <td>Click the Choose... button to display the Select a folder dialog, then select a project folder to store the images.</td>
+          </tr>
+        </table>
+		<h5>Other references</h5>
+		<ul>
+          <li><a href="MBMEditor.html">MBM Editor</a></li>
+   </ul>
+		<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+</html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_project.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_project.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,22 +1,23 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html><head>
-<title>MBM/MIF Editor</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-
-<h2>Add Images From Project </h2>
-	  
-	 <p>The Add Images from Project dialog allows you to add images currently available in the project. Select an image and click Ok to add the image. </p>
-	 <p class="note"><b>NOTE</b> Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM,MIF, or AIF editor.</p>
-	 <p>&nbsp;</p>
-	 <p align="center" class="Image"><img src="images/add_images_from_project.png" width="640" height="567"></p>
-		<p class="figure">Figure 1 - Add Images from Project </p>
-		<p>&nbsp;</p>
-		<p>&nbsp;</p>
-		<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html><head>
+<title>MBM/MIF Editor</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+
+<h2>Add Images From Project </h2>
+	  
+	 <p>The <b>Add Images from Project</b> dialog allows you to add images currently available in the project. Select an image and click <b>OK</b> to add the image. </p>
+   <p class="note"><b>NOTE</b> Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM, MIF, or AIF editor.</p>
+   <p align="center" class="Image"><img src="images/add_images_from_project.png" width="640" height="567"></p>
+		<p class="figure">Figure 1 - Add Images from Project </p>
+		<h5>Other references</h5>
+		<ul>
+          <li><a href="MBMEditor.html">MBM Editor</a></li>
+   </ul>
+   <div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+</html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,66 +1,66 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<meta name="keywords" content="Active Configuration, SIS Builder, Environment, Arguments, Paths and Symbols, ROM Builder" >
-<title>Carbide Build Configurations </title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Carbide Build Configurations </h2>
-<p>The <b>Carbide Build Configurations</b> panel is used to specify the project's <a href="../../concepts/build_configurations.htm">active build configuration</a> and its related build properties.  </p>
-<p align="center"><img src="../images/carbide_build_config.png" width="795" height="682" /></p>
-<p class="figure">Figure 1 - Carbide Build Configurations panel </p>
-<h5>Table 1 Carbide Build Configuration items </h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="20%" scope="col">Item</th>
-    <th width="71%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td width="20%"><b>Active Configuration </b></td>
-    <td>The <b>Active Configuration</b> drop down list allows you to <a href="../../tasks/projects/prj_set_build_tgt.htm">select</a> a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.</td>
-  </tr>
-  <tr>
-    <td width="20%"><b>Manage...</b></td>
-    <td>Click the <b>Manage</b>... button to <a href="../../tasks/projects/prj_new_build_config.htm">add</a> a new SDK/Configuration or remove an existing configuration.</td>
-  </tr>
-  <tr>
-    <td><b>SIS Builder </b></td>
-    <td><p>The <a href="pane_build_config_sis.htm">SIS Builder</a> pane is used to specify a .pkg file and .sis file options to create an application .sis file. These settings apply to the currently selected Configuration.</p></td>
-  </tr>
-  <tr>
-    <td><b>Environment</b></td>
-    <td><p>The <a href="pane_build_config_env.htm">Environment</a> tab allows you to view the current User and System environment variables that will be used  when any abld command is invoked.</p></td>
-  </tr>
-  <tr>
-    <td><b>Arguments</b></td>
-    <td><p>The <a href="pane_build_config_args.htm">Arguments</a> tab allows you to add additional arguments to common build commands used by Carbide during the build process including: </p>
-        <ul>
-          <li>Bldmake Arguments</li>
-          <li>Abld Arguments</li>
-        </ul>
-      <p>See the Symbian OS documentation for a specific command for a complete list of valid arguments. </p></td>
-  </tr>
-  <tr>
-    <td><b>Paths and Symbols </b></td>
-    <td>The <a href="pane_build_config_paths.htm">Paths and Symbols</a> tab allows you to see which paths and symbols have been indexed for the project. </td>
-  </tr>
-  <tr>
-    <td><b>ROM Builder </b></td>
-    <td>The <a href="../ROM_build_settings.html">ROM Builder</a> tab  allows you to specify commands and a working directory for building a GUI ROM Image.</td>
-  </tr>
-</table>
-<h5>Other references</h5>
-<ul>
-  <li><a href="pane_build_config.htm">SIS Builder</a></li>
-  <li><a href="../../concepts/build_configurations.htm">Active  Configuration</a></li>
-  <li><a href="../../tasks/projects/prj_build.htm">Building Projects</a></li>
-  <li><a href="../../tasks/projects/working_with_sis_pkg_files.htm">Creating a .PKG file</a></li>
-</ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<meta name="keywords" content="Active Configuration, SIS Builder, Environment, Arguments, Paths and Symbols, ROM Builder" >
+<title>Carbide Build Configurations </title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Carbide Build Configurations </h2>
+<p>Use the <b>Carbide Build Configurations</b> panel to specify the project's <a href="../../concepts/build_configurations.htm">active build configuration</a> and its related build properties.  </p>
+<p align="center"><img src="../images/carbide_build_config.png" width="795" height="692" /></p>
+<p class="figure">Figure 1 - Carbide Build Configurations panel </p>
+<h5>Table 1 Carbide Build Configuration items </h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="20%" scope="col">Item</th>
+    <th width="71%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td width="20%"><b>Active Configuration </b></td>
+    <td>The <b>Active Configuration</b> drop down list allows you to <a href="../../tasks/projects/prj_set_build_tgt.htm">select</a> a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.</td>
+  </tr>
+  <tr>
+    <td width="20%"><b>Manage...</b></td>
+    <td>Click the <b>Manage</b>... button to <a href="../../tasks/projects/prj_new_build_config.htm">add</a> a new SDK/Configuration or remove an existing configuration.</td>
+  </tr>
+  <tr>
+    <td><b>SIS Builder </b></td>
+    <td><p>The <a href="pane_build_config_sis.htm">SIS Builder</a> pane is used to specify a .pkg file and .sis file options to create an application .sis file. These settings apply to the currently selected Configuration.</p></td>
+  </tr>
+  <tr>
+    <td><b>Environment</b></td>
+    <td><p>The <a href="pane_build_config_env.htm">Environment</a> tab allows you to view the current User and System environment variables that will be used  when any abld command is invoked.</p></td>
+  </tr>
+  <tr>
+    <td><b>Arguments</b></td>
+    <td><p>The <a href="pane_build_config_args.htm">Arguments</a> tab allows you to add additional arguments to common build commands used by Carbide during the build process including: </p>
+        <ul>
+          <li>Bldmake Arguments</li>
+          <li>Abld Arguments</li>
+        </ul>
+      <p>See the Symbian OS documentation for a specific command for a complete list of valid arguments. </p></td>
+  </tr>
+  <tr>
+    <td><b>Paths and Symbols </b></td>
+    <td>The <a href="pane_build_config_paths.htm">Paths and Symbols</a> tab allows you to see which paths and symbols have been indexed for the project. </td>
+  </tr>
+  <tr>
+    <td><b>ROM Builder </b></td>
+    <td>The <a href="../ROM_build_settings.html">ROM Builder</a> tab  allows you to specify commands and a working directory for building a GUI ROM Image.</td>
+  </tr>
+</table>
+<h5>Other references</h5>
+<ul>
+  <li><a href="pane_build_config.htm">SIS Builder</a></li>
+  <li><a href="../../concepts/build_configurations.htm">Active  Configuration</a></li>
+  <li><a href="../../tasks/projects/prj_build.htm">Building Projects</a></li>
+  <li><a href="../../tasks/projects/working_with_sis_pkg_files.htm">Creating a .PKG file</a></li>
+</ul>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_env.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_env.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,62 +1,62 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<meta name="keywords" content="Environment" >
-<title>Environment Variables</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Environment Variables</h2>
-<p>  The <b>Environment Variables </b> pane allows you to view the current User and System environment variables that will be used  when any abld command is invoked. User variables are modified or added when a process is invoked. Read only system variables  are listed. Variables and values in bold  are items that have been modified from their default values.</p>
-<p>Some variables have special meaning, including:</p>
-<ul>
-  <li><span class="code">PATH</span> &#8212; will always place &quot;<span class="code">${EPOCROOT}\epoc32\tools;${EPOCROOT}\epoc32\gcc\bin;</span>&quot; at the front of the <span class="code">PATH</span> regardless of what it is changed to </li>
-  <li><span class="code">PATH</span>, <span class="code">EPOCROOT</span>, and <span class="code">*MW</span> variables &#8212; <span class="note">cannot be undefined as they are required for system builds</span></li>
-</ul>
-<p align="center"><img src="../images/page_build_config_env.png" width="575" height="473"></p>
-<p class="figure">Figure 1 - Environment Variables</p>
-<h5>Table 1 Environment variable items</h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="29%" scope="col">Item</th>
-    <th width="57%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td><b>New</b></td>
-    <td>Click to add a new environment variable. You must specify a name and a value. </td>
-  </tr>
-  <tr>
-    <td><b>Edit</b></td>
-    <td>Allows you to edit the name and value of an environment variable.</td>
-  </tr>
-  <tr>
-    <td><b>Undefine</b></td>
-    <td><p>Undefines the selected variable so that it is not used during a build.</p>
-      <p class="note"><b>NOTE</b> Some variables, like <span class="code">PATH</span>, <span class="code">EPOCROOT</span>, and those beginning with <span class="code">MW*</span> have special meaning and cannot be undefined. </p></td>
-  </tr>
-  <tr>
-    <td><b>Variable use</b></td>
-    <td><p>Shows the use for the selected variable. Uses include:</p>
-      <ul>
-        <li>Default &ndash; Take the variable as-is from the system, do not modify it.</li>
-        <li>Append &ndash; Add the value displayed to the end of the existing variable (the existing variable name is not displayed.</li>
-        <li>Prepend &ndash; Add the value displayed to the front of the existing variable (the existing variable name is not displayed.</li>
-        <li>Replace &ndash; Replace the value displayed with the existing variable.</li>
-        <li>Undefine &ndash; Not used during a build</li>
-      </ul></td>
-  </tr>
-</table>
-<h5>Other references </h5>
-<ul>
-  <li><a href="pane_build_config.htm">Carbide Build Configurations</a></li>
-  <li><a href="pane_build_config.htm">SIS Builder</a></li>
-  <li><a href="pane_build_config_args.htm">Arguments</a></li>
-  <li><a href="pane_build_config_paths.htm">Paths and Symbols </a></li>
-</ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<meta name="keywords" content="Environment" >
+<title>Environment Variables</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Environment Variables</h2>
+<p>  The <b>Environment Variables </b> pane allows you to view the current User and System environment variables that will be used  when any abld command is invoked. User variables are modified or added when a process is invoked. Read only system variables  are listed. Variables and values in bold  are items that have been modified from their default values.</p>
+<p>Some variables have special meaning, including:</p>
+<ul>
+  <li><span class="code">PATH</span> &#8212; will always place &quot;<span class="code">${EPOCROOT}\epoc32\tools;${EPOCROOT}\epoc32\gcc\bin;</span>&quot; at the front of the <span class="code">PATH</span> regardless of what it is changed to </li>
+  <li><span class="code">PATH</span>, <span class="code">EPOCROOT</span>, and <span class="code">*MW</span> variables &#8212; <span class="note">cannot be undefined as they are required for system builds</span></li>
+</ul>
+<p align="center"><img src="../images/page_build_config_env.png" width="558" height="456"></p>
+<p class="figure">Figure 1 - Environment Variables</p>
+<h5>Table 1 Environment variable items</h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="29%" scope="col">Item</th>
+    <th width="57%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td><b>New</b></td>
+    <td>Click to add a new environment variable. You must specify a name and a value. </td>
+  </tr>
+  <tr>
+    <td><b>Edit</b></td>
+    <td>Allows you to edit the name and value of an environment variable.</td>
+  </tr>
+  <tr>
+    <td><b>Undefine</b></td>
+    <td><p>Undefines the selected variable so that it is not used during a build.</p>
+      <p class="note"><b>NOTE</b> Some variables, like <span class="code">PATH</span>, <span class="code">EPOCROOT</span>, and those beginning with <span class="code">MW*</span> have special meaning and cannot be undefined. </p></td>
+  </tr>
+  <tr>
+    <td><b>Variable use</b></td>
+    <td><p>Shows the use for the selected variable. Uses include:</p>
+      <ul>
+        <li>Default &ndash; Take the variable as-is from the system, do not modify it.</li>
+        <li>Append &ndash; Add the value displayed to the end of the existing variable (the existing variable name is not displayed.</li>
+        <li>Prepend &ndash; Add the value displayed to the front of the existing variable (the existing variable name is not displayed.</li>
+        <li>Replace &ndash; Replace the value displayed with the existing variable.</li>
+        <li>Undefine &ndash; Not used during a build</li>
+      </ul></td>
+  </tr>
+</table>
+<h5>Other references </h5>
+<ul>
+  <li><a href="pane_build_config.htm">Carbide Build Configurations</a></li>
+  <li><a href="pane_build_config.htm">SIS Builder</a></li>
+  <li><a href="pane_build_config_args.htm">Arguments</a></li>
+  <li><a href="pane_build_config_paths.htm">Paths and Symbols </a></li>
+</ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_paths.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_paths.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,32 +1,33 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<meta name="keywords" content="Paths and Symbols, Include Paths, Symbols" >
-<title>Paths and Symbols </title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Paths and Symbols </h2>
-<p>  The <b>Paths and Symbols  </b> pane shows the paths and symbols used to the build the project index. This is a read-only list based on the setting of the <b>Build configuration for the indexer</b> option in the <b>C/C++ General</b> &gt; <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_idx.htm">Indexer</a> panel. Carbide now caches the paths and symbols which persist between debug sessions. If any of the files like bld.inf, MMP, or any of their <span class="code">include</span> files change, the list is automatically recalculated and CDT notified. </p>
-<p>To change what appears in the list:</p>
-<ul>
-  <li>In the <a href="../MMP_Editor.html">MMP Editor</a> - add macros, user, or system include  </li>
-  <li>Using the Macro File defined in the <a href="pane_macro_settings.htm">Carbide Macro Settings</a> panel </li>
-</ul>
-<p>You can also specify a macro file using the <a href="pane_macro_settings.htm">Carbide Macro Settings</a> page in the <b>Properties for <i>project</i></b> dialog. </p>
-<p align="center"><img src="../images/page_build_config_paths.png" width="558" height="456"></p>
-<p class="figure">Figure 1 - Paths and Symbols pane </p>
-<h5>Other references </h5>
-<ul>
-  <li><a href="pane_build_config.htm">Carbide Build Configurations</a></li>
-  <li><a href="pane_build_config.htm">SIS Builder</a></li>
-  <li><a href="pane_build_config_env.htm">Environment</a></li>
-  <li><a href="pane_build_config_args.htm">Arguments</a></li>
-</ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<meta name="keywords" content="Paths and Symbols, Include Paths, Symbols" >
+<title>Paths and Symbols </title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Paths and Symbols </h2>
+<p>  The <b>Paths and Symbols  </b> pane shows the paths and symbols used to the build the project index. This is a read-only list based on the setting of the <b>Build configuration for the indexer</b> option in the <b>C/C++ General</b> &gt; <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_idx.htm">Indexer</a> panel. Carbide now caches the paths and symbols which persist between debug sessions. If any of the files like bld.inf, MMP, or any of their <span class="code">include</span> files change, the list is automatically recalculated and CDT notified. </p>
+<p>To change what appears in the list:</p>
+<ul>
+  <li>In the <a href="../MMP_Editor.html">MMP Editor</a> - add macros, user, or system include  </li>
+  <li>Using the Macro File defined in the <a href="pane_macro_settings.htm">Carbide Macro Settings</a> panel </li>
+</ul>
+<p>You can also specify a macro file using the <a href="pane_macro_settings.htm">Carbide Macro Settings</a> page in the <b>Properties for <i>project</i></b> dialog. </p>
+<p align="center"><img src="../images/page_build_config_paths.png" width="558" height="456"></p>
+<p class="figure">Figure 1 - Paths and Symbols pane </p>
+<h5>Other references </h5>
+<ul>
+  <li><a href="pane_build_config.htm">Carbide Build Configurations</a></li>
+  <li><a href="pane_build_config.htm">SIS Builder</a></li>
+  <li><a href="pane_build_config_env.htm">Environment</a></li>
+  <li><a href="pane_build_config_args.htm">Arguments</a></li>
+</ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>
+License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_sis.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_build_config_sis.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,64 +1,69 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>SIS Builder</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>SIS Builder </h2>
-<p>The<b> SIS Builder</b> pane is used to specify one or more .PKG  and .SIS file options to create  application and patch .SIS files. These settings apply to the currently selected Configuration. </p>
-<p>The SIS Builder list includes these columns:</p>
-<ul>
-  <li><b>Enabled</b> - a checkmark indicates  the SIS file is built during the build process, an unchecked file is not built </li>
-  <li><b>Partial upgrade</b> - a checkmark indicates that a partial upgrade .SIS  file should be built. Left unchecked, no partial upgrade .SIS file is generated. See <a href="#PUAnchor">Partial Upgrades Files</a> below for more information on this feature.</li>
-  <li><b>Unsigned SIS file</b> - names of the unsigned SIS files used by the project </li>
-  <li><b>Signed SIS file</b>  - names of the signed SIS files created by the project  </li>
-</ul>
-<p align="center"><img src="../images/carbide_build_config.png" width="795" height="692" /></p>
-<p class="figure">Figure 1 - SIS Builder pane</p>
-<h5>Table 1 <span class="figure">SIS Builder</span> items </h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="20%" scope="col">Item</th>
-    <th width="71%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td><b>Add</b></td>
-    <td> Opens the <a href="wnd_sis_properties.htm">SIS Properties</a> window to add a  PKG file to the list. </td>
-  </tr>
-  <tr>
-    <td><b>Edit</b></td>
-    <td> Opens the selected SIS file in the <a href="wnd_sis_properties.htm">SIS Properties</a> window for editing.</td>
-  </tr>
-  <tr>
-    <td><b>Remove</b></td>
-    <td>Removes the selected SIS file from the list.</td>
-  </tr>
-  <tr>
-    <td><b>Move Up </b></td>
-    <td>Moves the selected SIS file up in the list order.</td>
-  </tr>
-  <tr>
-    <td><b>Move Down</b></td>
-    <td>Moves the selected SIS file down in the list order.</td>
-  </tr>
-</table>
-<h3><a name="PUAnchor" id="PUAnchor"></a>Partial Upgrade Files</h3>
-<p>The SIS Builder supports the generation of partial upgrade .SIS files. A dialog appears when a SIS file exceeds 250k in size that describes the partial upgrade feature with a link to the SIS Builder page. Partial upgrade files enable Carbide to generate and download to the device only those portions of the application that have changed, enabling faster debug cycles. It does this using the SIS partial upgrade (PU) flag to mark the SIS file as a replacement or addition to the original SIS file. Debugging of large applications using Application TRK is enhanced as the entire application no longer needs to be installed on the device each time a change is made. </p>
-<p>When the Partial update option is checked for a SIS file, both a complete and partial SIS files are generated. This ensures that the full SIS file is kept in sync with the partial upgrade SIS file. The partial upgrade SIS files are placed in the same folder as the full SIS file when stored in a project directory, or in the root of the project directory when the SIS file exists outside of the project. You can see where a partial upgrade file is created by examining the <b>Partial upgrade sis/sisx path</b> in the <a href="../../projects/launch/page_installation.htm">Installation</a> tab of the launch configuration. Links to the partial upgrade files are added to the project within the <a href="../view_cpp_projects.htm">Project Explorer</a> view.</p>
-<p class="note"><b>NOTE</b> Internally, the .PKG file format of a partial upgrade file is identical to a complete .PKG file with two exceptions, 1) the file list only includes the names of files changed, and 2) the PU flag is set.</p>
-<p>Partial upgrade files are deleted and only full SIS/SISX files are generated when: 1) the full SIS/SISX files do not already exist, 2) the PKG file is changed, and 3) the Partial upgrade option is disabled.</p>
-<h5>Other references</h5>
-<ul>
-  <li><a href="pane_build_config.htm">Carbide Build Configurations </a><a href="../../tasks/projects/working_with_sis_pkg_files.htm"></a></li>
-  <li><a href="pane_build_config_env.htm">Environment</a></li>
-  <li><a href="pane_build_config_args.htm">Arguments</a></li>
-  <li><a href="pane_build_config_paths.htm">Paths and Symbols</a></li>
-</ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>SIS Builder</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>SIS Builder </h2>
+<p>The<b> SIS Builder</b> pane is used to specify one or more .PKG  and .SIS file options to create  application and patch .SIS files. These settings apply to the currently selected Configuration. </p>
+<p>The SIS Builder list includes these columns:</p>
+<ul>
+  <li><b>Enabled</b> - a checkmark indicates  the SIS file is built during the build process, an unchecked file is not built </li>
+  <li><b>Partial upgrade</b> - a checkmark indicates that a partial upgrade .SIS  file should be built. Left unchecked, no partial upgrade .SIS file is generated. See <a href="#PUAnchor">Partial Upgrades Files</a> below for more information on this feature.</li>
+  <li><b>Unsigned SIS file</b> - names of the unsigned SIS files used by the project </li>
+  <li><b>Signed SIS file</b>  - names of the signed SIS files created by the project  </li>
+</ul>
+<p align="center"><img src="../images/carbide_build_config.png" width="778" height="675" /></p>
+<p class="figure">Figure 1 - SIS Builder pane</p>
+<h5>Table 1 <span class="figure">SIS Builder</span> items </h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="20%" scope="col">Item</th>
+    <th width="71%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td><b>Add</b></td>
+    <td> Opens the <a href="wnd_sis_properties.htm">SIS Properties</a> window to add a  PKG file to the list. </td>
+  </tr>
+  <tr>
+    <td><b>Edit</b></td>
+    <td> Opens the selected SIS file in the <a href="wnd_sis_properties.htm">SIS Properties</a> window for editing.</td>
+  </tr>
+  <tr>
+    <td><b>Remove</b></td>
+    <td>Removes the selected SIS file from the list.</td>
+  </tr>
+  <tr>
+    <td><b>Move Up </b></td>
+    <td>Moves the selected SIS file up in the list order.</td>
+  </tr>
+  <tr>
+    <td><b>Move Down</b></td>
+    <td>Moves the selected SIS file down in the list order.</td>
+  </tr>
+</table>
+<h3><a name="PUAnchor" id="PUAnchor"></a>Partial Upgrade Files</h3>
+<p>The SIS Builder supports the generation of partial upgrade .SIS files. A dialog appears when a SIS file exceeds 250k in size that describes the partial upgrade feature with a link to the SIS Builder page. Partial upgrade files enable Carbide to generate and download to the device only those portions of the application that have changed, enabling faster debug cycles. It does this using the SIS partial upgrade (PU) flag to mark the SIS file as a replacement or addition to the original SIS file. Debugging of large applications using Application TRK is enhanced as the entire application no longer needs to be installed on the device each time a change is made. </p>
+<p>When the Partial update option is checked for a SIS file, both a complete and partial SIS files are generated. This ensures that the full SIS file is kept in sync with the partial upgrade SIS file. The partial upgrade SIS files are placed in the same folder as the full SIS file when stored in a project directory, or in the root of the project directory when the SIS file exists outside of the project. You can see where a partial upgrade file is created by examining the <b>Partial upgrade sis/sisx path</b> in the <a href="../../projects/launch/page_installation.htm">Installation</a> tab of the launch configuration. Links to the partial upgrade files are added to the project within the <a href="../view_cpp_projects.htm">Project Explorer</a> view.</p>
+<p class="note"><b>NOTE</b> Internally, the .PKG file format of a partial upgrade file is identical to a complete .PKG file with two exceptions, 1) the file list only includes the names of files changed, and 2) the PU flag is set.</p>
+<p>Partial upgrade files are deleted and only full SIS/SISX files are generated when:</p>
+<ul>
+  <li>the full SIS/SISX files do not already exist</li>
+  <li>the PKG file is changed</li>
+  <li>the Partial upgrade option is disabled</li>
+</ul>
+<h5>Other references</h5>
+<ul>
+  <li><a href="pane_build_config.htm">Carbide Build Configurations </a><a href="../../tasks/projects/working_with_sis_pkg_files.htm"></a></li>
+  <li><a href="pane_build_config_env.htm">Environment</a></li>
+  <li><a href="pane_build_config_args.htm">Arguments</a></li>
+  <li><a href="pane_build_config_paths.htm">Paths and Symbols</a></li>
+</ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_project_settings.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/pane_project_settings.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,127 +1,126 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Carbide Project Settings</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<style type="text/css">
-<!--
-.style1 {
-	font-family: Georgia, "Times New Roman", Times, serif;
-	font-weight: bold;
-}
--->
-</style>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Carbide Project Settings</h2>
-<p>  Use the <b>Carbide Project Settings </b>window to specify whether all components or selected subcomponents listed in a build information file (bld.inf) should be built for the currently selected project. You can also specify whether to perform a <span class="code">clean</span> or <span class="code">reallyclean</span> command on the project before building a project.</p>
-<p align="center"><img src="../images/carbide_proj_settings.png" width="640" height="643" /></p>
-<p class="figure">Figure 1 - Carbide Project Settings</p>
-<h5>Table 1 Carbide Project Settings items </h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="29%" scope="col">Item</th>
-    <th width="57%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td><b>Bld.inf file</b></td>
-    <td>This is the path to the bld.inf file that lists the makefile and mmp components.</td>
-  </tr>
-  <tr>
-    <td><b>Bld.inf</b></td>
-    <td>Select this option to ensure all components are built for the selected project. </td>
-  </tr>
-  <tr>
-    <td><b>Selected Components</b></td>
-    <td><p>Select this option to  specify which components of the bld.inf file to be built, including makefiles. The equivalent call to abld is <span class="code">abld build &lt;subcomponent&gt;</span>. Use the <b>Exclude extension makefiles</b> and <b>Exclude test components</b> options to manage the items that appear in the list. </p>
-      <p>Toggle the state of each component to set its build state to true or not. A checkmark indicates a component is built. Click on a column title to sort the items by that columns contents. </p>
-    </td>
-  </tr>
-  <tr>
-    <td><b>Exclude extension makefiles </b></td>
-    <td>Toggles the presense of extension makefiles in the Selected components list. </td>
-  </tr>
-  <tr>
-    <td><b>Exclude test components </b></td>
-    <td>Toggles the presense of test components in the Selected components list. </td>
-  </tr>
-  <tr>
-    <td><b>Enable project specific settings </b></td>
-    <td>Click to set project specific build settings. By default a project in the workspace uses the global build settings unless this option is enabled. See the <a href="../wnd_build_prefs.htm">Build</a> preference panel for details on these options. </td>
-  </tr>
-  <tr>
-    <td><b>Configure Workspace Settings... </b></td>
-    <td>Opens the <a href="../wnd_build_prefs.htm">Build</a> preference panel. </td>
-  </tr>
-</table>
-<p>&nbsp;</p>
-<p align="center"><img src="../images/carbide_proj_settings_sbsv1.png" alt="sbsv1 tab" width="420" height="283"></p>
-<p align="center" class="figure">Figure 2 - SBSv1 Tab</p>
-<h5 align="left">Table 2 Symbian Build System v1 tab </h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="29%" scope="col">Item</th>
-    <th width="57%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td><span class="style1">Clean level </span></td>
-    <td><p>Specifies the level of clean to perform on  project files. The levels include:</p>
-      <ul>
-        <li>Level 0  (<span class="code">abld clean</span>) - removes all the intermediate files created during compilation, and all the executables and import libraries created by the linker</li>
-        <li>Level 1  (<span class="code">abld reallyclean</span>) - performs a <span class="code">clean</span> operation, but also removes all exported files and makefiles</li>
-        <li>Level 2  (<span class="code">abld reallyclean</span>, <span class="code">bldmake clean</span>) - performs  a <span class="code">reallyclean</span> operation and then removes all files created by bldmake</li>
-      </ul></td>
-  </tr>
-  <tr>
-    <td><span class="style1">Manage dependency tracking </span></td>
-    <td>If checked, the Symbian command line build system will not generate dependencies for source and resource files. These will be managed by Carbide. This can reduce build times. </td>
-  </tr>
-  <tr>
-    <td><b>Show a dialog to modify build actions when modified MMPs are detected </b></td>
-    <td><p>If checked, you will be asked what action to take before a build if a MMP file has been modified. </p>
-        <p>If not checked, the default action is taken for all modified mmp files. </p></td>
-  </tr>
-  <tr>
-    <td><b>Default action to take when mmp files are modified </b></td>
-    <td>Select either None, Link only, or Compile and Link.</td>
-  </tr>
-</table>
-<p align="left">&nbsp;</p>
-<p align="center"><img src="../images/carbide_proj_settings_sbsv2.png" alt="sbsv2 tab" width="420" height="283"></p>
-<p align="center" class="figure">Figure 3 - SBSv2 Tab</p>
-<h5 align="left">Table 3 Symbian Build System v2 tab (only visible for Projects created with SBSv2 builder) </h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="29%" scope="col">Item</th>
-    <th width="57%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td><span class="style1">Clean level </span></td>
-    <td>Select the level of clean when cleaning a project.
-      <p><strong>abld clean</strong> erases all files created by a corresponding abld target   command (all intermediate files created during compilation and all executables and import libraries created by the linker)</p>
-      <p><strong>abld reallyclean</strong> does what abld clean does, and also removes files   exported by abld export and makefiles generated by abld makefile, or the abld   test equivalents</p></td>
-  </tr>
-  <tr>
-    <td><b>Keep going  </b></td>
-    <td><p>This build option tells a particular command to   keep going even if unrelated build steps report errors or files are missing.</p>    </td>
-  </tr>
-  <tr>
-    <td><b>Debug </b></td>
-    <td><p>This option generates symbolic debug information for release or debug builds,   independent of the compiler optimization level.</p>
-      <p>By default, the build system generates symbolic debug information only for   the debug builds. With this option, the generation of symbolic debug information   is extended to release builds to support debugging of release binaries on ARM   ABI compliant platforms.</p></td>
-  </tr>
-  <tr>
-    <td><span class="style1">Override default make engine</span> </td>
-    <td>Check this box to enable  an edit box to specify the make engine to use, for example, eMake  from Electric Cloud.</td>
-  </tr>
-</table>
-<p>&nbsp;</p>
-<h4>Related tasks</h4>
-<ul><li><a href="../../tasks/projects/prj_build.htm">Building Projects</a></li>
-</ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Carbide Project Settings</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<style type="text/css">
+<!--
+.style5 {font-family: Verdana, Ariel, Helvetica, sans-serif; font-weight: bold; }
+-->
+</style>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Carbide Project Settings</h2>
+<p>  Use the <b>Carbide Project Settings </b>window to specify whether all components or selected subcomponents listed in a build information file (bld.inf) should be built for the currently selected project. You can also specify whether to perform a <span class="code">clean</span> or <span class="code">reallyclean</span> command on the project before building a project.</p>
+<p align="center"><img src="../images/carbide_proj_settings.png" width="640" height="643" /></p>
+<p class="figure">Figure 1 - Carbide Project Settings</p>
+<h5>Table 1 Carbide Project Settings items </h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="29%" scope="col">Item</th>
+    <th width="57%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td><b>Bld.inf file</b></td>
+    <td>This is the path to the bld.inf file that lists the makefile and mmp components.</td>
+  </tr>
+  <tr>
+    <td><b>Bld.inf</b></td>
+    <td>Select this option to ensure all components are built for the selected project. </td>
+  </tr>
+  <tr>
+    <td><b>Selected Components</b></td>
+    <td><p>Select this option to  specify which components of the bld.inf file to be built, including makefiles. The equivalent call to abld is <span class="code">abld build &lt;subcomponent&gt;</span>. Use the <b>Exclude extension makefiles</b> and <b>Exclude test components</b> options to manage the items that appear in the list. </p>
+      <p>Toggle the state of each component to set its build state to true or not. A checkmark indicates a component is built. Click on a column title to sort the items by that columns contents. </p>
+    </td>
+  </tr>
+  <tr>
+    <td><b>Exclude extension makefiles </b></td>
+    <td>Toggles the presense of extension makefiles in the Selected components list. </td>
+  </tr>
+  <tr>
+    <td><b>Exclude test components </b></td>
+    <td>Toggles the presense of test components in the Selected components list. </td>
+  </tr>
+  <tr>
+    <td><b>Enable project specific settings </b></td>
+    <td>Click to set project specific build settings. By default a project in the workspace uses the global build settings unless this option is enabled. See the <a href="../wnd_build_prefs.htm">Build</a> preference panel for details on these options. </td>
+  </tr>
+  <tr>
+    <td><b>Configure Workspace Settings... </b></td>
+    <td>Opens the <a href="../wnd_build_prefs.htm">Build</a> preference panel. </td>
+  </tr>
+</table>
+<p>&nbsp;</p>
+<p align="center"><img src="../images/carbide_proj_settings_sbsv1.png" alt="sbsv1 tab" width="417" height="243"></p>
+<p align="center" class="figure">Figure 2 - SBSv1 Tab</p>
+<h5 align="left">Table 2 Symbian Build System v1 tab </h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="29%" scope="col">Item</th>
+    <th width="57%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td><span class="style5">Clean level </span></td>
+    <td><p>Specifies the level of clean to perform on  project files. The levels include:</p>
+      <ul>
+        <li>Level 0  (<span class="code">abld clean</span>) - removes all the intermediate files created during compilation, and all the executables and import libraries created by the linker</li>
+        <li>Level 1  (<span class="code">abld reallyclean</span>) - performs a <span class="code">clean</span> operation, but also removes all exported files and makefiles</li>
+        <li>Level 2  (<span class="code">abld reallyclean</span>, <span class="code">bldmake clean</span>) - performs  a <span class="code">reallyclean</span> operation and then removes all files created by bldmake</li>
+      </ul></td>
+  </tr>
+  <tr>
+    <td><span class="style5">Manage dependency tracking </span></td>
+    <td>If checked, the Symbian command line build system will not generate dependencies for source and resource files. These will be managed by Carbide. This can reduce build times. </td>
+  </tr>
+  <tr>
+    <td><b>Show a dialog to modify build actions when modified MMPs are detected </b></td>
+    <td><p>If checked, you will be asked what action to take before a build if a MMP file has been modified. </p>
+        <p>If not checked, the default action is taken for all modified mmp files. </p></td>
+  </tr>
+  <tr>
+    <td><b>Default action to take when mmp files are modified </b></td>
+    <td>Select either None, Link only, or Compile and Link.</td>
+  </tr>
+</table>
+<p align="left">&nbsp;</p>
+<p align="center"><img src="../images/carbide_proj_settings_sbsv2.png" alt="sbsv2 tab" width="427" height="269"></p>
+<p align="center" class="figure">Figure 3 - SBSv2 Tab</p>
+<h5 align="left">Table 3 Symbian Build System v2 tab (only visible for Projects created with SBSv2 builder) </h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="29%" scope="col">Item</th>
+    <th width="57%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td><b>Clean level </b></td>
+    <td>Select the level of clean when cleaning a project.
+      <ul>
+        <li><strong>abld clean</strong> erases all files created by a corresponding abld target   command (all intermediate files created during compilation and all executables and import libraries created by the linker)</li>
+        <li><strong>abld reallyclean</strong> does what abld clean does, and also removes files   exported by abld export and makefiles generated by abld makefile, or the abld   test equivalents</li>
+      </ul></td>
+  </tr>
+  <tr>
+    <td><b>Keep going  </b></td>
+    <td><p>This build option tells a particular command to   keep going even if unrelated build steps report errors or files are missing.</p>    </td>
+  </tr>
+  <tr>
+    <td><b>Debug </b></td>
+    <td><p>This option generates symbolic debug information for release or debug builds,   independent of the compiler optimization level.</p>
+      <p>By default, the build system generates symbolic debug information only for   the debug builds. With this option, the generation of symbolic debug information   is extended to release builds to support debugging of release binaries on ARM   ABI compliant platforms.</p></td>
+  </tr>
+  <tr>
+    <td><b>Override default make engine</b> </td>
+    <td>Check this box to enable  an edit box to specify the make engine to use, for example, eMake  from Electric Cloud.</td>
+  </tr>
+</table>
+<p>&nbsp;</p>
+<h4>Related tasks</h4>
+<ul><li><a href="../../tasks/projects/prj_build.htm">Building Projects</a></li>
+</ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/wnd_sis_properties.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/build_properties/wnd_sis_properties.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,60 +1,60 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>SIS Properties </title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>SIS Properties </h2>
-<p> Use the<b> SIS Properties</b> dialog to specify SIS file creation and signing options for selected SIS file included in the project. </p>
-<p align="center"><img src="../images/wnd_sis_properties.png" width="455" height="452" /></p>
-<p class="figure">Figure 1 - SIS Properties dialog </p>
-<h5>Table 1 <span class="figure">SIS Properties window</span> items </h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="20%" scope="col">Item</th>
-    <th width="71%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td width="20%"><b>SIS  File Creation Options </b></td>
-    <td><p>Define the SIS file created: </p>
-      <ul>
-        <li><b>PKG File</b> &#8212; name of the PKG file to build. Click Browse to locate or else type in the file path and name. </li>
-        <li><b>Output File Name</b> &#8212; unsigned file name that is generated from the PKG file selected</li>
-        <li><b>Content Search Location</b> &#8212;   root location where PKG files are specified to search </li>
-        <li><b>Generate partial upgrade when appropriate</b> &#8212; enable to create package update files that only contain files changed since the last build</li>
-    </ul></td>
-  </tr>
-  <tr>
-    <td><b>Signing Options </b></td>
-    <td><p>Defines the signing options applied to the configuration. The options include: </p>
-      <ul>
-        <li><b>Don't sign sis file</b> &#8212; builds sis file without signing it </li>
-        <li><b>Self sign sis file</b> &#8212; signs the sis file without specifying the certificate/key pair </li>
-        <li><b>Sign sis file with certificate/key pair</b> &#8212; signs the sis file using the specified certificate/key pair </li>
-    </ul>      
-      <p>Enter the required information into the enabled fields based on the signing option selected above: </p>
-      <ul>
-        <li><b>Signed SIS File Name</b> &#8212;Final output signed file name. Default is input PKG name with &lsquo;sisx&rsquo; extension.</li>
-        <li><b>Password</b> &#8212; Optional password</li>
-        <li><b>Additional options</b> &#8212; Enter unfiltered options to be passed to the tool</li>
-        <li><b>Certificate</b> &ndash; Enter or browse to certificate</li>
-        <li><b>Key</b> &#8212; Enter or browse to  key</li>
-      </ul>    
-      <p class="note"><b>NOTE</b> On Symbian OS 9.x builds, if the key/cert pair are not defined, <span class="code">makekeys</span> will be called and temporary ones will be generated for you to      &quot;self-sign&quot; the application. Self-signed applications should be in the
-        0xE0000000-0xEFFFFFFF range.</p>
-      <p class="note"><b>NOTE</b> All Application TRK build configuration require a PKG file. If none is found in the active project then you will be asked to <a href="pane_pkg_config.htm">choose</a> one.</p>      </td>
-  </tr>
-</table>
-<h5>Related reference </h5>
-<ul>
-  <li><a href="pane_build_config.htm">Carbide Build Configurations</a></li>
-  <li><a href="pane_build_config_env.htm">Environment variables</a></li>
-</ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>SIS Properties </title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>SIS Properties </h2>
+<p> Use the<b> SIS Properties</b> dialog to specify SIS file creation and signing options for the selected SIS file included in the project. </p>
+<p align="center"><img src="../images/wnd_sis_properties.png" width="375" height="452" /></p>
+<p class="figure">Figure 1 - SIS Properties dialog </p>
+<h5>Table 1 <span class="figure">SIS Properties window</span> items </h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="20%" scope="col">Item</th>
+    <th width="71%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td width="20%"><b>SIS  File Creation Options </b></td>
+    <td><p>Define the SIS file created: </p>
+      <ul>
+        <li><b>PKG File</b> &#8212; name of the PKG file to build. Click Browse to locate or else type in the file path and name. </li>
+        <li><b>Output File Name</b> &#8212; unsigned file name that is generated from the PKG file selected</li>
+        <li><b>Content Search Location</b> &#8212;   root location where PKG files are specified to search </li>
+        <li><b>Generate partial upgrade when appropriate</b> &#8212; enable to create package update files that only contain files changed since the last build</li>
+    </ul></td>
+  </tr>
+  <tr>
+    <td><b>Signing Options </b></td>
+    <td><p>Defines the signing options applied to the configuration. The options include: </p>
+      <ul>
+        <li><b>Don't sign sis file</b> &#8212; builds sis file without signing it </li>
+        <li><b>Self sign sis file</b> &#8212; signs the sis file without specifying the certificate/key pair </li>
+        <li><b>Sign sis file with certificate/key pair</b> &#8212; signs the sis file using the specified certificate/key pair </li>
+    </ul>      
+      <p>Enter the required information into the enabled fields based on the signing option selected above: </p>
+      <ul>
+        <li><b>Signed SIS File Name</b> &#8212;Final output signed file name. Default is input PKG name with &lsquo;sisx&rsquo; extension.</li>
+        <li><b>Password</b> &#8212; Optional password</li>
+        <li><b>Additional options</b> &#8212; Enter unfiltered options to be passed to the tool</li>
+        <li><b>Certificate</b> &ndash; Enter or browse to certificate</li>
+        <li><b>Key</b> &#8212; Enter or browse to  key</li>
+      </ul>    
+      <p class="note"><b>NOTE</b> On Symbian OS 9.x builds, if the key/cert pair are not defined, <span class="code">makekeys</span> will be called and temporary ones will be generated for you to      &quot;self-sign&quot; the application. Self-signed applications should be in the
+        0xE0000000-0xEFFFFFFF range.</p>
+      <p class="note"><b>NOTE</b> All Application TRK build configuration require a PKG file. If none is found in the active project then you will be asked to <a href="pane_pkg_config.htm">choose</a> one.</p>      </td>
+  </tr>
+</table>
+<h5>Related reference </h5>
+<ul>
+  <li><a href="pane_build_config.htm">Carbide Build Configurations</a></li>
+  <li><a href="pane_build_config_env.htm">Environment variables</a></li>
+</ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/debugger_settings.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/debugger_settings.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -25,7 +25,7 @@
   <li><a href="../tasks/start/carbide_debugging.htm">Debugging a Program</a> (Example)</li>
   <li><a href="../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
 </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
 </body>
 </html>
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/MMP_wizard.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/MMP_wizard2.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/carbide_build_config.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/filter_launch_config.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_build_all_configs.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_freeze_exports.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/indexer.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/indexer_prop.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_build_config_env.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_build_config_paths.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_disassembly.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_disassembly_menu.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_disassm_breakpoint.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wiz_name_and_location_page.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_sis_properties.png has changed
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/indexer.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/indexer.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,68 +1,67 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Indexer</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-<h2>Indexer</h2>
-<p>The C/C++ indexer uses the parser to create a database of your source and header files that provides the basis for C/C++ search, navigation features and content assist. The goal of indexing is to record all named elements in a project's source code and store them with their related data. The indexer parses each source file in your project and updates related indexes. By indexing your files with the indexer, useful features such as code completion and fast file search can be used. It is also possible to specify different indexer settings for each project in your workspace.</p>
-   <p>If you choose to perform the Full C/C++ Indexer option the indexer will consume the CPU for some time, but you will gain more benefit from the process after it completes.
-    However, if you do not require the benefits of indexing your project, select the No Indexer option to speed up the process of building your project.</p>
-   <p>The indexer runs on a background thread and reacts to resource change events such as:</p>
-   <ul>
-     <li>C/C++ project creation/deletion</li>
-     <li>Source files creation/deletion</li>
-     <li>File imports</li>
-     <li> Source file content changes</li>
-   </ul>
-   <p>The Preferences Indexer can be accessed by selecting Window &gt; Preferences then expanding the C/C++ group and selecting Indexer (figure 1). The Project Properties Indexer can be accessed by selecting a project in the C/C++ Projects or Symbian Project Navigator view and selecting Project &gt; Properties, then select C/C++ Indexer (figure 2).</p>
-   <p class="note"><b>NOTE</b> You can also rebuild a project's index by selecting a project, right-click to display the context menu and select <b>Rebuild Index</b>. </p>
-   <p align="center" class="Image"><img src="images/indexer.png" width="663" height="439" /></p>
-   <p align="left" class="figure">Figure 1 - Indexer Window in Preferences Panels</p>
-   <p align="left" class="Image">&nbsp;</p>
-   <p align="center" class="Image"><img src="images/indexer_prop.png" width="616" height="392" /></p>
-   <p align="left" class="figure">Figure 2 - Indexer Window in Project Properties</p>
-   <p align="left" class="Image">&nbsp; </p>
-   <table cellpadding="2" cellspacing="0"
-border="0">
-	 <tr valign="top"><th width="221" class="Cell">Name</th><th width="558" class="Cell">Function</th></tr>
-         <tr valign="top">
-           <td class="Cell"><b>Available indexers </b></td>
-           <td class="Cell"><p>Dropdown list of available index options.</p>
-             <ul>
-               <li>No Indexer - Project source files will not be indexed, therefore search features will not work accurately and code completion will not be available.</li>
-               <li>Fast C/C++ Indexer - Source files will be indexed and eat up a lot of CPU time and memory during the first generation of the indexer. This can take some time depending on the size of your project. Afterwards the indexer will only reindex the relevant parts you changed in your code and not the whole source tree.</li>
-               <li>Full C/C++ Indexer - Performs a complete parse of all source files and takes up the most amount of time to complete.</li>
-           </ul></td>
-        </tr>
-         <tr valign="top">
-           <td class="Cell"><b>Apply indexer to all projects now </b></td>
-           <td class="Cell">Select this option to apply the Fast C/C++ Indexer option to all projects in your current workspace. </td>
-        </tr>
-         <tr valign="top">
-           <td class="Cell"><b>Rebuild the index when changing to a different build configuration </b></td>
-           <td class="Cell">Select this option to rescan and index the source files for the current project when you change the active build configuration. The index will be built based on the active build configuration. All macros and header files used to build the index will be taken from the active build configuration.</td>
-         </tr>
-         <tr valign="top">
-           <td class="Cell"><p><b>Build the index only for the build configuration specified in the project's indexer settings</b></p>
-           <p>&nbsp;</p>
-           <p><b>Build the index only for the specified build configuration </b></p></td>
-           <td class="Cell"><p>The indexer will only be run for the build configuration specified in the Indexer panel in the project's property settings. All macros and header files used to build the index will be taken from the specified configuration.</p>
-           <p>&nbsp;</p>
-           <p class="note"><b>NOTE</b> This option appears in the project properties indexer panel. A dropdown list is provided to select a build configuration for the currently selected project.</p></td>
-         </tr>
-   </table>
-	 <p>&nbsp;</p>
-	 <h5>Related concepts</h5>
-	 <ul>
-       <li><a href="../concepts/build_configurations.htm">Active Build Configuration</a></li>
-  </ul>
-	 <h5>Related tasks     </h5>
-	 <ul><li><a href="../tasks/projects/prj_set_build_tgt.htm">Setting Active Build Configurations</a></li>
-       <li><a href="../tasks/projects/prj_debug_config.htm">Creating Launch Configurations</a></li>
-	   <li><a href="../tasks/projects/prj_new_build_config.htm">Creating Build Configurations</a></li>
-	 </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-   </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+<title>Indexer</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+<h2>Indexer</h2>
+<p>The C/C++ <b>Indexer</b> uses the parser to create a database of  source and header files that provide the basis for C/C++ search, navigation features and content assist. The goal of indexing is to record all named elements in a project's source code and store them with their related data. The indexer parses each source file in your project and updates related indexes. By indexing your files with the indexer, useful features such as code completion and fast file search can be used. It is also possible to specify different indexer settings for each project in your workspace.</p>
+   <p>If you choose to perform the <b>Full C/C++ Indexer </b>option the indexer will consume the CPU for some time, but you will gain more benefit from the process after it completes.
+    However, if you do not require the benefits of indexing your project, select the <b>No Indexer</b> option to speed up the process of building your project.</p>
+   <p>The indexer runs on a background thread and reacts to resource change events such as:</p>
+   <ul>
+     <li>C/C++ project creation/deletion</li>
+     <li>Source files creation/deletion</li>
+     <li>File imports</li>
+     <li> Source file content changes</li>
+   </ul>
+   <p>The global <b>Indexer</b> is accessed by selecting <b>Window &gt; Preferences &gt; C/C++ &gt; Indexer</b> (figure 1). The sections outlined in red appear as part of the project level indexer.</p>
+   <p class="note"><b>NOTE</b> You can also rebuild a project's index by selecting a project, then right-click  and select the <b>Rebuild Index</b> menu item. </p>
+   <p align="center" class="Image"><img src="images/indexer.png" width="627" height="704" /></p>
+   <p align="left" class="figure">Figure 1 - Indexer Window in Preferences Panels</p>
+   <p align="left" class="Image">The project  indexer is accessed by selecting a project in the Project Explorer or Symbian Project Navigator view and selecting <b>Project &gt; Properties &gt; C/C++ General &gt; Indexer</b> (figure 2).</p>
+   <p align="center" class="Image"><img src="images/indexer_prop.png" width="682" height="579" /></p>
+   <p align="left" class="figure">Figure 2 - Indexer Window in Project Properties </p>
+   <table cellpadding="2" cellspacing="0"
+border="0">
+	 <tr valign="top"><th width="221" class="Cell">Name</th><th width="558" class="Cell">Function</th></tr>
+         <tr valign="top">
+           <td class="Cell"><b>Select indexer </b></td>
+           <td class="Cell"><p>Dropdown list of available index options.</p>
+             <ul>
+               <li>Fast C/C++ Indexer - Source files will be indexed and eat up a lot of CPU time and memory during the first generation of the indexer. This can take some time depending on the size of your project. Afterwards the indexer will only reindex the relevant parts you changed in your code and not the whole source tree.</li>
+               <li>Full C/C++ Indexer - Performs a complete parse of all source files and takes up the most amount of time to complete.</li>
+               <li>No Indexer - Project source files are not indexed, therefore search features will not work accurately and code completion will not be available.</li>
+           </ul></td>
+        </tr>
+         <tr valign="top">
+           <td class="Cell"><b>Apply indexer to all projects now </b></td>
+           <td class="Cell">Select this option to apply the Fast C/C++ Indexer option to all projects in your current workspace. </td>
+        </tr>
+         <tr valign="top">
+           <td class="Cell"><b>Rebuild the index when changing to a different build configuration </b></td>
+           <td class="Cell">Select this option to rescan and index the source files for the current project when you change the active build configuration. The index will be built based on the active build configuration. All macros and header files used to build the index will be taken from the active build configuration.</td>
+         </tr>
+         <tr valign="top">
+           <td class="Cell"><p><b>Build the index only for the build configuration specified in the project's indexer settings</b></p>
+           <p>&nbsp;</p>
+           <p><b>Build the index only for the specified build configuration </b></p></td>
+           <td class="Cell"><p>The indexer will only be run for the build configuration specified in the Indexer panel in the project's property settings. All macros and header files used to build the index will be taken from the specified configuration.</p>
+           <p>&nbsp;</p>
+           <p class="note"><b>NOTE</b> This option appears in the project properties indexer panel. A dropdown list is provided to select a build configuration for the currently selected project.</p></td>
+         </tr>
+   </table>
+	 <p>&nbsp;</p>
+	 <h5>Related concepts</h5>
+	 <ul>
+       <li><a href="../concepts/build_configurations.htm">Active Build Configuration</a></li>
+  </ul>
+	 <h5>Related tasks     </h5>
+	 <ul><li><a href="../tasks/projects/prj_set_build_tgt.htm">Setting Active Build Configurations</a></li>
+       <li><a href="../tasks/projects/prj_debug_config.htm">Creating Launch Configurations</a></li>
+	   <li><a href="../tasks/projects/prj_new_build_config.htm">Creating Build Configurations</a></li>
+	 </ul>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+   </html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configuration_filter.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configuration_filter.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,31 +1,30 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Launch Configuration Filters</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Launch Configuration Filters</h2>
-<p>The Launch Configuration Filters panel is used to  filter out which launch configurations will not appear in the Run or Debug window used to define launch configurations. For example, select the <b>Filter checked launch configuration types</b> option and check the configuration types that you do not want to appear in the <b>Run &gt; Run...</b> or <b>Run &gt; Debug...</b> window, as shown in Figure 1. </p>
-<p align="center"><img src="images/filter_launch_config.png" width="580" height="573" /></p>
-<p class="figure">Figure 1 - Launch Configuration Filters </p>
-<p>&nbsp;</p>
-<h5>Related references</h5>
-<ul>
-  <li><a href="../reference/wnd_debug_configuration.htm">Debug Window</a> </li>
-</ul>
-<h5>Related tasks </h5>
-<ul>
-  <li><a href="../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
-  <li><a href="../tasks/projects/prj_new_build_config.htm">Adding/Removing Build Configurations</a></li>
-  <li><a href="../tasks/projects/prj_set_build_tgt.htm">Setting a Build Configuration </a></li>
-</ul>
-<div class="step">
-  <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</div>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Launch Configuration Filters</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Launch Configuration Filters</h2>
+<p>Use the <b>Launch Configurations</b> panel  to  filter out which launch configurations appear in the <b>Run</b> or <b>Debug</b> window used to define launch configurations. For example, select the <b>Delete configurations when associated resource is deleted</b> option and check the configuration types that you do not want to appear in the <b>Run &gt; Run...</b> or <b>Run &gt; Debug...</b> window, as shown in Figure 1. </p>
+<p align="center"><img src="images/filter_launch_config.png" width="627" height="557" /></p>
+<p class="figure">Figure 1 - Launch Configurations preference panel</p>
+<h5>Related references</h5>
+<ul>
+  <li><a href="../reference/wnd_debug_configuration.htm">Debug Window</a> </li>
+</ul>
+<h5>Related tasks </h5>
+<ul>
+  <li><a href="../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
+  <li><a href="../tasks/projects/prj_new_build_config.htm">Adding/Removing Build Configurations</a></li>
+  <li><a href="../tasks/projects/prj_set_build_tgt.htm">Setting a Build Configuration </a></li>
+</ul>
+<div class="step">
+  <div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</div>
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/abld.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/abld.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -10,7 +10,7 @@
 </head>
 <body bgcolor="#FFFFFF">
 <h2>ABLD Actions </h2>
-<p>Use the <b>ABLD</b> menu option to invoke an specific <span class="code">abld</span> command on the selected project or file. ABLD is available under  <b>Project &gt; ABLD</b> or by right-clicking a project or file in the <a href="../view_cpp_projects.htm">Project Explorer</a> or <a href="../view_sym_proj_nav.htm">Symbian Project Navigator</a> views and choosing <b>ABLD &gt; <i>command</i></b>. When executed any arguments specified in the <a href="../build_properties/pane_build_config_args.htm">Carbide Build Configurations</a> pane for the command are passed to the selected tool. </p>
+<p>Use the <b>ABLD</b> menu option to invoke an specific <span class="code">abld</span> command on the selected project or file. ABLD is available under  <b>Project &gt; ABLD</b> or by right-clicking a project or file in the <a href="../view_cpp_projects.htm">Project Explorer</a>, <a href="../view_sym_proj_nav.htm">Symbian Project Navigator</a>, and <a href="../view_disassembly.htm">Disassembly</a> views and choosing <b>ABLD &gt; <i>command</i></b>. When executed any arguments specified in the <a href="../build_properties/pane_build_config_args.htm">Carbide Build Configurations</a> pane for the command are passed to the selected tool. </p>
 <p align="center"><img src="../images/menu_abld.png" width="496" height="136"></p>
 <p class="figure">Figure 1 - Available ABLD actions</p>
 <p>The available commands include:</p>
@@ -28,7 +28,7 @@
 <ul>
   <li><a href="menus.htm">Carbide Menu</a></li>
 </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
 </body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -19,11 +19,11 @@
     <th width="62%" scope="col">Explanation</th>
   </tr>
   <tr>
-    <td>Check All </td>
+    <td><b>Check All </b></td>
     <td>Enables catching all exceptions.</td>
   </tr>
   <tr>
-    <td>Clear All </td>
+    <td><b>Clear All </b></td>
     <td>Disables catching all exceptions.</td>
   </tr>
 </table>
@@ -53,7 +53,7 @@
     <li><a href="../debugger/debug/viewing_debug.htm">Debug View</a></li>
   </ul>
 
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
 </body>
 </html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -23,61 +23,84 @@
   <li>Reposition the PC  using the various move commands (Figure 1) by first selecting the line to move to, then select the command from the context menu.</li>
   <li>Set breakpoints at the start of any assembler instruction by right-clicking the left hand column to view the context menu options (Figure 2) </li>
 </ul>
-<p>Figure 1 shows the Dissassembly view and the PC context menu that appears when you right-click in the data pane. Right-clicking  the left border opens the breakpoint context menu.</p>
-<p align="center"><img src="images/view_disassembly.png" width="555" height="272" alt="" /></p>
-<p class="figure">Figure 1 - Repositioning the PC in the Disassembly view</p>
-<p class="figure"><img src="images/view_disassm_breakpoint.png" width="506" height="172" alt="" /></p>
-<p class="figure">Figure 2 - Setting Breakpoints in the Disassembly view </p>
-<h5>Table 1. Disassembly view &mdash;context menu</h5>
+<p>Figure 1 shows the <b>Dissassembly</b> view stopped at a breakpoint.</p>
+<p align="center"><img src="images/view_disassembly.png" width="785" height="202" alt="" /></p>
+<p class="figure">Figure 1 - Disassembly view</p>
+<p>Figure 2 shows the context menu that appears when you right-click in the Dissassembly pane. Right-clicking  the left border opens the breakpoint context menu in Figure 3.</p>
+<p class="figure"><img src="images/view_disassembly_menu.png" width="232" height="133"></p>
+<p class="figure">Figure 2 - Disassembly pane context menu</p>
+<h5>Table 1. Disassembly pane &mdash; context menu</h5>
 <table width="88%"  border="0" cellpadding="2" cellspacing="0">
   <tr>
-      <th width="26%" scope="col">Item</th>
-      <th width="8%" scope="col">Icon</th>
-      <th width="66%" scope="col">Explanation</th>
+    <th width="26%" scope="col">Item</th>
+    <th width="8%" scope="col">Icon</th>
+    <th width="66%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td><b>Run to Line </b></td>
+    <td><center>
+      <img src="images/icon_dis_run_to_line.png" width="18" height="18">
+    </center></td>
+    <td>Select <b>Run to Line</b> to execute the program from the currently executed line (the green line) to the selected line (the blue line).</td>
   </tr>
-    <tr>
-      <td><b>Run to Line </b></td>
-      <td><center>
-        <img src="images/icon_dis_run_to_line.png" width="18" height="18">
-      </center>      </td>
-      <td>Select <b>Run to Line</b> to execute the program from the currently executed line (the green line) to the selected line (the blue line).</td>
+  <tr>
+    <td><b>Move to Line</b></td>
+    <td><center>
+      <img src="images/icon_dis_move_to_line.png" width="19" height="15">
+    </center></td>
+    <td><p>Select <b>Move to Line</b> to move the program counter to the selected line  (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program.</p>
+        <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
+  </tr>
+  <tr>
+    <td><b>Resume at Line </b></td>
+    <td><center>
+      <img src="images/icon_dis_resume_at_line.png" width="18" height="14">
+    </center></td>
+    <td><p>Select <b>Resume at Line</b> to begin program execution at the selected line   (the blue line), skipping all lines between it and the currently executed line  (the green line). </p>
+        <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
+  </tr>
+  <tr>
+    <td><b>ABLD</b></td>
+    <td>&nbsp;</td>
+    <td>Use the <a href="menus/abld.htm">ABLD</a> menu option to invoke an specific <span class="code">abld</span> command on the selected project or file.</td>
   </tr>
-    <tr>
-      <td><b>Move to Line</b></td>
-      <td><center>
-        <img src="images/icon_dis_move_to_line.png" width="19" height="15">
-      </center>
-      </td>
-      <td><p>Select <b>Move to Line</b> to move the program counter to the selected line  (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program.</p>
-      <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
-    </tr>
-    <tr>
-      <td><b>Resume at Line </b></td>
-      <td><center>
-        <img src="images/icon_dis_resume_at_line.png" width="18" height="14">
-      </center>      </td>
-      <td><p>Select <b>Resume at Line</b> to begin program execution at the selected line   (the blue line), skipping all lines between it and the currently executed line  (the green line). </p>
-      <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
-    </tr>
-    <tr>
-      <td><b>Toggle Breakpoint </b></td>
-      <td><center>
-      </center>      </td>
-      <td>Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between <a href="../tasks/breakpoints/pgm_bp_setting.htm">setting</a> and <a href="../tasks/breakpoints/pgm_bp_clearing.htm">removing</a> the breakpoint. </td>
-    </tr>
-    <tr>
-      <td><b>Disable/Enable Breakpoint </b></td>
-      <td><center>
-      </center>      </td>
-      <td>Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.</td>
-    </tr>
-    <tr>
-      <td><b>Breakpoint Properties </b></td>
-      <td><center>
-      </center>      </td>
-      <td>Select this option to open the Breakpoint Properties dialog. </td>
-    </tr>
+  <tr>
+    <td><b>Freeze Exports</b></td>
+    <td><center>
+      <img src="images/icon_freeze_exports.png" width="19" height="18">
+    </center>
+    </td>
+    <td>Calls the appropriate <span class="code">abld</span> command  to generate a .def file.</td>
+  </tr>
+  <tr>
+    <td><b>Build All Configurations</b></td>
+    <td><center>
+      <img src="images/icon_build_all_configs.png" width="20" height="18">
+    </center>
+    </td>
+    <td>Click <b>Build All Configurations</b> to build all enabled build configurations in the current project.</td>
+  </tr>
+  <tr>
+    <td><b>Toggle Breakpoint </b></td>
+    <td><center>
+    </center></td>
+    <td>Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between <a href="../tasks/breakpoints/pgm_bp_setting.htm">setting</a> and <a href="../tasks/breakpoints/pgm_bp_clearing.htm">removing</a> the breakpoint. </td>
+  </tr>
+  <tr>
+    <td><b>Disable/Enable Breakpoint </b></td>
+    <td><center>
+    </center></td>
+    <td>Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.</td>
+  </tr>
+  <tr>
+    <td><b>Breakpoint Properties </b></td>
+    <td><center>
+    </center></td>
+    <td>Select this option to open the <b>Breakpoint Properties</b> dialog. </td>
+  </tr>
 </table>
+<p class="figure"><img src="images/view_disassm_breakpoint.png" width="785" height="202" alt="" /></p>
+<p class="figure">Figure 3 - Setting Breakpoints in the Disassembly view </p>
 <div class="step">
   <h4>Opening the Disassembly view </h4>
   <ul>
@@ -96,6 +119,6 @@
 <ul><li><a href="../concepts/breakpoints.htm">Breakpoints</a></li>
   <li><a href="../debugger/debug/cmds_reposition_pc.htm">Repositioning the Program Counter</a></li>
 </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 </body>
 </html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -62,7 +62,9 @@
     </tr>
     <tr>
       <td><b>Refresh</b></td>
-      <td>&nbsp;</td>
+      <td><center>
+      </center>
+      </td>
       <td>Click to refresh view display.</td>
     </tr>
 </table>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mem_array.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mem_array.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,97 +1,97 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>ArrayWindow</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Array Window</h2>
-<p> An Array window allows manipulation of a contiguous block of memory, displayed as an array of elements. The window lists array contents sequentially, starting at
-element 0.</p>
-<p>The Array window title shows the base address bound to the array. The base address can bind to an address, a variable, or a register. An array bound to a local variable closes after the routine that defines the variable returns to the calling routine.</p>
-<p>For array elements cast as structured types, a hierarchical control appears to the left of each element. Use these hierarchical controls to expand or collapse the display of each element&rsquo;s contents.</p>
-<p>Figure 1 shows an Array window. Table 1 explains the items in the window.</p>
-<p class="figure">Figure 1 Array window</p>
-<p>&nbsp;</p>
-<h5>Table 1 Array window&mdash;items </h5>
-<table width="100%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="25%" scope="col">Item</th>
-    <th width="21%" scope="col">Icon</th>
-    <th width="54%" scope="col">Explanation</th>
-  </tr>
-  <tr>
-    <td>Hierarchical control</td>
-    <td>&nbsp;</td>
-    <td>Click to collapse the view of the information pane.</td>
-  </tr>
-  <tr>
-    <td>Bind To</td>
-    <td>&nbsp;</td>
-    <td>Select the base address of the array: Address, Variable, or Register.</td>
-  </tr>
-  <tr>
-    <td>Array size</td>
-    <td>&nbsp;</td>
-    <td>Enter the number of elements to display in the Array window.</td>
-  </tr>
-  <tr>
-    <td>Struct Member</td>
-    <td>&nbsp;</td>
-    <td>Select a specific member to show in each element, or show all members.</td>
-  </tr>
-  <tr>
-    <td>Element</td>
-    <td>&nbsp;</td>
-    <td>Shows the array elements in a hierarchical list.</td>
-  </tr>
-  <tr>
-    <td>Value</td>
-    <td>&nbsp;</td>
-    <td>Shows the value of each array element.</td>
-  </tr>
-  <tr>
-    <td>Location</td>
-    <td>&nbsp;</td>
-    <td>Shows the address in memory of each array element.</td>
-  </tr>
-</table>
-<div class="step">
-  <h5>Opening an Array Window</h5>
-  <p> Use the View Array command to manipulate a memory block in an Array window.</p>
-  <ol>
-    <li>Select the array that you want to view.</li>
-    <li>Select Data &gt; View Array.</li>
-    <p>A new Array window appears.</p>
-  </ol>
-</div>
-<p class="note"><b>TIP</b> Drag and drop a register or variable name into an Array window to set the base address. Use the View Memory As command to interpret memory displayed in an Array window as a different type.</p>
-<p>Alternatively, use a contextual menu to open an Array window, as explained in Table 2.</p>
-<h5>Table 2 Opening an Array window by using a contextual menu </h5>
-<table width="77%"  border="0" cellpadding="2" cellspacing="0">
-  <tr>
-    <th width="31%" scope="col">On this host&hellip;</th>
-    <th width="69%" scope="col">Do this&hellip;</th>
-  </tr>
-  <tr>
-    <td>Windows</td>
-    <td>Right-click the array and select View Array.</td>
-  </tr>
-  <tr>
-    <td>Solaris</td>
-    <td>Click and hold on the array, then select View Array.</td>
-  </tr>
-  <tr>
-    <td>Linux</td>
-    <td>Click and hold on the array, then select View Array.</td>
-  </tr>
-</table>
-<p><br />
-</p>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>ArrayWindow</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Array Window</h2>
+<p> The <b>Array</b> window allows manipulation of a contiguous block of memory, displayed as an array of elements. The window lists array contents sequentially, starting at
+element 0.</p>
+<p>The Array window title shows the base address bound to the array. The base address can bind to an address, a variable, or a register. An array bound to a local variable closes after the routine that defines the variable returns to the calling routine.</p>
+<p>For array elements cast as structured types, a hierarchical control appears to the left of each element. Use these hierarchical controls to expand or collapse the display of each element&rsquo;s contents.</p>
+<p>Figure 1 shows an Array window. Table 1 explains the items in the window.</p>
+<p class="figure">Figure 1 Array window</p>
+<p>&nbsp;</p>
+<h5>Table 1 Array window&mdash;items </h5>
+<table width="100%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="25%" scope="col">Item</th>
+    <th width="21%" scope="col">Icon</th>
+    <th width="54%" scope="col">Explanation</th>
+  </tr>
+  <tr>
+    <td>Hierarchical control</td>
+    <td>&nbsp;</td>
+    <td>Click to collapse the view of the information pane.</td>
+  </tr>
+  <tr>
+    <td>Bind To</td>
+    <td>&nbsp;</td>
+    <td>Select the base address of the array: Address, Variable, or Register.</td>
+  </tr>
+  <tr>
+    <td>Array size</td>
+    <td>&nbsp;</td>
+    <td>Enter the number of elements to display in the Array window.</td>
+  </tr>
+  <tr>
+    <td>Struct Member</td>
+    <td>&nbsp;</td>
+    <td>Select a specific member to show in each element, or show all members.</td>
+  </tr>
+  <tr>
+    <td>Element</td>
+    <td>&nbsp;</td>
+    <td>Shows the array elements in a hierarchical list.</td>
+  </tr>
+  <tr>
+    <td>Value</td>
+    <td>&nbsp;</td>
+    <td>Shows the value of each array element.</td>
+  </tr>
+  <tr>
+    <td>Location</td>
+    <td>&nbsp;</td>
+    <td>Shows the address in memory of each array element.</td>
+  </tr>
+</table>
+<div class="step">
+  <h5>Opening an Array Window</h5>
+  <p> Use the View Array command to manipulate a memory block in an Array window.</p>
+  <ol>
+    <li>Select the array that you want to view.</li>
+    <li>Select Data &gt; View Array.</li>
+    <p>A new Array window appears.</p>
+  </ol>
+</div>
+<p class="note"><b>TIP</b> Drag and drop a register or variable name into an Array window to set the base address. Use the View Memory As command to interpret memory displayed in an Array window as a different type.</p>
+<p>Alternatively, use a contextual menu to open an Array window, as explained in Table 2.</p>
+<h5>Table 2 Opening an Array window by using a context menu </h5>
+<table width="77%"  border="0" cellpadding="2" cellspacing="0">
+  <tr>
+    <th width="31%" scope="col">On this host&hellip;</th>
+    <th width="69%" scope="col">Do this&hellip;</th>
+  </tr>
+  <tr>
+    <td>Windows</td>
+    <td>Right-click the array and select View Array.</td>
+  </tr>
+  <tr>
+    <td>Solaris</td>
+    <td>Click and hold on the array, then select View Array.</td>
+  </tr>
+  <tr>
+    <td>Linux</td>
+    <td>Click and hold on the array, then select View Array.</td>
+  </tr>
+</table>
+<p><br />
+</p>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddingClasses.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddingClasses.html	Thu Feb 18 11:17:02 2010 -0600
@@ -16,12 +16,11 @@
 		  or select <b>New &gt; Class</b> from the project&prime;s pop-up
 	    menu where you want the new class to reside. </p> 
      <p>
-	    The New C++ Class wizard then appears. 
-     </p> 
+	    The <b>New C++ Class</b> wizard  appears.     </p> 
 	  </li> 
 	  <li> 
 	    <p>
-		   Specify the folder when the class should be created by typing the		    <b>Source Folder</b> name or by clicking <b>Browse</b> and
+		   Specify the folder where the class should be created by typing the		    <b>Source Folder</b> name or by clicking <b>Browse</b> and
 	    selecting the source folder. </p> 
 		  
 	     <p align="center" class="Image"><img src="../images/newclasswiz.gif" alt="" width="500" height="568"  border="0" /></p>
@@ -40,7 +39,7 @@
 	    <p>
 		   Click <b>Add</b> to choose the <b>Base Classes</b> from which the class has to be derived</p> 
 		  
-	     <p align="center" class="Image"><img src="../images/choosebaseclass.gif" alt="" width="306" height="565"  border="0" /></p>
+	     <p align="center" class="Image"><img src="images/wnd_chooseBaseClass.png" width="309" height="565"></p>
        <p>To select a base type you are looking for, do the following: </p>
       <ol type="a">
       <li>Type the search string to locate the class, struct and other low-level types you are looking for</li>
@@ -63,7 +62,6 @@
 			   class in new header and source files with default names. Otherwise, deselect
 			   the Use Default checkbox, and enter the Header and Source file names. Click Browse to select the Header and Source files, if you want to
         add the class declaration and definition to existing files. </p> 
-
      <li>
 	       Click Finish to create a C++ class according to the
         specification, or click Cancel to cancel the task.</li> 
@@ -73,7 +71,7 @@
 	   <ul>
          <li><a href="../reference/NewClassWizard.html">New C++ Classs Wizard</a></li>
    </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
    </body>
    </html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html	Thu Feb 18 11:17:02 2010 -0600
@@ -21,7 +21,7 @@
 	   </li> 
 		<div class="Figure">
 
-			 <p class="Image"><img src="../images/SDKPreferences.png" width="696" height="583" /></p>
+			 <p class="Image"><img src="../images/SDKPreferences.png" width="740" height="546" /></p>
  
 		  
 </div> 
@@ -38,7 +38,7 @@
 <ul>
        <li><a href="../reference/SDKPreferences.html">SDK Preferences</a></li>
    </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
    </body>
    </html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/AppInfoFile.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/AppInfoFile.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,59 +1,59 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Creating an AIF File in Modifying Resources</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-   <h2>Creating an AIF File</h2>
-   
-   <p>
-	  The AIF Definition File wizard creates a file that
-		specifies an AIF file to be built as part of the project. An AIF file is a
-		Symbian OS application information file, which describes an application's icons
-   and properties. For more information, see <a href="../concepts/AIFDefWizard.html">Concepts &gt;AIF File</a>.</p>
-   <p class="note"><b>NOTE</b> AIF files are used only for projects created for Symbian OS versions
-		  before v9.1.</p>
-   <div class="step">
-     <h4>
-     To create an AIF  file</h4>
-   <ol> 
-	  <li> 
-	    <p>
-		   Open the MMP file associated with the project in the Symbian Project Navigator (double-click on .mmp file or right-click and select Open).</p> 
-	    
-	     <p align="center" class="Image"><img src="projects/images/AIF_editor_mmp_symprojnav.png" width="271" height="261" /></p>
-     </li>
-		 <p class="figure">Figure 1 - MMP File in Symbian Project Navigator</p>
-	  <li>The MMP editor opens.</li> 
-	    
-      <p align="center" class="Image"><img src="projects/images/AIF_editor_mmp_editor.png" width="581" height="383" /></p>
-      <p class="figure">Figure 2 - Access to AIF Editor in MMP Editor</p>
-	  <li> 
-	    Select the Sources tab and select AIF in the Resources group.
-	  </li> 
-	  <li>Click Add button to open the AIF editor.</li>
-	  <p align="center"><img src="projects/images/AIF_editor.png" width="700" height="575" /></p>
-	  <p class="figure">Figure 3 - AIF Editor</p>
-	  <li>   
-      Enter a name for the .aif file or click untitled.aif button to set a default name based on the SDK and project name.</li> 
-      <li>Specify a resource file from the dropdown list or browse the filesystem.</li>
-	  <li>Click the Add From Project or Add From Filesystem buttons to add image and mask bitmaps.</li>
-	  <li>Set the Shared Image Properties (color depth, mask depth, and color format).</li>
-	  <li>Select the two images (image and mask) and select Pair Image and Mask button.</li>
-	  <li>Click Ok to create AIF file from the information you defined in the editor. </li>
-   </ol>
-	  <p align="center"><img src="projects/images/AIF_editor2.png" width="700" height="575" /></p>
-	  <p align="left" class="figure">Figure 4- AIF Editor with information defined</p>
-   </div>
-     <h5>Related concepts</h5>
-     <ul>
-       <li> <a href="../concepts/AIFDefWizard.html">AIF File</a></li>
-     </ul>
-     <h5>Related reference </h5>
-   <ul>
-     <li> <a href="../reference/AIFEditor.html">AIF Editor</a></li>
-   </ul>
-   <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-   </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+<title>Creating an AIF File in Modifying Resources</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+   <h2>Creating an AIF File</h2>
+   
+   <p>
+	  The <b>AIF Definition File</b> wizard creates a file that
+		specifies an AIF file to be built as part of the project. An AIF file is a
+		Symbian OS application information file, which describes an application's icons
+   and properties. For more information, see <a href="../concepts/AIFDefWizard.html">Concepts &gt;AIF File</a>.</p>
+   <p class="note"><b>NOTE</b> AIF files are used only for projects created for Symbian OS versions
+		  before v9.1.</p>
+   <div class="step">
+     <h4>
+     To create an AIF  file</h4>
+   <ol> 
+	  <li> 
+	    <p>
+		   Open the MMP file associated with the project in the <a href="../reference/view_sym_proj_nav.htm">Symbian Project Navigator</a> (double-click on MMP file or right-click and select <b>Open</b>).</p> 
+	    
+        <p align="center" class="Image"><img src="projects/images/AIF_editor_mmp_symprojnav.png" width="271" height="261" /></p>
+     </li>
+		 <p class="figure">Figure 1 - MMP File in Symbian Project Navigator</p>
+	  <li>The MMP editor opens.</li> 
+	    
+      <p align="center" class="Image"><img src="projects/images/AIF_editor_mmp_editor.png" width="581" height="383" /></p>
+      <p class="figure">Figure 2 - Access to AIF Editor in MMP Editor</p>
+	  <li> 
+	    Select the Sources tab and select AIF in the Resources group.
+	  </li> 
+	  <li>Click Add button to open the AIF editor.</li>
+	  <p align="center"><img src="projects/images/AIF_editor.png" width="700" height="575" /></p>
+	  <p class="figure">Figure 3 - AIF Editor</p>
+	  <li>   
+      Enter a name for the .aif file or click untitled.aif button to set a default name based on the SDK and project name.</li> 
+      <li>Specify a resource file from the dropdown list or browse the filesystem.</li>
+	  <li>Click the Add From Project or Add From Filesystem buttons to add image and mask bitmaps.</li>
+	  <li>Set the Shared Image Properties (color depth, mask depth, and color format).</li>
+	  <li>Select the two images (image and mask) and select Pair Image and Mask button.</li>
+	  <li>Click Ok to create AIF file from the information you defined in the editor. </li>
+   </ol>
+	  <p align="center"><img src="projects/images/AIF_editor2.png" width="700" height="575" /></p>
+	  <p align="left" class="figure">Figure 4- AIF Editor with information defined</p>
+   </div>
+     <h5>Related concepts</h5>
+     <ul>
+       <li> <a href="../concepts/AIFDefWizard.html">AIF File</a></li>
+     </ul>
+     <h5>Related reference </h5>
+   <ul>
+     <li> <a href="../reference/AIFEditor.html">AIF Editor</a></li>
+   </ul>
+   <div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+   </html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,271 +1,271 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html><head>
-<title>Exporting project(s) to MMP/Bld.inf files in Tasks</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-   </head>
-   <body>
-
-   <div class="step">
-     <h2>Exporting project(s) to MMP/Bld.inf files</h2>
-     <p>
-       The command-line Symbian OS toolchain requires a component description
-       file (<span class="code">Bld.Inf</span>) and one or more project definition files
-       (<span class="code">.mmp</span>) to build a project. The export command allows you to create
-       these files for your projects.       </p>
-     <h4>
-       To export project(s) to a <span class="code">Bld.Inf</span> and/or <span class="code">MMP</span>
-       file:       </h4>
-     <ol> 
-       <li> 
-         Click <span class="code">File &gt; Export...</span> to get a list of the
-         available export wizards: 
-         <p>
-           OR         </p> 
-	     <p>
-	        Click <span class="code">Export</span> from the pop-up menus of the
-	        <span class="code">C/C++ Projects</span> and <span class="code">Navigator</span> views to get a
-		      list of the available export wizards:         </p> 
-	     <div class="Figure">
-		      
-	        <p class="Image"><a name=""><img src="../images/export1.gif" alt="" width="470" height="550"  border="0"></a></p>
-  </div> 
-       </li> 
-	    <li>Select <span class="code">Symbian MMP/Bld.Inf</span> and click
-		    <span class="code">Next</span> to go to the <span class="code">Symbian Projects</span> page: 
-	      </p> 
-	      <div class="Figure">
-		      
-	         <p class="Image"><a name=""><img src="../images/export2.gif" alt="" width="470" height="550"  border="0"></a></p>
-  </div> 
-	    </li> 
-	    <li> 
-		    Select the project(s) you intend to export from the list of
-		    <span class="code">Symbian Projects</span>.	    </li> 
-	    <li> 
-		    Click <span class="code">Next</span> to go to the <span class="code">SDKs and Build Configurations Selection</span> page: 
-	      <div class="Figure">
-		      
-	         <p class="Image"><a name=""><img src="../images/export3.gif" alt="" width="470" height="550"  border="0"></a></p>
-  </div> 
-	    </li> 
-	    <li> 
-		    Select at least one build configuration for each project in the
-		    left-hand pane from the list of available SDKs and build configurations in the
-		    right-hand pane. By default, all the build configurations chosen during the
-		    last export are selected. If a project is being exported for the first time, no
-		    build configurations are selected. 
-	      <p>
-	         The build configurations chosen for a project are distinguished using
-		      guard macros in the <span class="code">MMP</span> file. The guard macros are placed around
-		      the <span class="code">MMP</span> file statements containing resources or build setting,
-		      only valid for a subset of the chosen build configurations.	      </p> 
-	      <p>
-	         There are cases where guard macros may not be able to distinguish
-		      between two build configurations. The export wizard shows a conflict when two
-		      such ambiguous build configurations are selected by the user.	      </p> 
-	      <p>
-	         The combination of build configurations which results in a conflict
-		      are as follows:	      </p> 
-  
-		  <ul> 
-		    <li> 
-		      <p>
-		        Any two build configurations that differ only in the build
-		        variant (UDEB/UREL). For example, "UIQ 3.0 Phone (GCCE) Debug" and "UIQ 3.0
-		        Phone (GCCE) Release" configurations will result in a conflict, as they differ
-		        only in the build variant.	           </p> 
-	        </li> 
-		     <li> 
-		        <p>
-		          Any two build configurations, of which one is user-defined based
-			       on the other using the <span class="code">Manage</span> option in the <span class="code">C/C++
-			         Build properties</span> view of the project.		        </p> 
-			    <p>
-			      <i>For more information on managing build configurations,
-			      refer to the CDT user guide.</i>		        </p> 
-		     </li> 
-	      </ul>
-  
-		  <p>
-		    The wizard will change the build settings in the <span class="code">MMP</span>
-		    file based on the chosen build configuration. If more than one build
-		    configuration which require different build settings are chosen, guard macros
-		    are used to determine the build settings. For example, if you want to change
-		    the <span class="code">SECUREID</span> option for all the <code>EKA2</span> build
-		    configurations, the wizard will append the following lines into the
-		    <span class="code">MMP</span> file:	      </p> 
-	      <p class="CodeBlock">#if def EKA2<br>&nbsp;&nbsp;SECUREID 0x00301<br>#endif</p> 
-	      <p>
-	         Where <code>EKA2</span> is the guard macro for all the build
-		      configurations designed for the EKA2 kernel. The above <span class="code">MMP</span> file
-		      statements check whether the <code>EKA2</span> guard macro is defined, and if
-		      it is, change the <code>SECUREID</span> option accordingly.	      </p> 
-	    </li> 
-	    <li> 
-		    Click <span class="code">Next</span> to go to the <span class="code">MMP File and Bld.inf
-		      File</span> page: 
-	      <div class="Figure">		    
-	        <div align="center"><a name=""><img src="../images/export4.gif" alt="" width="470" height="550"  border="0"></a></div>
-	      </div> 
-	      <ol type="a">
-	        <li>
-	           Type the <span class="code">MMP</span> file location in the <span class="code">MMP
-		          File</span> field, or click <span class="code">Browse</span> to select the
-	           <span class="code">MMP</span> file for each project listed above. 
-	           <p>
-	             By default, the <span class="code">MMP</span> file is exported to one of the
-		          following locations in the order listed below:	           </p>
-	           <ul>
-	             <li> The location where the project was exported the last time. </li>
-	             <li> The group folder of the exported project, if it exists. </li>
-	             <li> The exported project's root directory. </li>
-              </ul>
-	        </li>
-	        <li>
-	           If you select the <span class="code">Export Bld.inf file</span> option, then
-		        type the <span class="code">Bld.Inf</span> file location in the <span class="code">Bld.inf
-		          File</span> field, or click <span class="code">Browse</span> to select the
-	           <span class="code">Bld.Inf</span> file. 
-	           <p>
-	             If you do not select the <span class="code">Export Bld.inf file</span> option,
-		          then you need not specify the <span class="code">Bld.Inf</span> file location.	           </p>
-	           <p>
-	             By default, the <span class="code">Bld.Inf</span> file is exported to one of the
-		           following locations in the order listed below:	           </p>
-	           <ul>
-	             <li>
-	               The location where the <span class="code">Bld.Inf</span> was created when the
-		             project was last exported to an <span class="code">MMP</span> file. </li>
-	             <li> The <span class="code">MMP</span> file location.</li>
-              </ul>
-	        </li>
-          </ol>
-	    </li> 
-       <li>Click Next to go to the Other Makefiles page where you can specify extra Makefiles to invoke from bld.inf </li> 
-  
-	 <blockquote>
-	   <p align="center"><img src="../images/export4a.gif" width="470" height="550"></p>
-    </blockquote>
-       <li>Click Next to open the Scalable Icon Makefiles page where you can specify the Makefiles used to generate scalable icon files.</li>
-	   <p align="center"><img src="../images/export4b.gif" width="470" height="550"></p>
-        <li>Click <span class="code">Next</span> to go to the <span class="code">PRJ_EXPORTS</span> page, to specify the list of files to be copied from the source directories to
-            the releasables directories while building the project:
-            <div class="Figure">
-              
-              <p class="Image"><a name=""><img src="../images/export5.gif" alt="" width="470" height="550"  border="0"></a></p>
-            </div>
-          <p>
-             <i>Note that this page is displayed only if you have selected
-             the Export Bld.inf file option in the previous page.</i>          </p>
-        </li>
-        <li> 
-            Type the <span class="code">Source</span> and <span class="code">Target</span>
-            locations of the file to be copied, and click <span class="code">Add</span> to append
-            the source-target pair to the <span class="code">PRJ_EXPORTS</span> list. You can use
-            <span class="code">Browse</span> to specify the source file and its target location. If
-            the target location for the file is not specified, it will be copied to
-            <span class="code">epoc32\include</span> directory. 
-          <p>
-             Note that the contents of the <span class="code">PRJ_EXPORTS</span> list is
-              exactly the same as it appears in the <code>PRJ_EXPORTS</span> section of the
-             <span class="code">Bld.Inf</span> file.          </p> 
-        </li>
-        <li> 
-            If you want to modify or delete any entry from the
-            <span class="code">PRJ_EXPORTS</span> list, select the entry and click
-            <span class="code">Modify</span> or <span class="code">Delete</span>.        </li>
-        <li> 
-            Click <span class="code">Next</span> to go to the <span class="code">MMP Preview</span>
-            page: 
-          <div class="Figure">
-              
-             <p class="Image"><a name=""><img src="../images/export6.gif" alt="" width="470" height="550"  border="0"></a></p>
-      </div> 
-        </li>
-        <li> 
-            Select a project from the list of projects to be exported, to see a
-            preview of the <span class="code">MMP</span> file in the pane below. You can edit the
-            contents if required.        </li>
-        <li> 
-            Click <span class="code">Finish</span> to complete the export process. The
-            wizard will create the managed <span class="code">MMP</span> file and <code class="filename">Bld.inf</span>
-            file in their specified locations.
-          <p>
-             A managed <span class="code">MMP</span> file contains the same content as a
-              standard <span class="code">MMP</span> file would, but the contents are organised into
-              following managed sections using special tags:          </p> 
-      
-		  <ul> 
-		    <li> 
-		      <p>
-		        Binary Build Information	           </p> 
-            </li> 
-             <li> 
-                <p>
-                  Search Path                </p> 
-             </li> 
-             <li> 
-                <p>
-                  Project Content Managed                </p> 
-             </li> 
-             <li> 
-                <p>
-                  Linkage                </p> 
-             </li> 
-             <li> 
-                <p>
-                  Customization                </p> 
-             </li> 
-          </ul>
-      
-		  <p>
-		    You will be notified in case of any errors during the updated
-		    process, which results in not creating the <span class="code">MMP</span> or
-		    <span class="code">Bld.Inf</span> files.</p> 
-        </li>
-     </ol>
-   </div>
-     <p>
-       The following <span class="code">MMP</span> file generated by the wizard, shows how
-       its content is organised using managed sections:       </p>
-     <h4 class="listing">// HelloCarbide.mmp</h4>
-     <p class="listing">/*&amp; START_BINARY_BUILD &amp;*/<br>
-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
-     CAPABILITY READUSERDATA<br>
-     TARGET HelloCarbide.exe<br>
-     TARGETTYPE exe<br>
-     UID 0x00000000 0xe4d95f85<br>
-     VENDORID 0x00000000<br>
-     SECUREID 0xE4D95F85<br>
-     /*&amp; END_BINARY_BUILD &amp;*/</p>
-     <p class="listing">/*&amp; START_SEARCH_PATHS &amp;*/<br>
-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
-     SYSTEMINCLUDE \epoc32\include \epoc32\include\variant \epoc32\include\oem<br>
-     USERINCLUDE ..\inc ..\data<br>
-     /*&amp; END_SEARCH_PATHS &amp;*/</p>
-     <p class="listing">/*&amp; START_PROJECT_CONTENT &amp;*/<br>
-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
-     SOURCEPATH ..\data<br>
-     START RESOURCE HelloCarbide.rss<br>
-     TARGETPATH resource\apps<br>
-     HEADER<br>
-     END<br>
-     START RESOURCE HelloCarbide_reg.rss<br>
-     TARGETPATH private\10003a3f\apps<br>
-     HEADER<br>
-     END<br>
-     SOURCEPATH ..\src<br>
-     SOURCE Waving.cpp HelloCarbideDocument.cpp HelloCarbideApplication.cpp<br>
-     SOURCE HelloCarbideAppView.cpp HelloCarbideAppUi.cpp HelloCarbide.cpp<br>
-     /*&amp; END_PROJECT_CONTENT &amp;*/</p>
-     <p class="listing">/*&amp; START_LINKAGE_INFORMATION &amp;*/<br>
-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
-     LIBRARY euser.lib apparc.lib cone.lib eikcore.lib avkon.lib commonengine.lib<br>
-     LIBRARY efsrv.lib estor.lib<br>
-     /*&amp; END_LINKAGE_INFORMATION &amp;*/</p>
-   <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html><head>
+<title>Exporting project(s) to MMP/Bld.inf files in Tasks</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+   </head>
+   <body>
+
+   <div class="step">
+     <h2>Exporting project(s) to MMP/Bld.inf files</h2>
+     <p>
+       The command-line Symbian OS toolchain requires a component description
+       file (<span class="code">Bld.Inf</span>) and one or more project definition files
+       (<span class="code">.mmp</span>) to build a project. The export command allows you to create
+       these files for your projects.       </p>
+     <h4>
+       To export project(s) to a <span class="code">Bld.Inf</span> and/or <span class="code">MMP</span>
+       file:       </h4>
+     <ol> 
+       <li> 
+         Click <span class="code">File &gt; Export...</span> to get a list of the
+         available export wizards: 
+         <p>
+           OR         </p> 
+	     <p>
+	        Click <span class="code">Export</span> from the pop-up menus of the
+	        <span class="code">C/C++ Projects</span> and <span class="code">Navigator</span> views to get a
+		      list of the available export wizards:         </p> 
+	     <div class="Figure">
+		      
+	        <p class="Image"><a name=""><img src="../images/export1.gif" alt="" width="470" height="550"  border="0"></a></p>
+  </div> 
+       </li> 
+	    <li>Select <span class="code">Symbian MMP/Bld.Inf</span> and click
+		    <span class="code">Next</span> to go to the <span class="code">Symbian Projects</span> page: 
+	      <p></p> 
+	      <div class="Figure">
+		      
+	         <p class="Image"><a name=""><img src="../images/export2.gif" alt="" width="470" height="550"  border="0"></a></p>
+  </div> 
+	    </li> 
+	    <li> 
+		    Select the project(s) you intend to export from the list of
+		    <span class="code">Symbian Projects</span>.	    </li> 
+	    <li> 
+		    Click <span class="code">Next</span> to go to the <span class="code">SDKs and Build Configurations Selection</span> page: 
+	      <div class="Figure">
+		      
+	         <p class="Image"><a name=""><img src="../images/export3.gif" alt="" width="470" height="550"  border="0"></a></p>
+  </div> 
+	    </li> 
+	    <li> 
+		    Select at least one build configuration for each project in the
+		    left-hand pane from the list of available SDKs and build configurations in the
+		    right-hand pane. By default, all the build configurations chosen during the
+		    last export are selected. If a project is being exported for the first time, no
+		    build configurations are selected. 
+	      <p>
+	         The build configurations chosen for a project are distinguished using
+		      guard macros in the <span class="code">MMP</span> file. The guard macros are placed around
+		      the <span class="code">MMP</span> file statements containing resources or build setting,
+		      only valid for a subset of the chosen build configurations.	      </p> 
+	      <p>
+	         There are cases where guard macros may not be able to distinguish
+		      between two build configurations. The export wizard shows a conflict when two
+		      such ambiguous build configurations are selected by the user.	      </p> 
+	      <p>
+	         The combination of build configurations which results in a conflict
+		      are as follows:	      </p> 
+  
+		  <ul> 
+		    <li> 
+		      <p>
+		        Any two build configurations that differ only in the build
+		        variant (UDEB/UREL). For example, "UIQ 3.0 Phone (GCCE) Debug" and "UIQ 3.0
+		        Phone (GCCE) Release" configurations will result in a conflict, as they differ
+		        only in the build variant.	           </p> 
+	        </li> 
+		     <li> 
+		        <p>
+		          Any two build configurations, of which one is user-defined based
+			       on the other using the <span class="code">Manage</span> option in the <span class="code">C/C++
+			         Build properties</span> view of the project.		        </p> 
+			    <p>
+			      <i>For more information on managing build configurations,
+			      refer to the CDT user guide.</i>		        </p> 
+		     </li> 
+	      </ul>
+  
+		  <p>
+		    The wizard will change the build settings in the <span class="code">MMP</span>
+		    file based on the chosen build configuration. If more than one build
+		    configuration which require different build settings are chosen, guard macros
+		    are used to determine the build settings. For example, if you want to change
+		    the <span class="code">SECUREID</span> option for all the <code>EKA2 build
+		    configurations, the wizard will append the following lines into the
+		    <span class="code">MMP</span> file:	      </code></p><code> 
+	      <p class="CodeBlock">#if def EKA2<br>&nbsp;&nbsp;SECUREID 0x00301<br>#endif</p> 
+	      <p>
+	         Where <code>EKA2 is the guard macro for all the build
+		      configurations designed for the EKA2 kernel. The above <span class="code">MMP</span> file
+		      statements check whether the <code>EKA2 guard macro is defined, and if
+		      it is, change the <code>SECUREID option accordingly.	      </code></code></code></p> 
+	    </code></li><code><code><code><code> 
+	    <li> 
+		    Click <span class="code">Next</span> to go to the <span class="code">MMP File and Bld.inf
+		      File</span> page: 
+	      <div class="Figure">		    
+	        <div align="center"><a name=""><img src="../images/export4.gif" alt="" width="470" height="550"  border="0"></a></div>
+	      </div> 
+	      <ol type="a">
+	        <li>
+	           Type the <span class="code">MMP</span> file location in the <span class="code">MMP
+		          File</span> field, or click <span class="code">Browse</span> to select the
+	           <span class="code">MMP</span> file for each project listed above. 
+	           <p>
+	             By default, the <span class="code">MMP</span> file is exported to one of the
+		          following locations in the order listed below:	           </p>
+	           <ul>
+	             <li> The location where the project was exported the last time. </li>
+	             <li> The group folder of the exported project, if it exists. </li>
+	             <li> The exported project's root directory. </li>
+              </ul>
+	        </li>
+	        <li>
+	           If you select the <span class="code">Export Bld.inf file</span> option, then
+		        type the <span class="code">Bld.Inf</span> file location in the <span class="code">Bld.inf
+		          File</span> field, or click <span class="code">Browse</span> to select the
+	           <span class="code">Bld.Inf</span> file. 
+	           <p>
+	             If you do not select the <span class="code">Export Bld.inf file</span> option,
+		          then you need not specify the <span class="code">Bld.Inf</span> file location.	           </p>
+	           <p>
+	             By default, the <span class="code">Bld.Inf</span> file is exported to one of the
+		           following locations in the order listed below:	           </p>
+	           <ul>
+	             <li>
+	               The location where the <span class="code">Bld.Inf</span> was created when the
+		             project was last exported to an <span class="code">MMP</span> file. </li>
+	             <li> The <span class="code">MMP</span> file location.</li>
+              </ul>
+	        </li>
+          </ol>
+	    </li> 
+       <li>Click Next to go to the Other Makefiles page where you can specify extra Makefiles to invoke from bld.inf </li> 
+  
+	 <blockquote>
+	   <p align="center"><img src="../images/export4a.gif" width="470" height="550"></p>
+    </blockquote>
+       <li>Click Next to open the Scalable Icon Makefiles page where you can specify the Makefiles used to generate scalable icon files.</li>
+	   <p align="center"><img src="../images/export4b.gif" width="470" height="550"></p>
+        <li>Click <span class="code">Next</span> to go to the <span class="code">PRJ_EXPORTS</span> page, to specify the list of files to be copied from the source directories to
+            the releasables directories while building the project:
+            <div class="Figure">
+              
+              <p class="Image"><a name=""><img src="../images/export5.gif" alt="" width="470" height="550"  border="0"></a></p>
+            </div>
+          <p>
+             <i>Note that this page is displayed only if you have selected
+             the Export Bld.inf file option in the previous page.</i>          </p>
+        </li>
+        <li> 
+            Type the <span class="code">Source</span> and <span class="code">Target</span>
+            locations of the file to be copied, and click <span class="code">Add</span> to append
+            the source-target pair to the <span class="code">PRJ_EXPORTS</span> list. You can use
+            <span class="code">Browse</span> to specify the source file and its target location. If
+            the target location for the file is not specified, it will be copied to
+            <span class="code">epoc32\include</span> directory. 
+          <p>
+             Note that the contents of the <span class="code">PRJ_EXPORTS</span> list is
+              exactly the same as it appears in the <code>PRJ_EXPORTS section of the
+             <span class="code">Bld.Inf</span> file.          </code></p> 
+        </li><code>
+        <li> 
+            If you want to modify or delete any entry from the
+            <span class="code">PRJ_EXPORTS</span> list, select the entry and click
+            <span class="code">Modify</span> or <span class="code">Delete</span>.        </li>
+        <li> 
+            Click <span class="code">Next</span> to go to the <span class="code">MMP Preview</span>
+            page: 
+          <div class="Figure">
+              
+             <p class="Image"><a name=""><img src="../images/export6.gif" alt="" width="470" height="550"  border="0"></a></p>
+      </div> 
+        </li>
+        <li> 
+            Select a project from the list of projects to be exported, to see a
+            preview of the <span class="code">MMP</span> file in the pane below. You can edit the
+            contents if required.        </li>
+        <li> 
+            Click <span class="code">Finish</span> to complete the export process. The
+            wizard will create the managed <span class="code">MMP</span> file and <code class="filename">Bld.inf
+            file in their specified locations.
+          <p>
+             A managed <span class="code">MMP</span> file contains the same content as a
+              standard <span class="code">MMP</span> file would, but the contents are organised into
+              following managed sections using special tags:          </p> 
+      
+		  <ul> 
+		    <li> 
+		      <p>
+		        Binary Build Information	           </p> 
+            </li> 
+             <li> 
+                <p>
+                  Search Path                </p> 
+             </li> 
+             <li> 
+                <p>
+                  Project Content Managed                </p> 
+             </li> 
+             <li> 
+                <p>
+                  Linkage                </p> 
+             </li> 
+             <li> 
+                <p>
+                  Customization                </p> 
+             </li> 
+          </ul>
+      
+		  <p>
+		    You will be notified in case of any errors during the updated
+		    process, which results in not creating the <span class="code">MMP</span> or
+		    <span class="code">Bld.Inf</span> files.</p> 
+        </code></li>
+     </code></code></code></code></code></ol>
+   </div><code><code><code><code><code><code class="filename">
+     <p>
+       The following <span class="code">MMP</span> file generated by the wizard, shows how
+       its content is organised using managed sections:       </p>
+     <h4 class="listing">// HelloCarbide.mmp</h4>
+     <p class="listing">/*&amp; START_BINARY_BUILD &amp;*/<br>
+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
+     CAPABILITY READUSERDATA<br>
+     TARGET HelloCarbide.exe<br>
+     TARGETTYPE exe<br>
+     UID 0x00000000 0xe4d95f85<br>
+     VENDORID 0x00000000<br>
+     SECUREID 0xE4D95F85<br>
+     /*&amp; END_BINARY_BUILD &amp;*/</p>
+     <p class="listing">/*&amp; START_SEARCH_PATHS &amp;*/<br>
+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
+     SYSTEMINCLUDE \epoc32\include \epoc32\include\variant \epoc32\include\oem<br>
+     USERINCLUDE ..\inc ..\data<br>
+     /*&amp; END_SEARCH_PATHS &amp;*/</p>
+     <p class="listing">/*&amp; START_PROJECT_CONTENT &amp;*/<br>
+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
+     SOURCEPATH ..\data<br>
+     START RESOURCE HelloCarbide.rss<br>
+     TARGETPATH resource\apps<br>
+     HEADER<br>
+     END<br>
+     START RESOURCE HelloCarbide_reg.rss<br>
+     TARGETPATH private\10003a3f\apps<br>
+     HEADER<br>
+     END<br>
+     SOURCEPATH ..\src<br>
+     SOURCE Waving.cpp HelloCarbideDocument.cpp HelloCarbideApplication.cpp<br>
+     SOURCE HelloCarbideAppView.cpp HelloCarbideAppUi.cpp HelloCarbide.cpp<br>
+     /*&amp; END_PROJECT_CONTENT &amp;*/</p>
+     <p class="listing">/*&amp; START_LINKAGE_INFORMATION &amp;*/<br>
+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.<br>
+     LIBRARY euser.lib apparc.lib cone.lib eikcore.lib avkon.lib commonengine.lib<br>
+     LIBRARY efsrv.lib estor.lib<br>
+     /*&amp; END_LINKAGE_INFORMATION &amp;*/</p>
+   <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </code></code></code></code></code></code></body>
+</html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,43 +1,43 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Creating an MBM File in Modifying Resources</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-   <body>
-<h2>Creating an MBM File</h2>
-<p>
-		Symbian OS programs typically store bitmaps for application icons or
-		other purposes in the Symbian OS multi-bitmap (MBM) file format, as described
-		in <a href="../concepts/MBMDefWizard.html">MBM File</a>. The Edit MBM/MIF Contents or Edit MBM Contents window allows you to create an MBM file.</p>
-	 <div class="step">
-	   <h4>
-		  To create an MBM file</h4>
-   </div>
-	 <ol> 
-		<li> 
-		 In the Symbian Project Navigator view double-click  a .mmp file (Figure 1) to open the <b>MMP Editor</b> (Figure 2).
-		   <p align="center"><img src="projects/images/AIF_editor_mmp_symprojnav.png" width="271" height="261" /></p>
-		   <p align="center" class="figure">Figure 1- MMP File </p>
-	   </li>
-	    <li>
-       In the <b>Sources</b> tab under the <b>Resources</b> group, select <b>Bitmaps</b> </li>
-
-	    <p align="center"><img src="projects/images/mmpeditor_addbitmap.png" width="581" height="383" /></p>
-	 <p align="center" class="figure">Figure 2 - MMP Editor</p>
-	 <li>Click <b>Add</b> to display the <b>Edit MBM Contents</b> window (Figure 3)</li>
- 
-	 <p align="center"><img src="projects/images/MBM_editor.png" width="900" height="600" /></p>
-	 <p class="figure">Figure 3 - MBM Editor  </p>
-	 <p>You can now use the MBM Editor to add bitmaps, with and without masks, to the MBM file.</p>
-    <li>Enter a name for the mbm file in the <b>Target file</b> text box.</li>
-	<li>Add bitmap files to the editor by using the <b>Add From Project</b> or <b>Add From Filesystem</b> buttons.</li>
-    </ol>
-	   <p>Additional information for the MBM editor fields is provided in <a href="../reference/MBMEditor.html">MBM Editor</a>.</p>
-	   <h5>Related concepts</h5>
-	   <ul>
-     <li><a href="../concepts/MBMDefWizard.html">MBM File</a> </li>
-   </ul>
-   <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-   </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+<title>Creating an MBM File in Modifying Resources</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+   <body>
+<h2>Creating an MBM File</h2>
+<p>
+		Symbian OS programs typically store bitmaps for application icons or
+		other purposes in the Symbian OS multi-bitmap (MBM) file format, as described
+		in <a href="../concepts/MBMDefWizard.html">MBM File</a>. The Edit MBM/MIF Contents or Edit MBM Contents window allows you to create an MBM file.</p>
+	 <div class="step">
+	   <h4>
+		  To create an MBM file</h4>
+   </div>
+	 <ol> 
+		<li> 
+		 In the <a href="../reference/view_sym_proj_nav.htm">Symbian Project Navigato</a>r view double-click  a .mmp file (Figure 1) to open the <b>MMP Editor</b> (Figure 2).
+	      <p align="center"><img src="projects/images/AIF_editor_mmp_symprojnav.png" width="271" height="261" /></p>
+		   <p align="center" class="figure">Figure 1- MMP File </p>
+	   </li>
+       <li>
+       In the <b>Sources</b> tab under the <b>Resources</b> group, select <b>Bitmaps</b> </li>
+
+	    <p align="center"><img src="projects/images/mmpeditor_addbitmap.png" width="581" height="383" /></p>
+	 <p align="center" class="figure">Figure 2 - MMP Editor</p>
+	 <li>Click <b>Add</b> to display the <b>Edit MBM Contents</b> window (Figure 3)</li>
+ 
+	 <p align="center"><img src="projects/images/MBM_editor.png" width="900" height="600" /></p>
+	 <p class="figure">Figure 3 - MBM Editor  </p>
+	 <p>You can now use the MBM Editor to add bitmaps, with and without masks, to the MBM file.</p>
+    <li>Enter a name for the mbm file in the <b>Target file</b> text box.</li>
+	<li>Add bitmap files to the editor by using the <b>Add From Project</b> or <b>Add From Filesystem</b> buttons.</li>
+    </ol>
+	   <p>Additional information for the MBM editor fields is provided in <a href="../reference/MBMEditor.html">MBM Editor</a>.</p>
+	   <h5>Related concepts</h5>
+	   <ul>
+     <li><a href="../concepts/MBMDefWizard.html">MBM File</a> </li>
+   </ul>
+   <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </body>
+   </html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html	Thu Feb 18 11:17:02 2010 -0600
@@ -27,7 +27,7 @@
 	   </li>
 		<div class="Figure">
 
-		   <p class="Image"><img src="../images/SDKPreferences.png" width="696" height="583" /></p>
+		   <p class="Image"><img src="../images/SDKPreferences.png" width="740" height="546" /></p>
 	   </div>
 		<p class="note"><b>NOTE</b> SDKs shown in <span class="style2">red</span> indicate a problem, for example no <span class="style1">EPOCROOT</span>. </p>
 
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,69 +1,69 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Run Mode Debugger Settings</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Run Mode On-Device Debugging</h2>
-<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
-<ol>
-  <li><b>Install device connection software</b></li>
-  <li><a href="run_mode_debug_01.htm">Install Perl</a></li>
-  <li><a href="run_mode_debug_02.htm">Install an SDK</a></li>
-  <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li>
-  <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li>
-  <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li>
-  <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li>
-  <li><a href="run_mode_debug_07.htm">Configure TRK connection on the device</a></li>
-  <li><a href="run_mode_debug_08.htm">Create a launch configuration</a></li>
-</ol>
-<div class="step">
-<h4><a name="runInstall" id="runInstall">	</a>Install Device Connection Software</h4>
-<p>The two choices for connecting are Bluetooth and PC Suite. </p>
-<h5>BlueTooth</h5>
-<ol>
-  <li>System requirements: </li>
-  <ul>
-    <li>Administration rights on your computer</li>
-    <li> BT dongle attached to your computer</li>
-    <li>Bluetooth installer to install the drivers</li>
-  </ul>
-  <li>Install the Bluetooth dongle to a USB port</li>
-  <li>Install the drivers from the Bluetooth CD</li>
-  <li>Click on the Bluetooth icon in your system tray and run the Bluetooth setup</li>
-  <li>Right click on the Bluetooth icon in the System tray and select Advanced Configuration</li>
-  <li>Click the Accessibility tab
-    <ol type="a">
-      <li>Check the option &ldquo;Let other Bluetooth devices discover this computer&rdquo;</li>
-        <li>Set the option under &ldquo;Allow&rdquo; to &ldquo;All Devices&rdquo;</li>
-      </ol>
-    </li>
-</ol>
-<p class="note"><b>NOTE</b> The Nokia PC image includes the Microsoft Bluetooth drivers which do not support serial emulation over Bluetooth. You need to download and install the drivers provided by the Bluetooth manufacturer to connect to a device. </p>
-<h5>Nokia PC Suite 6.8</h5>
-<ol>
-  <li>Install <a href="http://www.nokiausa.com/support/pcsuite/main.html%20or%20http://europe.nokia.com/A4144903">PC Suite</a> (or later version)    
-    <p>Launch the PC Suite installer and follow the onscreen instructions to install the software. When finished, a <b>Get Connected</b> wizard should appear</p>
-  </li>
-  <li> Press Next</li>
-  <li>In the &quot;Select your connection type&quot; window select &quot;Cable Connection&quot; and press Next</li>
-  <li>You will be prompted to connect the phone via the USB cable</li>
-  <li>Connect the phone and continue with  onscreen instructions</li>
-  <li>After installation your  phone should be listed</li>
-  <li>Click Finish</li>
-  <li>Select PC suite on your phone</li>
-  <p>The Nokia PC Suite window should appear</p>
-  <li>Select the Manage Connections icon</li>
-  <li>Uncheck all the connections available</li>
-  <li>Click Ok</li>
-  <p>PC Suite is now ready to use.</p>
-</ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Run Mode Debugger Settings</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Run Mode On-Device Debugging</h2>
+<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
+<ol>
+  <li><b>Install device connection software</b></li>
+  <li><a href="run_mode_debug_01.htm">Install Perl</a></li>
+  <li><a href="run_mode_debug_02.htm">Install an SDK</a></li>
+  <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li>
+  <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li>
+  <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li>
+  <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li>
+  <li><a href="run_mode_debug_07.htm">Configure TRK connection on the device</a></li>
+  <li><a href="run_mode_debug_08.htm">Create a launch configuration</a></li>
+</ol>
+<div class="step">
+<h4><a name="runInstall" id="runInstall">	</a>Install Device Connection Software</h4>
+<p>The two choices for connecting are Bluetooth and PC Suite. </p>
+<h5>BlueTooth</h5>
+<ol>
+  <li>System requirements: </li>
+  <ul>
+    <li>Administration rights on your computer</li>
+    <li> BT dongle attached to your computer</li>
+    <li>Bluetooth installer to install the drivers</li>
+  </ul>
+  <li>Install the Bluetooth dongle to a USB port</li>
+  <li>Install the drivers from the Bluetooth CD</li>
+  <li>Click on the Bluetooth icon in your system tray and run the Bluetooth setup</li>
+  <li>Right click on the Bluetooth icon in the System tray and select Advanced Configuration</li>
+  <li>Click the Accessibility tab
+    <ol type="a">
+      <li>Check the option &ldquo;Let other Bluetooth devices discover this computer&rdquo;</li>
+        <li>Set the option under &ldquo;Allow&rdquo; to &ldquo;All Devices&rdquo;</li>
+      </ol>
+    </li>
+</ol>
+<p class="note"><b>NOTE</b> The Nokia PC image includes the Microsoft Bluetooth drivers which do not support serial emulation over Bluetooth. You need to download and install the drivers provided by the Bluetooth manufacturer to connect to a device. </p>
+<h5>Nokia PC Suite</h5>
+<ol>
+  <li>Install <a href="http://www.nokiausa.com/support/pcsuite/main.html%20or%20http://europe.nokia.com/A4144903">PC Suite</a> (or later version)    
+    <p>Launch the PC Suite installer and follow the onscreen instructions to install the software. When finished, a <b>Get Connected</b> wizard should appear</p>
+  </li>
+  <li> Press Next</li>
+  <li>In the &quot;Select your connection type&quot; window select &quot;Cable Connection&quot; and press Next</li>
+  <li>You will be prompted to connect the phone via the USB cable</li>
+  <li>Connect the phone and continue with  onscreen instructions</li>
+  <li>After installation your  phone should be listed</li>
+  <li>Click Finish</li>
+  <li>Select PC suite on your phone</li>
+  <p>The Nokia PC Suite window should appear</p>
+  <li>Select the Manage Connections icon</li>
+  <li>Uncheck all the connections available</li>
+  <li>Click Ok</li>
+  <p>PC Suite is now ready to use.</p>
+</ol>
+</div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -33,7 +33,7 @@
   <li>UIQ 3.0</li>
   <li>Series 60 cust kits </li>
   <li>Techview Development kits
-    </p>
+    <p></p>
   </li>
 </ul>
 </ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,28 +1,28 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Disabling an Eventpoint</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Disabling an Eventpoint</h2>
-<p>Disable an eventpoint to prevent it from performing its specified action. The disabled eventpoint remains at the source-code line at which you set it, so that you can enable it later. Disabling the eventpoint is easier than clearing it and re-creating it from scratch.</p>
-<div class="step">
-  <h4>To disable an eventpoint</h4>
-  <ol>
-    <li>Select the eventpoint to disable</li>
-    <p>Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.</p>
-    <li>Click Debug &gt; Disable Eventpoint</li>
-    <p>The Disable Eventpoint menu appears.</p>
-    <li>From the menu, click the Disable Eventpoint command, where Eventpoint is the type of eventpoint that you want to disable</li>
-    <p>The enabled eventpoint icon changes to a disabled eventpoint icon (shown at left). The disabled eventpoint icon indicates that the eventpoint does not perform its specified action.<br />
-</p>
-  </ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Disabling an Eventpoint</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Disabling an Eventpoint</h2>
+<p>Disable an eventpoint to prevent it from performing its specified action. The disabled eventpoint remains at the source-code line at which you set it, so that you can enable it later. Disabling the eventpoint is easier than clearing it and re-creating it from scratch.</p>
+<div class="step">
+  <h4>To disable an eventpoint</h4>
+  <ol>
+    <li>Select the eventpoint to disable</li>
+    <p>Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.</p>
+    <li>Click Debug &gt; Disable Eventpoint</li>
+    <p>The Disable Eventpoint menu appears.</p>
+    <li>From the menu, click the Disable Eventpoint command, where Eventpoint is the type of eventpoint that you want to disable</li>
+    <p>The enabled eventpoint icon changes to a disabled eventpoint icon (shown at left). The disabled eventpoint icon indicates that the eventpoint does not perform its specified action.<br />
+</p>
+  </ol>
+</div>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,27 +1,27 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Enabling an Eventpoint</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Enabling an Eventpoint</h2>
-<p>Enable an eventpoint to have it perform its specified action during program execution. Enabling an eventpoint that you previously disabled is easier than clearing it and re-creating it from scratch.</p>
-<div class="step">
-  <h4>To enable an eventpoint</h4>
-  <ol>
-    <li>Select the eventpoint that you want to enable</li>
-    <p>Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.</p>
-    <li>Click Debug &gt; Enable Eventpoint</li>
-    <p>The Enable Eventpoint menu appears.</p>
-    <li>From the menu, click the Enable Eventpoint command, where Eventpoint is the type of eventpoint that you want to enable</li>
-    <li>The disabled eventpoint icon changes to its original eventpoint icon. The enabled eventpoint icon indicates that the eventpoint will perform its specified action.</li>
-  </ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Enabling an Eventpoint</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Enabling an Eventpoint</h2>
+<p>Enable an eventpoint to have it perform its specified action during program execution. Enabling an eventpoint that you previously disabled is easier than clearing it and re-creating it from scratch.</p>
+<div class="step">
+  <h4>To enable an eventpoint</h4>
+  <ol>
+    <li>Select the eventpoint that you want to enable</li>
+    <p>Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.</p>
+    <li>Click Debug &gt; Enable Eventpoint</li>
+    <p>The Enable Eventpoint menu appears.</p>
+    <li>From the menu, click the Enable Eventpoint command, where Eventpoint is the type of eventpoint that you want to enable</li>
+    <li>The disabled eventpoint icon changes to its original eventpoint icon. The enabled eventpoint icon indicates that the eventpoint will perform its specified action.</li>
+  </ol>
+</div>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_setting.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_setting.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,35 +1,35 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Setting a Conditional Eventpoint</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Setting a Conditional Eventpoint</h2>
-<p>Use the Condition column of the Breakpoints view to set a conditional eventpoint. A conditional eventpoint has an associated conditional expression. The debugger evaluates the expression to determine whether the eventpoint performs its specified action.</p>
-<p>A conditional eventpoint behaves in two different ways:</p>
-<ul>
-  <li>If the expression evaluates to <span class="code">true</span> (a non-zero value), the eventpoint performs its specified action.</li>
-  <li>If the expression evaluates to <span class="code">false</span> (a zero value), the eventpoint does not perform its specified action.</li>
-</ul>
-<div class="step">
-  <h4>To set a conditional eventpoint</h4>
-  <ol>
-    <li>Set an eventpoint that you want to associate with a conditional expression</li>
-    <li>Click Windows &gt; Show View &gt; Breakpoints</li>
-    <p>A Breakpoints view appears.</p>
-    <li>Find the eventpoint that you want to associate with a conditional expression</li>
-    <li>Double-click the Condition column in alignment with the eventpoint</li>
-    <li>Enter an expression in the Condition text box</li>
-    <p>During subsequent debugging sessions, the debugger evaluates the expression to determine whether the eventpoint performs its specified action.</p>
-  </ol>
-</div>
-<p class="note"><b>NOTE</b> Alternatively, drag-and-drop an expression from a source view or from the Expression view into the Breakpoints view.<br />
-</p>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Setting a Conditional Eventpoint</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Setting a Conditional Eventpoint</h2>
+<p>Use the Condition column of the <a href="../../debugger/breakpoints/viewing_breakpoints.htm">Breakpoints</a> view to set a conditional eventpoint. A conditional eventpoint has an associated conditional expression. The debugger evaluates the expression to determine whether the eventpoint performs its specified action.</p>
+<p>A conditional eventpoint behaves in two different ways:</p>
+<ul>
+  <li>If the expression evaluates to <span class="code">true</span> (a non-zero value), the eventpoint performs its specified action.</li>
+  <li>If the expression evaluates to <span class="code">false</span> (a zero value), the eventpoint does not perform its specified action.</li>
+</ul>
+<div class="step">
+  <h4>To set a conditional eventpoint</h4>
+  <ol>
+    <li>Set an eventpoint that you want to associate with a conditional expression</li>
+    <li>Click Windows &gt; Show View &gt; Breakpoints</li>
+    <p>A Breakpoints view appears.</p>
+    <li>Find the eventpoint that you want to associate with a conditional expression</li>
+    <li>Double-click the Condition column in alignment with the eventpoint</li>
+    <li>Enter an expression in the Condition text box</li>
+    <p>During subsequent debugging sessions, the debugger evaluates the expression to determine whether the eventpoint performs its specified action.</p>
+  </ol>
+</div>
+<p class="note"><b>NOTE</b> Alternatively, drag-and-drop an expression from a source view or from the Expression view into the Breakpoints view.<br />
+</p>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_viewing.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_viewing.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,24 +1,24 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Viewing Eventpoint Properties</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Viewing Eventpoint Properties</h2>
-<p>After you set an eventpoint, you can view and modify its properties.</p>
-<div class="step">
-  <h4>To view properties for an eventpoint</h4>
-  <ol>
-    <li>Select its name in the Breakpoints view </li>
-    <li>Click Breakpoints &gt; Breakpoint Properties<br />
-</li>
-  </ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Viewing Eventpoint Properties</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Viewing Eventpoint Properties</h2>
+<p>After you set an eventpoint, you can view and modify its properties.</p>
+<div class="step">
+  <h4>To view properties for an eventpoint</h4>
+  <ol>
+    <li>Select its name in the Breakpoints view </li>
+    <li>Click Breakpoints &gt; Breakpoint Properties<br />
+</li>
+  </ol>
+</div>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,30 +1,30 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Log Point</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Log Point</h2>
-<p>  A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.</p>
-<h5>Related tasks</h5>
-<ul>
-  <li><a href="pause_point_set.htm">Setting a Pause Point</a></li>
-  <li><a href="pause_point_clear.htm">Clearing a Pause Point </a></li>
-</ul>
-<p>&nbsp;</p>
-<div class="step"><h5>Clearing a Log Point</h5>
-  <p>To clear a Log Point, follow these steps:</p>
-  <ol>
-    <li>Select the Log Point that you want to clear.</li>
-    <p>Click the cursor on the line of source code that has the Log Point, or select the Log Point by name in the Breakpoints window.</p>
-    <li>Click Debug &gt; Clear Eventpoint &gt; Clear Log Point.</li>
-  </ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Log Point</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Log Point</h2>
+<p>  A <b>Log Point</b> logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.</p>
+<h5>Related tasks</h5>
+<ul>
+  <li><a href="pause_point_set.htm">Setting a Pause Point</a></li>
+  <li><a href="pause_point_clear.htm">Clearing a Pause Point </a></li>
+</ul>
+<p>&nbsp;</p>
+<div class="step"><h5>Clearing a Log Point</h5>
+  <p>To clear a Log Point, follow these steps:</p>
+  <ol>
+    <li>Select the Log Point that you want to clear.</li>
+    <p>Click the cursor on the line of source code that has the Log Point, or select the Log Point by name in the Breakpoints window.</p>
+    <li>Click Debug &gt; Clear Eventpoint &gt; Clear Log Point.</li>
+  </ol>
+</div>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,40 +1,40 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Log Point</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Log Point</h2>
-<p>  A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.</p>
-<h5>Related tasks</h5>
-<ul>
-  <li><a href="pause_point_set.htm">Setting a Pause Point</a></li>
-  <li><a href="pause_point_clear.htm">Clearing a Pause Point </a></li>
-</ul>
-<p>&nbsp;</p>
-<div class="step">
-  <h5>Setting a Log Point</h5>
-  <p>To set a Log Point, follow these steps:</p>
-  <ol>
-    <li>Click the cursor on the line of source code at which you want to set the Log Point.</li>
-    <li>Click Debug &gt; Set Eventpoint &gt; Set Log Point.</li>
-    <li>Enter the text of your log message in the Message text box.</li>
-    <li>Check at least one of these checkboxes:</li>
-    <ul><li><b>Log Message</b>&mdash;check to have the IDE display your message in a Message window when program execution reaches the Log Point</li>
-    <li><b>Speak Message</b> (Windows OS)&mdash;check to have the IDE use the sound capabilities of the host operating system to speak the message that you enter in the Message text box.</li>
-    <p class="note"><b>NOTE</b> (Windows) Install the Speech software development kit (SDK) in order to have the Speak Message feature work correctly.</p>
-    <li><b>Treat as Expression</b>&mdash;check to have the IDE evaluate the text you enter in the Message text box as an expression. For example, if you enter the name of a variable in the Message text, the debugger writes the value of that variable in the console output window.</li>
-    <li><b>Stop in Debugger</b>&mdash;check to stop program execution in the debugger</li>
-    </ul>
-    <li>Click the OK button to confirm your settings.</li>
-  </ol>
-</div>
-<p>Example use: If you want to display the value of a variable each time some code is executed, set a log point, check the Log Message and Treat as expression boxes and enter the variable name in the edit box, then click OK.</p>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Log Point</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Log Point</h2>
+<p>  A <b>Log Point</b> logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.</p>
+<h5>Related tasks</h5>
+<ul>
+  <li><a href="pause_point_set.htm">Setting a Pause Point</a></li>
+  <li><a href="pause_point_clear.htm">Clearing a Pause Point </a></li>
+</ul>
+<p>&nbsp;</p>
+<div class="step">
+  <h5>Setting a Log Point</h5>
+  <p>To set a Log Point, follow these steps:</p>
+  <ol>
+    <li>Click the cursor on the line of source code at which you want to set the Log Point.</li>
+    <li>Click Debug &gt; Set Eventpoint &gt; Set Log Point.</li>
+    <li>Enter the text of your log message in the Message text box.</li>
+    <li>Check at least one of these checkboxes:</li>
+    <ul><li><b>Log Message</b>&mdash;check to have the IDE display your message in a Message window when program execution reaches the Log Point</li>
+    <li><b>Speak Message</b> (Windows OS)&mdash;check to have the IDE use the sound capabilities of the host operating system to speak the message that you enter in the Message text box.</li>
+    <p class="note"><b>NOTE</b> (Windows) Install the Speech software development kit (SDK) in order to have the Speak Message feature work correctly.</p>
+    <li><b>Treat as Expression</b>&mdash;check to have the IDE evaluate the text you enter in the Message text box as an expression. For example, if you enter the name of a variable in the Message text, the debugger writes the value of that variable in the console output window.</li>
+    <li><b>Stop in Debugger</b>&mdash;check to stop program execution in the debugger</li>
+    </ul>
+    <li>Click the OK button to confirm your settings.</li>
+  </ol>
+</div>
+<p>Example use: If you want to display the value of a variable each time some code is executed, set a log point, check the Log Message and Treat as expression boxes and enter the variable name in the edit box, then click OK.</p>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,34 +1,34 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Pause Point</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Pause Point</h2>
-<p>  A Pause Point suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.</p>
-<h5>Related tasks</h5>
-<ul>
-  <li><a href="log_point_set.htm">Setting a Log Point</a></li>
-  <li><a href="log_point_clear.htm">Clearing a Log Point </a></li>
-</ul>
-<p>&nbsp;</p>
-<p></p>
-  <div class="step">
-  <h5>Clearing a Pause Point</h5>
-  <p>To clear a Pause Point, follow these steps:</p>
-  <ol>
-    <li>Select the Pause Point that you want to clear.</li>
-    <p>Click the cursor on the line of source code that has the Pause Point, or select the Pause Point by name in the Breakpoints window.</p>
-    <li>Click Debug &gt; Clear Eventpoint &gt; Clear Pause Point.<br />
-    </li>
-  </ol>
-</div>
-  <p></p>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Pause Point</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Pause Point</h2>
+<p>  A <b>Pause Point</b> suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.</p>
+<h5>Related tasks</h5>
+<ul>
+  <li><a href="log_point_set.htm">Setting a Log Point</a></li>
+  <li><a href="log_point_clear.htm">Clearing a Log Point </a></li>
+</ul>
+<p>&nbsp;</p>
+<p></p>
+  <div class="step">
+  <h5>Clearing a Pause Point</h5>
+  <p>To clear a Pause Point, follow these steps:</p>
+  <ol>
+    <li>Select the Pause Point that you want to clear.</li>
+    <p>Click the cursor on the line of source code that has the Pause Point, or select the Pause Point by name in the Breakpoints window.</p>
+    <li>Click Debug &gt; Clear Eventpoint &gt; Clear Pause Point.<br />
+    </li>
+  </ol>
+</div>
+  <p></p>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,32 +1,32 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Pause Point</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Pause Point</h2>
-<p>  A Pause Point suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.</p>
-<h5>Related tasks</h5>
-<ul>
-  <li><a href="log_point_set.htm">Setting a Log Point</a></li>
-  <li><a href="log_point_clear.htm">Clearing a Log Point </a></li>
-</ul>
-<p>&nbsp;</p>
-<div class="step">
-    <h5>Setting a Pause Point</h5>
-    <p>To set a Pause Point, follow these steps:</p>
-    <ol>
-      <li>Click the cursor on the line of source code at which you want to set the Pause Point.</li>
-      <li>Click Debug &gt; Set Eventpoint &gt; Set Pause Point.</li>
-    </ol>
-</div>
-  <p></p>
-  <p></p>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Pause Point</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Pause Point</h2>
+<p>  A <b>Pause Point</b> suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.</p>
+<h5>Related tasks</h5>
+<ul>
+  <li><a href="log_point_set.htm">Setting a Log Point</a></li>
+  <li><a href="log_point_clear.htm">Clearing a Log Point </a></li>
+</ul>
+<p>&nbsp;</p>
+<div class="step">
+    <h5>Setting a Pause Point</h5>
+    <p>To set a Pause Point, follow these steps:</p>
+    <ol>
+      <li>Click the cursor on the line of source code at which you want to set the Pause Point.</li>
+      <li>Click Debug &gt; Set Eventpoint &gt; Set Pause Point.</li>
+    </ol>
+</div>
+  <p></p>
+  <p></p>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,25 +1,25 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Clearing a Trace Collection</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Clearing a Trace Collection</h2>
-<p>Clear a  Trace Collection  eventpoint when you are finished collecting trace data.</p>
-<div class="step">
-  <h4>Clearing a Trace Collection On Eventpoint</h4>
-    <p>To clear a Trace Collection  eventpoint, follow these steps:</p>
-  <ol>
-    <li>Select the Trace Collection  eventpoint that you want to clear</li>
-    <p>Click the cursor on the line of source code that has the Trace Collection  eventpoint, or select the Trace Collection  eventpoint by name in the Breakpoints view.</p>
-    <li>Click Debug &gt; Clear Eventpoint &gt; Clear Trace Collection On</li>
-  </ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Clearing a Trace Collection</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Clearing a Trace Collection</h2>
+<p>Clear a  <b>Trace Collection</b>  eventpoint when you are finished collecting trace data.</p>
+<div class="step">
+  <h4>Clearing a Trace Collection On Eventpoint</h4>
+    <p>To clear a Trace Collection  eventpoint, follow these steps:</p>
+  <ol>
+    <li>Select the Trace Collection  eventpoint that you want to clear</li>
+    <p>Click the cursor on the line of source code that has the Trace Collection  eventpoint, or select the Trace Collection  eventpoint by name in the Breakpoints view.</p>
+    <li>Click Debug &gt; Clear Eventpoint &gt; Clear Trace Collection On</li>
+  </ol>
+</div>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,24 +1,24 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Trace Collection Off</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Trace Collection Off</h2>
-<p>  A Trace Collection Off eventpoint stops the collection of trace data. This eventpoint is useful when you want trace collection to stop when program execution reaches a line of source code that you specify.</p>
-<div class="step">
-  <h4>Setting a Trace Collection Off Eventpoint</h4>
-  <p>To set a Trace Collection Off eventpoint, follow these steps:</p>
-  <ol>
-    <li>Click the cursor on the line of source code at which you want to set the Trace Collection Off eventpoint</li>
-    <li>Click Debug &gt; Set Eventpoint &gt; Set Trace Collection Off</li>
-  </ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Trace Collection Off</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Trace Collection Off</h2>
+<p>  A <b>Trace Collection Off</b> eventpoint stops the collection of trace data. This eventpoint is useful when you want trace collection to stop when program execution reaches a line of source code that you specify.</p>
+<div class="step">
+  <h4>Setting a Trace Collection Off Eventpoint</h4>
+  <p>To set a Trace Collection Off eventpoint, follow these steps:</p>
+  <ol>
+    <li>Click the cursor on the line of source code at which you want to set the Trace Collection Off eventpoint</li>
+    <li>Click Debug &gt; Set Eventpoint &gt; Set Trace Collection Off</li>
+  </ol>
+</div>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,24 +1,24 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Trace Collection On</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Trace Collection On</h2>
-<p>A Trace Collection On eventpoint starts the collection of trace data. This eventpoint is useful when you want trace collection to start when program execution reaches a line of source code that you specify.</p>
-<div class="step">
-  <h4>Setting a Trace Collection On Eventpoint</h4>
-  <p>To set a Trace Collection On eventpoint, follow these steps:</p>
-  <ol>
-    <li>Click the cursor on the line of source code at which you want to set the Trace Collection On eventpoint</li>
-    <li>Click Debug &gt; Set Eventpoint &gt; Set Trace Collection On</li>
-  </ol>
-</div>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Trace Collection On</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Trace Collection On</h2>
+<p>A <b>Trace Collection On</b> eventpoint starts the collection of trace data. This eventpoint is useful when you want trace collection to start when program execution reaches a line of source code that you specify.</p>
+<div class="step">
+  <h4>Setting a Trace Collection On Eventpoint</h4>
+  <p>To set a Trace Collection On eventpoint, follow these ssteps:</p>
+  <ol>
+    <li>Click the cursor on the line of source code at which you want to set the Trace Collection On eventpoint</li>
+    <li>Click Debug &gt; Set Eventpoint &gt; Set Trace Collection On</li>
+  </ol>
+</div>
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br />License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/images/wnd_chooseBaseClass.png has changed
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html	Thu Feb 18 11:17:02 2010 -0600
@@ -1,59 +1,59 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Tasks in Symbian OS Eclipse Development User Guide</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-   </head>
-   <body>
-   <div class="AuthoredContent">
-   <a name="eclipse_tasks"></a>
-
-
-  </div><div class="Head1">
-<h2>Tasks</h2>
-</div><div class="Bodytext"> 
-  
-
-  <p>
-	 This section explains the different tasks that can be performed using the
-	 Symbian OS plug-ins for Eclipse. It provides step-by-step instructions for
-	 performing each task. 
-  </p>
-  <p>
-	 To develop a program requires that you have installed one or more
-	 development kits. The <i>Working with SDKs</i> tasks describes the
-	 tasks for setting up and selecting the kits to use with your project. 
-  </p>
-  <p>
-	 Next, program creation is described. This can be done either by creating a
-	 new project through a wizard, or by importing an existing Symbian OS project
-	 file. 
-  </p>
-  <p>
-	 You can either import a 
-	 <code class="filename">bld.inf</code> file, in which case all the projects specified in that
-	 component are imported, or import a single 
-	 <code>mmp</code> file. The two cases are discussed separately below. 
-  </p>
-  <p>
-	 You can then add and build code in the project. This is mostly done using
-	 the standard CDT tools and techniques. The plug-ins through also offer special
-	 support for the Symbian OS specific file formats for application information
-	 files (AIF) and multi-bitmap files (MBM), as described in <i>Modifying
-	 Resources</i>. 
-  </p>
-  <ul>
-<li><a href="WorkingwithSDKs.html">Working with SDKs</a></li>
-<li><a href="CreatingNewProjects.html">Creating New Projects</a></li>
-<li><a href="ImportingProjects.html">Importing Projects from a Bld.Inf File</a></li>
-<li><a href="ExportingtoMMP_BLDinf.html">Exporting Project(s) to MMP/Bld.inf Files </a></li>
-<li><a href="AddingClasses.html">Adding Classes</a></li>
-<li><a href="ModifyingResources.html">Modifying Resources</a></li>
-<li><a href="projects/prj_build.htm">Building Projects</a></li>
-</ul>
-
-
-
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-   </body>
-   </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+<title>Tasks in Symbian OS Eclipse Development User Guide</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+   </head>
+   <body>
+   <div class="AuthoredContent">
+   <a name="eclipse_tasks"></a>
+
+
+  </div><div class="Head1">
+<h2>Tasks</h2>
+</div><div class="Bodytext"> 
+  
+
+  <p>
+	 This section explains the different tasks that can be performed using the
+	 Symbian OS plug-ins for Eclipse. It provides step-by-step instructions for
+	 performing each task. 
+  </p>
+  <p>
+	 To develop a program requires that you have installed one or more
+	 development kits. The <i>Working with SDKs</i> tasks describes the
+	 tasks for setting up and selecting the kits to use with your project. 
+  </p>
+  <p>
+	 Next, program creation is described. This can be done either by creating a
+	 new project through a wizard, or by importing an existing Symbian OS project
+	 file. 
+  </p>
+  <p>
+	 You can either import a 
+	 <code class="filename">bld.inf</code> file, in which case all the projects specified in that
+	 component are imported, or import a single 
+	 <code>mmp</code> file. The two cases are discussed separately below. 
+  </p>
+  <p>
+	 You can then add and build code in the project. This is mostly done using
+	 the standard CDT tools and techniques. The plug-ins through also offer special
+	 support for the Symbian OS specific file formats for application information
+	 files (AIF) and multi-bitmap files (MBM), as described in <i>Modifying
+	 Resources</i>. 
+  </p>
+  <ul>
+<li><a href="WorkingwithSDKs.html">Working with SDKs</a></li>
+<li><a href="CreatingNewProjects.html">Creating New Projects</a></li>
+<li><a href="ImportingProjects.html">Importing Projects from a Bld.Inf File</a></li>
+<li><a href="ExportingtoMMP_BLDinf.html">Exporting Project(s) to MMP/Bld.inf Files </a></li>
+<li><a href="AddingClasses.html">Adding Classes</a></li>
+<li><a href="ModifyingResources.html">Modifying Resources</a></li>
+<li><a href="projects/prj_build.htm">Building Projects</a></li>
+</ul>
+
+
+
+<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+   </div></body>
+   </html>
    
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,26 +1,28 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Opening a Log View</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Opening a Log View</h2>
-<p>Use the<a href="../../reference/debugger_settings.htm"> Debugger Settings</a> preference panel to enable the message logging option. The Log view records these types of messages for a program during a debugging session:</p>
-<ul>
-  <li>the start of new tasks</li>
-  <li>routine entry and exit</li>
-  <li>Windows: DLL loading and unloading, and debug <span class="code">printf()</span> messages</li>
-</ul>
-<p>Select the Log System Messages option in the Debugger Settings target settings preference panel.</p>
-<p>Select Project &gt; Debug.</p>
-<ol>
-  <p>The Log view appears. It allows you to select, copy, and save logged text to a file for later analysis. </p>
-</ol>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Opening a Log View</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Opening a Log View</h2>
+<p>Use the <a href="../../reference/debugger_settings.htm">Debugger Settings</a> preference panel to enable the message logging option. The Log view records these types of messages for a program during a debugging session:</p>
+<ul>
+  <li>the start of new tasks</li>
+  <li>routine entry and exit</li>
+  <li>Windows: DLL loading and unloading, and debug <span class="code">printf()</span> messages</li>
+</ul>
+<p>Select the <b>Log System Messages</b> option in the <b>Debugger Settings</b> target settings preference panel.</p>
+<ul>
+  <li>Select <b>Project &gt; Debug</b></li>
+</ul>
+<ol>
+  <p>The <a href="../../reference/view_log.htm">Log</a> view appears. It allows you to select, copy, and save logged text to a file for later analysis. </p>
+</ol>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -38,7 +38,7 @@
     <td><b>SIS Properties </b></td>
     <td><div align="center">
       <p align="left">Complete the PKG File, and Signing Options settings in the <a href="../../reference/build_properties/wnd_sis_properties.htm">SIS Properties</a> dialog. By default, SIS files are output in the directory of the original SIS file.</p>
-      <p><img src="../../reference/images/wnd_sis_properties.png" width="455" height="452"></p>
+      <p><img src="../../reference/images/wnd_sis_properties.png" width="375" height="452"></p>
       <p class="figure">Figure 2 - SIS Properties dialog </p>
       </div></td>
   </tr>
@@ -57,7 +57,7 @@
 <ul>
   <li><a href="../start/carbide_deploying.htm">Manually Deploying Programs to Devices</a></li>
 </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
 </body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,49 +1,49 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Debugging Applications</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Debugging Applications</h2>
-<p>You can debug one or more applications just as you would any other executable with full support of the Carbide debugger. There are two methods that one can use to debug an application:</p>
-<ul>
-  <li><b>For console applications, assign the Executable and leave the Emulator blank in the Debug window</b></li>
-  <p>In the <a href="prj_debug_config.htm">Debug</a> window or <a href="prj_debug_config.htm">launch configuration</a>, simply  point the <b>Executable</b> option  to the  executable and clear the <b>Emulator</b> option  as shown in Figure 1. This launches the  application when you start a debug session from the project. </p>
-</ul>
-<blockquote>
-  <p align="center"><img src="images/page_debug_console.png" width="633" height="206" /></p>
-  <p class="figure">Figure 1 - Launch ConsoleTest executable to debug the ConsoleTest project</p>
-</blockquote>
-
-<ul>
-  <li><b>For regular applications, assign the Executable and Remote process to launch in the Debug window</b></li>
-</ul>
-<blockquote>
-  <p>In the <a href="prj_debug_config.htm">Debug</a> window or <a href="prj_debug_config.htm">launch configuration</a>, simply point both the <b>Executable</b>   and  <b>Remote process to launch</b> options to the application. This launches the  application when you start a debug session from the application project.</p>
-  <p align="center"><img src="../../reference/images/panel_trk_main.png" width="639" height="323" /></p>
-  <p align="left" class="figure">Figure 2 - Assign Executable and Remote Process</p>
-</blockquote>
-<h5>Related concepts</h5>
-  <ul>
-    <li><a href="../../concepts/Projects.html">Projects</a></li>
-    <li><a href="../../concepts/Modify.html">Project Resources</a> </li>
-  </ul>
-  <h5>Related tasks</h5>
-  <ul>
-    <li><a href="prj_debug_dlls.htm">Debugging DLLs </a></li>
-    <li><a href="prj_import_exe.htm">Importing Symbian Executables </a></li>
-    <li><a href="prj_debug_config.htm">Creating a Launch Configuration</a></li>
-  </ul>
-  <h5>Related references</h5>
-  <ul>
-    <li><a href="../../reference/ProjectDirectories.html">Project Directories</a></li>
-</ul>
-
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Debugging Applications</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Debugging Applications</h2>
+<p>You can debug one or more applications just as you would any other executable with full support of the Carbide debugger. There are two methods that one can use to debug an application:</p>
+<ul>
+  <li><b>For console applications, assign the Executable and leave the Emulator blank in the Debug window</b></li>
+  <p>In the <a href="prj_debug_config.htm">Debug</a> window or <a href="prj_debug_config.htm">launch configuration</a>, simply  point the <b>Executable</b> option  to the  executable and clear the <b>Emulator</b> option  as shown in Figure 1. This launches the  application when you start a debug session from the project. </p>
+</ul>
+<blockquote>
+  <p align="center"><img src="images/page_debug_console.png" width="633" height="206" /></p>
+  <p class="figure">Figure 1 - Launch ConsoleTest executable to debug the ConsoleTest project</p>
+</blockquote>
+
+<ul>
+  <li><b>For regular applications, assign the Executable and Remote process to launch in the Debug window</b></li>
+</ul>
+<blockquote>
+  <p>In the <a href="prj_debug_config.htm">Debug</a> window or <a href="prj_debug_config.htm">launch configuration</a>, simply point both the <b>Executable</b>   and  <b>Remote process to launch</b> options to the application. This launches the  application when you start a debug session from the application project.</p>
+  <p align="center"><img src="../../reference/images/panel_trk_main.png" width="593" height="251" /></p>
+  <p align="left" class="figure">Figure 2 - Assign Executable and Remote Process</p>
+</blockquote>
+<h5>Related concepts</h5>
+  <ul>
+    <li><a href="../../concepts/Projects.html">Projects</a></li>
+    <li><a href="../../concepts/Modify.html">Project Resources</a> </li>
+  </ul>
+  <h5>Related tasks</h5>
+  <ul>
+    <li><a href="prj_debug_dlls.htm">Debugging DLLs </a></li>
+    <li><a href="prj_import_exe.htm">Importing Symbian Executables </a></li>
+    <li><a href="prj_debug_config.htm">Creating a Launch Configuration</a></li>
+  </ul>
+  <h5>Related references</h5>
+  <ul>
+    <li><a href="../../reference/ProjectDirectories.html">Project Directories</a></li>
+</ul>
+
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
 </html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -10,7 +10,7 @@
 <body bgcolor="#FFFFFF">
 <h2>Searching for SDKs</h2>
 <p>  Use the <a href="../../reference/SDKPreferences.html">SDK Preferences panel</a> to search for installed Symbian OS SDKs.</p>
-<p align="center"><img src="../../images/SDKPreferences.png" width="696" height="583" /></p>
+<p align="center"><img src="../../images/SDKPreferences.png" width="740" height="546" /></p>
 <p class="figure">Figure 1. SDK Preferences panel</p>
 <div class="step">
   <h4>Searching for SDKs </h4>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -26,12 +26,12 @@
     <td rowspan="2" valign="middle"><p>An SDK or OS developer kit (DevKit) including:</p>
       <ul><li>9.x or higher for Platform Security </li>
     </ul></td>
-    <td height="65"><p>Targets: S60 5th and 3rd Ed., Qt, UIQ</p>
+    <td height="65"><p>Targets: S60 5th and 3rd Ed., Qt</p>
       <p>Debugger: Emulators, on-device debugging</p>
     <p>UI Designer: create graphical interfaces quickly using standard UI components</p></td>
   </tr>
   <tr>
-    <td><p>Targets: S60 5th and 3rd Ed., Qt, UIQ</p>
+    <td><p>Targets: S60 5th and 3rd Ed., Qt</p>
     <p>Debugger: Emulators, on-device debugging, device debugging in ROM, kernel debugging </p>
     <p>Performance Investigator: application performance data, memory usage, power usage, button event reporting </p></td>
   </tr>
@@ -72,12 +72,6 @@
             <li>Qt SDK for S60</li>
           </ul>
         </li>
-        <li>UIQ SDKs (<a href="http://www.uiq.com/">www.uiq.com</a>)
-          <ul>
-            <li>UIQ 3.1 </li>
-            <li>UIQ 3.0</li>
-          </ul>
-        </li>
       </ul>
       <ul><li>Perl (<a href="http://www.activestate.com">www.activestate.com</a>)
     (required)              
@@ -100,7 +94,7 @@
 <ul>
   <li> <a href="carbide_overview.htm">Carbide.c++ Overview</a></li>
 </ul>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
 </body>
 </html>
\ No newline at end of file