--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_data.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_data.htm Wed Jun 23 11:20:23 2010 -0500
@@ -10,8 +10,7 @@
<body bgcolor="#FFFFFF">
<h2>Working with Debugger Data</h2>
<p> This section explains how to work with data that the Carbide.c++ debugger generates. The following windows show various types of debugger data.</p>
-<ul><li><a href="../reference/view_system_browser.htm">System Browser Window</a> view —shows individual processes and tasks that the debugger can control</li>
- <li><a href="../reference/view_log.htm">Console view</a> —shows messages generated during the debugging session</li>
+<ul><li><a href="../reference/view_log.htm">Console view</a> —shows messages generated during the debugging session</li>
</ul>
<div id="footer">Copyright © 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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/BasicSettings.html Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/BasicSettings.html Wed Jun 23 11:20:23 2010 -0500
@@ -1,57 +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="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 © 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>
+<!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="500" /></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 © 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
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/carbide_preferences.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/menu_mem_rendering_options.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/menu_memory_rendering_options.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/pref_indexer.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/pref_indexer_properties.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/prefs_carbide_cpp.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_memory.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_pref_code_styles.png has changed
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/indexer.html Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/indexer.html Wed Jun 23 11:20:23 2010 -0500
@@ -1,67 +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++ <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 > Preferences > C/C++ > 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 > Properties > C/C++ General > 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> </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> </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> </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 © 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>
+<!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 > Preferences > C/C++ > 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/pref_indexer.png" alt="Indexer preference panel" width="680" height="775"></p>
+ <p align="left" class="figure">Figure 1 - C/C++ Indexer in Preferences</p>
+ <p align="left" class="Image">The project indexer is accessed by selecting a project in the <a href="view_cpp_projects.htm">Project Explorer</a> or <a href="view_sym_proj_nav.htm">Symbian Project Navigator</a> view and selecting <b>Project > Properties > C/C++ General > Indexer</b> (figure 2).</p>
+ <p align="center" class="Image"><img src="images/pref_indexer_properties.png" alt="Indexer properties panel" width="680" height="628"></p>
+ <p align="left" class="figure">Figure 2 - Indexer panel in Properties for project_name</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> </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> </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> </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 © 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/memory_rendering_options.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/memory_rendering_options.htm Wed Jun 23 11:20:23 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body bgcolor="#FFFFFF">
<h2>Memory Rendering Options</h2>
-<p>You can configure the Memory Rendering pane to display data in the memory location in a variety of ways. The following options are visible on the context menu for the Memory Rendering pane. </p>
+<p>You can configure the <strong>Memory Rendering</strong> pane to display data in the memory location in a variety of ways. The following options are visible on the context menu for the Memory Rendering pane. </p>
<p>Right-click to select an option shown in Table 1. </p>
<h5>Table 1. Memory Rendering context menu options </h5>
<table width="88%" border="0" cellpadding="2" cellspacing="0">
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm Wed Jun 23 11:20:23 2010 -0500
@@ -21,7 +21,7 @@
<li>Value pane (right) — Shows the current value of each corresponding expression. Double-click a value to change it.</li>
</ul>
<p>Figure 1 shows the <b>Expressions</b> view.</p>
-<p align="center"><img src="images/view_expressions.png" width="571" height="202" /></p>
+<p align="center"><img src="images/view_expressions.png" width="439" height="144" /></p>
<p class="figure">Figure 1 - Expressions view </p>
<h5>Table 1. Expressions view —items </h5>
<table width="88%" border="0" cellpadding="2" cellspacing="0">
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_global_variables.htm Wed Jun 23 11:17:17 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,53 +0,0 @@
-<!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>Global Variables Window</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Global Variables Window</h2>
-<p>The Global Variables window shows all global and static variables for each process that you debug. You can open separate Global Variables windows for each process in the same build target. Use the window to observe changes in variable values as the program executes.</p>
-<p>Figure 1 shows the Global Variables window.</p>
-<p class="figure">Figure 1 Global Variables window</p>
-<h5>Table 1 Global Variables window—items </h5>
-<table width="84%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="28%" scope="col">Item</th>
- <th width="72%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>File</b></td>
- <td>Lists source files that declare global or static variables. Click a source file to view its static variables. Click Global Variables to view all global variables declared in the program.</td>
- </tr>
- <tr>
- <td><b>Variables</b></td>
- <td>Lists variables according to the file selected in the File pane. Double-click a variable to display it in a separate Variable window.</td>
- </tr>
-</table>
-<div class="step">
- <h5>Opening the Global Variables Window</h5>
- <p>Use the Global Variables window to display global variables declared in a program or static variables declared in source files that comprise the program.</p>
- <ul>
- <li>To open the Global Variables window, select View > Global Variables or Window > Global Variables Window.</li>
- </ul>
-</div>
-<p></p>
-<div class="step">
- <h5>Viewing Global Variables for Different Processes</h5>
- <p>You can open a separate Global Variables window for each process that the same parent application creates.</p>
- <p>To open the Global Variables window for a particular process, follow these steps:</p>
- <ol>
- <li>Click Project > Debug.</li>
- <p>A debugging session starts.</p>
- <li>In the Thread window toolbar, use the Process list box to specify the process that has the global variables that you want to examine.</li>
- <li>Click View > Global Variables or Window > Global Variables Window.</li>
- <p>Repeat these steps for each process that has global variables that you want to examine.</p>
- </ol>
-</div>
-<div id="footer">Copyright © 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/view_mem_array.htm Wed Jun 23 11:17:17 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,97 +0,0 @@
-<!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’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> </p>
-<h5>Table 1 Array window—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> </td>
- <td>Click to collapse the view of the information pane.</td>
- </tr>
- <tr>
- <td>Bind To</td>
- <td> </td>
- <td>Select the base address of the array: Address, Variable, or Register.</td>
- </tr>
- <tr>
- <td>Array size</td>
- <td> </td>
- <td>Enter the number of elements to display in the Array window.</td>
- </tr>
- <tr>
- <td>Struct Member</td>
- <td> </td>
- <td>Select a specific member to show in each element, or show all members.</td>
- </tr>
- <tr>
- <td>Element</td>
- <td> </td>
- <td>Shows the array elements in a hierarchical list.</td>
- </tr>
- <tr>
- <td>Value</td>
- <td> </td>
- <td>Shows the value of each array element.</td>
- </tr>
- <tr>
- <td>Location</td>
- <td> </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 > 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…</th>
- <th width="69%" scope="col">Do this…</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 © 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/view_memory_wnd.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_memory_wnd.htm Wed Jun 23 11:20:23 2010 -0500
@@ -1,93 +1,88 @@
-<!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>Memory View</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Memory View </h2>
-<p> Use the <b>Memory</b> view to inspect and change process memory. You can address memory using expressions such as:</p>
-<ul>
- <li class="code">0x0847d3c </li>
- <li class="code">(&y)+1024 </li>
- <li class="code">*ptr</li>
- <li class="code">FNname + 1 </li>
-</ul>
-<p>You can configure your output to display traditional, hexadecimal, ascii and/or signed/unsigned decimal. You can also set the size of the rendering columns. </p>
-<p class="note"><b>CAUTION</b> Arbitrarily changing memory contents could degrade the stability of the IDE, another program, or the operating system itself. Understand the consequences of manipulating memory.</p>
-<p>Figure 1 shows the Memory view.</p>
-<p align="center"><img src="../images/views/view_memory.png" width="639" height="250" /></p>
-<p class="figure">Figure 2 - Memory view showing a memory rendering in traditional format</p>
-<h5>Table 1 Memory view—items </h5>
-<table width="100%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="37%" scope="col">Item</th>
- <th width="11%" scope="col">Icon</th>
- <th width="52%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><a href="../tasks/memory/view_memory_show.htm">New Memory View</a> </td>
- <td><div align="center"><img src="images/view_mem_new_memory_btn.png" width="16" height="17" /></div></td>
- <td>Click to add a new Memory monitor view. </td>
- </tr>
- <tr>
- <td><b>Pin Memory Monitor </b></td>
- <td><div align="center"><img src="images/view_mem_pin_memory_btn.png" width="19" height="18" /></div></td>
- <td>Pin memory view.</td>
- </tr>
- <tr>
- <td><b>Refresh</b></td>
- <td> </td>
- <td>Click to refresh the memory display.</td>
- </tr>
- <tr>
- <td><b>Toggle Memory Monitors Pane </b></td>
- <td><div align="center"><img src="images/view_mem_toggle_pane_btn.png" width="19" height="17" /></div></td>
- <td>Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><b>Toggle Split Pane </b></td>
- <td><div align="center"><img src="images/view_mem_split_pane_btn.png" width="17" height="17" /></div></td>
- <td>Alternately shows and hides the Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><b>Link Memory Monitor Panes </b></td>
- <td><div align="center"><img src="images/view_mem_link_btn.png" width="20" height="19" /></div></td>
- <td><span>Enable to synchronize the current selection between the rendering of the same memory monitor </span>. </td>
- </tr>
- <tr>
- <td><b>Switch Memory Monitor </b></td>
- <td><div align="center"><img src="images/view_mem_switch_monitor_btn.png" width="33" height="20" /></div></td>
- <td>If different memory monitor views have been added, select from list of memory monitor views.</td>
- </tr>
- <tr>
- <td><a href="../tasks/memory/memory_monitor_adding.htm">Add Memory Monitor</a> / <a href="../tasks/memory/memory_rendering_adding.htm">Add Rendering</a> </td>
- <td><div align="center"><img src="../images/icons/mem_add_monitor_icon.png" width="18" height="18" /></div></td>
- <td>Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><a href="../tasks/memory/memory_monitor_removing.htm">Remove Memory Monitor / Remove Rendering </a></td>
- <td><div align="center"><img src="../images/icons/mem_remove_monitor_icon.png" width="19" height="19" /></div></td>
- <td>Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><b>Remove All </b></td>
- <td><div align="center"><img src="../images/icons/mem_remove_all_icon.png" width="21" height="20" /></div></td>
- <td>Remove all memory monitors or renderings from the associated pane. </td>
- </tr>
-</table>
-<p align="left">Each memory monitor rendering pane can be configured independently. Right-click in the Renderings pane to see the rendering options available. The options presented in the context menu may differ if you have not chosen the Traditional rendering view (Figure 2). </p>
-<p align="center"><img src="images/menu_mem_rendering_options.png" width="198" height="270"></p>
-<p class="figure">Figure 2 - Rendering pane options </p>
-<h5>Related tasks</h5>
-<ul>
- <li><a href="../tasks/memory/memory_monitor_adding.htm"> Adding a Memory Monitor</a></li>
- <li><a href="../tasks/memory/memory_rendering_adding.htm">Adding a Memory Rendering </a></li>
-</ul>
-<div id="footer">Copyright © 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>
+<!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>Memory View</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Memory View </h2>
+<p> Use the <b>Memory</b> view to inspect and change process memory. You can address memory using expressions such as:</p>
+<ul>
+ <li class="code">0x0847d3c </li>
+ <li class="code">(&y)+1024 </li>
+ <li class="code">*ptr</li>
+ <li class="code">FNname + 1 </li>
+</ul>
+<p>You can configure your output to display traditional, hexadecimal, ascii and/or signed/unsigned decimal. You can also set the size of the rendering columns. </p>
+<p class="note"><b>CAUTION</b> Arbitrarily changing memory contents could degrade the stability of the IDE, another program, or the operating system itself. Understand the consequences of manipulating memory.</p>
+<p>Figure 1 shows the Memory view.</p>
+<p align="center"><img src="images/view_memory.png" alt="Memory view" width="619" height="208"></p>
+<p class="figure">Figure 2 - Memory view showing a memory rendering in traditional format</p>
+<h5>Table 1 Memory view—items </h5>
+<table width="100%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="37%" scope="col">Item</th>
+ <th width="11%" scope="col">Icon</th>
+ <th width="52%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><a href="../tasks/memory/view_memory_show.htm">New Memory View</a> </td>
+ <td><div align="center"><img src="images/view_mem_new_memory_btn.png" width="16" height="17" /></div></td>
+ <td>Click to add a new Memory monitor view. </td>
+ </tr>
+ <tr>
+ <td><b>Pin Memory Monitor </b></td>
+ <td><div align="center"><img src="images/view_mem_pin_memory_btn.png" width="19" height="18" /></div></td>
+ <td>Pin memory view.</td>
+ </tr>
+ <tr>
+ <td><b>Toggle Memory Monitors Pane </b></td>
+ <td><div align="center"><img src="images/view_mem_toggle_pane_btn.png" width="19" height="17" /></div></td>
+ <td>Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><b>Toggle Split Pane </b></td>
+ <td><div align="center"><img src="images/view_mem_split_pane_btn.png" width="17" height="17" /></div></td>
+ <td>Alternately shows and hides the Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><b>Link Memory Monitor Panes </b></td>
+ <td><div align="center"><img src="images/view_mem_link_btn.png" width="20" height="19" /></div></td>
+ <td><span>Enable to synchronize the current selection between the rendering of the same memory monitor </span>. </td>
+ </tr>
+ <tr>
+ <td><b>Switch Memory Monitor </b></td>
+ <td><div align="center"><img src="images/view_mem_switch_monitor_btn.png" width="33" height="20" /></div></td>
+ <td>If different memory monitor views have been added, select from list of memory monitor views.</td>
+ </tr>
+ <tr>
+ <td><a href="../tasks/memory/memory_monitor_adding.htm">Add Memory Monitor</a> / <a href="../tasks/memory/memory_rendering_adding.htm">Add Rendering</a> </td>
+ <td><div align="center"><img src="../images/icons/mem_add_monitor_icon.png" width="18" height="18" /></div></td>
+ <td>Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><a href="../tasks/memory/memory_monitor_removing.htm">Remove Memory Monitor / Remove Rendering </a></td>
+ <td><div align="center"><img src="../images/icons/mem_remove_monitor_icon.png" width="19" height="19" /></div></td>
+ <td>Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><b>Remove All </b></td>
+ <td><div align="center"><img src="../images/icons/mem_remove_all_icon.png" width="21" height="20" /></div></td>
+ <td>Remove all memory monitors or renderings from the associated pane. </td>
+ </tr>
+</table>
+<p align="left">Each memory monitor rendering pane can be configured independently. Right-click in the Renderings pane to see the rendering options available. The options presented in the context menu may differ if you have not chosen the Traditional rendering view (Figure 2). </p>
+<p align="center"><img src="images/menu_memory_rendering_options.png" width="444" height="380"></p>
+<p class="figure">Figure 2 - Rendering pane options </p>
+<h5>Related tasks</h5>
+<ul>
+ <li><a href="../tasks/memory/memory_monitor_adding.htm"> Adding a Memory Monitor</a></li>
+ <li><a href="../tasks/memory/memory_rendering_adding.htm">Adding a Memory Rendering </a></li>
+</ul>
+<div id="footer">Copyright © 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_reg_details.htm Wed Jun 23 11:17:17 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,138 +0,0 @@
-<!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>Registers Details Window</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Registers Details Window</h2>
-<p> The Register Details window (Windows OS) lets you view detailed information about individual bits of registers from 2 bits to 32 bits in size. This window shows information for both system registers and memory-mapped registers. To open the Register Details window, click View > Register Details or Window > Register Details Window.</p>
-<p>The Register Details window has fields that describe the register, its bitfields, and the values of those bitfields. XML files in the Registers folder of your Carbide installation provide the information that appears in the window. The Registers folder is inside the Support folder. The Support folder is inside the Plugins folder of your Carbide installation.</p>
-<p>Figure 1 shows the Register Details window. Table 1 explains items in the window.</p>
-<p class="figure">Figure 1 Register Details window<br />
-</p>
-<h5>Table 1. Register Details window—items </h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="29%" scope="col">Item</th>
- <th width="17%" scope="col">Icon</th>
- <th width="54%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td>Description File text box</td>
- <td> </td>
- <td>Enter the name or full path to the XML file for the register you want to view, or click the Browse button to open a dialog box that you can use to specify the file.</td>
- </tr>
- <tr>
- <td>Register Name</td>
- <td> </td>
- <td>Shows the name of the register depicted in the window.</td>
- </tr>
- <tr>
- <td>Address text box</td>
- <td> </td>
- <td><p>Enter the starting address of the register values that you want to see in the Register Display.</p>
- <p> An error message appears if you enter an invalid starting address.</p></td>
- </tr>
- <tr>
- <td>Format list box</td>
- <td> </td>
- <td><p>Specify the data format for bit values in the Register Display:</p>
- <ul>
- <li>Binary</li>
- <li>Character</li>
- <li>Decimal</li>
- <li>Unsigned Decimal</li>
- <li>Hexadeccimal</li>
- <li>Default—have the IDE determine the best format</li>
- </ul></td>
- </tr>
- <tr>
- <td>Register Display</td>
- <td> </td>
- <td>Shows a depiction of the register that you specify in the Description File text box, including individual register bits and their values.</td>
- </tr>
- <tr>
- <td>Bitfield Name list box</td>
- <td> </td>
- <td><p>Specify a bitfield to highlight in the Register Display. The Description portion of the window reflects available information for the bitfield.</p>
- <p> Select None to have the Description portion of the window reflect information for the entire register and not a bitfield in that register.</p></td>
- </tr>
- <tr>
- <td>Bit Value text box</td>
- <td> </td>
- <td><p>Shows the current value of the bits in the Bitfield Name list box, according to the format that you specify in the Format list box.</p>
- <p>Click the spin buttons to increment or decrement the current value, or enter a new value in the text box.</p>
- <p>Changing the value changes only the Register Display. You must click the Write button to write the new value to the register itself.</p></td>
- </tr>
- <tr>
- <td>Bit Value Modifier list box</td>
- <td> </td>
- <td><p>Specify a new value for the selected bitfield, or view a brief explanation of specific bitfield values.</p>
- <p> Changing the value changes only the Register Display. You must click the Write button to write the new value to the register.</p></td>
- </tr>
- <tr>
- <td>Description</td>
- <td> </td>
- <td><p>Shows a description of the register or a selected bitfield in the register.</p>
- <p> Use the Description File text box to specify the register.</p>
- <p>Use the Text View list box to view specific register information, such as register descriptions, bitfield descriptions, and register details.</p></td>
- </tr>
- <tr>
- <td>Revert button</td>
- <td> </td>
- <td><p>Click to change a modified value in the Register Display to its original value.</p>
- <p> If you clicked the Write button to write a new value to the register, you cannot revert that value.</p></td>
- </tr>
- <tr>
- <td>Read button</td>
- <td> </td>
- <td>Click to have the Register Display reflect current bit values from the register itself.</td>
- </tr>
- <tr>
- <td>Write button</td>
- <td> </td>
- <td><p>Click to write the bit values in the Register Display to the register.</p>
- <p> After you write new values to the register, you cannot revert them.</p></td>
- </tr>
- <tr>
- <td>Reset Value button</td>
- <td> </td>
- <td><p>Click to restore the default value for the selected bitfield.</p>
- <p> The IDE disables this button if the selected bitfield does not have a default value.</p></td>
- </tr>
- <tr>
- <td>Text View list box</td>
- <td> </td>
- <td>Use to specify information that appears in the Description portion of the window.</td>
- </tr>
-</table>
-<h4> Description File</h4>
-<p> Enter in this text box the name of the register that you want to see in the Register Display of the Register Details window. Alternatively, enter the full path to the register description file on your computer, or click the Browse button to open a dialog box that lets you specify the register description file. The text box is not case sensitive.</p>
-<p>After you enter a name or path, the debugger searches for a matching register description file in the Registers folder of your Carbide installation and the project access paths. If the debugger finds a matching file, the Register Display updates the information in the Register Details window. If the debugger does not find a matching name, an error message appears.</p>
-<p>For example, to view the contents of the Opcode register, you can:</p>
-<ul>
- <li>type <span class="code">Opcode</span> in the Description File text box and press Enter or Return, or</li>
- <li>type the full path to the <span class="code">opcode.xml</span> file in the Registers folder and press Enter or Return.</li>
-</ul>
-<p>The debugger matches your entry with the <span class="code">opcode.xml</span> file in the Registers folder. The Register Display in the Register Details window updates its information to show Opcode register details.</p>
-<p>The debugger also updates the Register Display to show the current values in the register. If the debugger fails to update the display, an error message appears.</p>
-<h4>Register Display</h4>
-<p>This display shows the current contents of 32 bits of register data, starting at the address that you specify in the Address text box. The data appears according to the format that you specify in the Format list box.</p>
-<p>The Register Display groups the 32 bits of data into register bitfields. Clicking one of the bits selects its associated bitfield. Additional information about the bitfield, such as its name and permissions, appears in the Description portion of the Register Details window.</p>
-<h4>Text View</h4>
-<p>Use this list box to change the information that appears in the Description portion of the Register Details window:</p>
-<ul>
- <li><b>Auto</b>—select to have the IDE determine which information to display in the window</li>
- <li><b>Register Description</b>—select to show information about the entire register, such as the name of the register itself and the meaning of its contents</li>
- <li><b>Bitfield Description</b>—select to show information about the selected bitfield in the Register Display, such as the name of the bitfield and its access permissions</li>
- <li><b>Register Details</b>—select to show in-depth information about the current register, such as its name, its bit values, and bit-value explanations<br />
- </li>
-</ul>
-<div id="footer">Copyright © 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/view_signals_wnd.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm Wed Jun 23 11:20:23 2010 -0500
@@ -4,14 +4,12 @@
<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>Signals View</title>
+<title>Signals view</title>
<link rel="StyleSheet" href="../../book.css" type="text/css"/>
</head>
<body bgcolor="#FFFFFF">
-<h2>Signals View</h2>
-<p> The Signals view of the Debug perspective lets you view the signals defined on the selected debug target and how the debugger handles each one.</p>
-<p class="note"><b>NOTE</b> Currently Carbide.c++ does not support this CDT feature.</p>
-<p>Figure 1 shows the Signals view.</p>
+<h2>Signals view</h2>
+<p> The Signals view of the Debug perspective lets you view the signals defined on the selected debug target and how the debugger handles each one. Figure 1 shows the Signals view.</p>
<p align="center"><img src="../images/views/view_signals.png" width="500" height="205" /></p>
<p class="figure">Figure 1 - Signals view</p>
<h5>Table 1 Signals view—items </h5>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_system_browser.htm Wed Jun 23 11:17:17 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,62 +0,0 @@
-<!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>System Browser View</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>System Browser View</h2>
-<p> The <b>System Browser</b> view shows system level information about processes executing on various machines, like the host computer or the hardware under debugger control. The <span class="note">view</span> shows this information:</p>
-<ul>
- <li>running processes</li>
- <li>tasks for selected processes</li>
- <li>some hidden processes</li>
-</ul>
-<p>Click on the expand icon for a process to view all tasks assigned to the selected process. Processes under debugger control appear in bold. Double-click a task to open it in a new Thread window, or choose the task name and click the Stack Crawl View button.</p>
-<p>Table 1 explains items in the window.</p>
-<p class="note"><b>NOTE</b> If the System Browser view does not show processes for a specific machine, you will need to start a debugging session for that machine. For example, you might need to debug a project that runs on external hardware in order to see executing processes for that hardware.</p>
-<h5>Table 1 System Browser <span class="note">view</span>—items </h5>
-<table width="79%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="30%" scope="col">Item</th>
- <th width="16%" scope="col">Icon</th>
- <th width="54%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Attach to Process</b></td>
- <td> </td>
- <td>Click to have the debugger control the selected process.</td>
- </tr>
- <tr>
- <td><b>Stack Crawl view</b></td>
- <td> </td>
- <td>Click to open a Thread window for the selected process.</td>
- </tr>
- <tr>
- <td><b>Refresh</b></td>
- <td> </td>
- <td>This icon indicates that information for selected item is periodically updated. Click this icon to toggle between refresh and no refresh.</td>
- </tr>
- <tr>
- <td><b>No Refresh</b></td>
- <td> </td>
- <td>This icon indicates that information is not updated for the selected item.</td>
- </tr>
- <tr>
- <td><b>Expand</b></td>
- <td> </td>
- <td>Click to expand a process and list related tasks.</td>
- </tr>
-</table>
-<h5>Related concepts</h5>
-<ul>
- <li><a href="../tasks/processes/opening_system_browser.htm">Opening a System Browser View</a> </li>
- <li><a href="../tasks/processes/attach_debugger_to_process.htm">Attaching Debugger to a Process</a> </li>
-</ul>
-<div id="footer">Copyright © 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/wnd_build_prefs.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_build_prefs.htm Wed Jun 23 11:20:23 2010 -0500
@@ -9,9 +9,7 @@
<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
<style type="text/css">
<!--
-.style1 { font-family: Georgia, "Times New Roman", Times, serif;
- font-weight: bold;
-}
+.style4 {font-family: Verdana, Ariel, Helvetica, sans-serif; font-weight: bold; }
-->
</style>
</head>
@@ -21,7 +19,7 @@
</a> page in the <b>Preferences</b> window provides global preferences to control general build options like clean, test components, dependency tracking, concurrent build jobs, build behavior, and emulator options.</p>
<p align="center"><img src="images/prefs_build_workspace.png" width="620" height="458" alt="" /></p>
<p class="figure">Figure 1 - Build workspace preferences page </p>
-<p>The following options are available in both the global Build preference panel and the project <b>Properties > Carbide.c++ > </b><b><a href="build_properties/pane_project_settings.htm">Carbide Project Settings</a></b> panel. </p>
+<p>The following options are available in both the global Build preference panel and the project <b>Properties > Carbide.c++ > </b><b><a href="build_properties/pane_project_settings.htm">Project Settings</a></b> panel. </p>
<h5>Table 1 Build Preferences —items</h5>
<table width="100%" border="0" cellpadding="2" cellspacing="0">
<tr>
@@ -51,7 +49,7 @@
</tr>
</table>
<p> </p>
-<p align="center"><img src="images/carbide_proj_settings_sbsv1.png" alt="sbsv1 tab" width="417" height="243"></p>
+<p align="center"><img src="images/carbide_proj_settings_sbsv1.png" alt="sbsv1 tab" width="444" height="143"></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">
@@ -60,35 +58,31 @@
<th width="57%" scope="col">Explanation</th>
</tr>
<tr>
- <td><span class="style1">Clean level </span></td>
+ <td><p class="style4">Clean level </p></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>
+ </ul> </td>
</tr>
<tr>
- <td><span class="style1">Manage dependency tracking (improves build speed) </span></td>
+ <td><p class="style4">Manage dependency tracking (improves build speed) </p></td>
<td><p>Enable to have Carbide manage the dependency tracking for source and resource files. Carbide does this by separating out the generation of dependency information from the makefile and managing the entire process. All builds now can quickly compare whether new dependency information is required due to changes in a source file and only build those that need updating. </p>
- <p>If not enabled, the Symbian OS command line build system handles all dependency tracking by generating the dependency information in the makefiles. Because it does this for all project files, regardless of the number of changes, it can result in a performance penalty. A single edit in a MMP file forces a complete regeneration of the makefile dependency information for all project files. </p>
- </td>
+ <p>If not enabled, the Symbian OS command line build system handles all dependency tracking by generating the dependency information in the makefiles. Because it does this for all project files, regardless of the number of changes, it can result in a performance penalty. A single edit in a MMP file forces a complete regeneration of the makefile dependency information for all project files. </p> </td>
</tr>
<tr>
- <td><b>Show a dialog to modify build actions when modified MMPs are detected </b></td>
- <td><p>Enable to have Carbide ask before starting a build what action to take when modified files are detected. When disabled, do not show a dialog but use the default action listed below.</p>
- </td>
+ <td><p><strong>Show a dialog to modify build actions when modified MMPs are detected </strong></p></td>
+ <td><p>Enable to have Carbide ask before starting a build what action to take when modified files are detected. When disabled, do not show a dialog but use the default action listed below.</p> </td>
</tr>
<tr>
- <td><b>Default action to take when mmp files are modified </b></td>
+ <td><p><strong>Default action to take when mmp files are modified </strong></p></td>
<td><p>Defines the default action Carbide should execute when it detects modified MMP files and the option above is disabled: </p>
<ul>
<li>None</li>
<li>Link Only</li>
<li>Compile and Link</li>
- </ul>
- </td>
+ </ul> </td>
</tr>
<tr>
<td><strong>Do not offer to track dependencies for projects build on command-line </strong></td>
@@ -96,7 +90,7 @@
</tr>
</table>
<p align="left"> </p>
-<p align="center"><img src="images/carbide_proj_settings_sbsv2.png" alt="sbsv2 tab" width="427" height="269"></p>
+<p align="center"><img src="images/carbide_proj_settings_sbsv2.png" alt="sbsv2 tab" width="423" height="176"></p>
<p align="center" class="figure">Figure 3 - SBSv2 tab </p>
<h5 align="left">Table 3 Symbian Build System v2 tab </h5>
<table width="100%" border="0" cellpadding="2" cellspacing="0">
@@ -130,7 +124,7 @@
</table>
<h5>Related references</h5>
<ul>
- <li><a href="build_properties/pane_project_settings.htm">Carbide Project Settings </a></li>
+ <li><a href="build_properties/pane_project_settings.htm">Project Settings </a></li>
</ul>
<div id="footer">Copyright © 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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref.htm Wed Jun 23 11:20:23 2010 -0500
@@ -11,8 +11,8 @@
<body bgcolor="#FFFFFF">
<h2>Carbide.c++ preferences</h2>
<p>The <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=com.nokia.carbide.cpp.project.ui.preferences.CarbidePreferencePage)")'>
-Carbide.c++</a> panel in the <b>Preferences</b> window provides an option to keep your projects updated when you add or create files. Figure 1 shows the Carbide.c++ preference panel.</p>
-<p align="center"><img src="images/carbide_preferences.png" width="627" height="544" alt="" /></p>
+Carbide.c++</a> panel in the <b>Preferences</b> window provides an option to keep your projects updated when you add or create files. Figure 1 shows the Carbide.c++ preference panel.</p>
+<p align="center"><img src="images/prefs_carbide_cpp.png" alt="Carbide.c++ preference panel" width="671" height="554"></p>
<p class="figure">Figure 1 - Carbide.c++ preferences page </p>
<h5>Table 1 Carbide.c++ Preferences —items</h5>
<table width="850" border="0" cellpadding="2" cellspacing="0">
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Wed Jun 23 11:20:23 2010 -0500
@@ -6,14 +6,15 @@
<h2>Code Styles preferences</h2>
- <p>Carbide supports the use of code styles in projects via the C/C++ <img src="../images/command_link.png" alt="" width="16" height="12" border="0" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferences.CodeFormatterPreferencePage)")'> Code Style</a> preference panel. Use a code style profile to set specific smart typing features, like indentation, tabs or spaces, and many more options. There are several preset code styles like GNU, while Carbide supplies these profiles:</p>
+ <p>Carbide supports the use of code styles in projects via the C/C++ <img src="../images/command_link.png" alt="" width="16" height="12" border="0" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferences.CodeFormatterPreferencePage)")'> Code Style</a> preference panel. Use a code style profile to set specific smart typing features, like indentation, tabs or spaces, and many more options. There are several built-in code styles like GNU, Whitesmith, and others, while Carbide supplies these additional styles:</p>
<ul>
- <li><b>Symbian OS</b> — settings are based on the <a href="http://developer.symbian.com/main/downloads/papers/coding_stds/2003-01_SyOSCodStn.pdf">Symbian OS C++ coding standards</a> PDF </li>
- <li><b>S60</b> — settings are based on the <a href="http://www.forum.nokia.com/document/Cpp_Developers_Library/?content=GUID-232258EC-D3B4-4D72-B12B-FFC34F070B4B_GUID-0B6641F4-8393-40B0-96A1-8BF96CB41134.html">S60 Platform: C++ Coding Conventions</a></li>
+ <li><b>Symbian OS</b> — settings are based on the <a href="http://developer.symbian.com/main/downloads/papers/coding_stds/2003-01_SyOSCodStn.pdf">Symbian OS C++ coding standards</a></li>
+ <li><b>S60</b> — settings are based on the <strong>C++ Developer's Library > </strong><a href="http://library.forum.nokia.com/index.jsp?topic=/Nokia_Symbian3_Developers_Library/GUID-B51A9A1F-8E80-4DF6-904A-7BD1A8976BBB.html">C++ Coding Conventions</a></li>
+ <li><strong>Qt</strong> — settings for Qt projects</li>
</ul>
- <p>Setting a code style sets it for the entire workspace. When a new file is created the currently selected code style rules are applied as you edit the file. You can apply a set of rules to a previously created source file by opening it in an editor view, then right-clicking and choosing <b>Source > Format</b> (<span class="code">CTRL+SHIFT+F</span>). </p>
- <p align="center"><img src="images/wnd_pref_code_styles.png" width="627" height="544" /></p>
- <p align="center" class="figure">Figure 1 - Code Style preference panel </p>
+ <p>Setting a code style sets it for the entire workspace. When a new file is created the currently selected code style rules are applied as you edit the file. You can apply a set of rules to a previously created source file by opening it in an editor view, then right-clicking and choosing <b>Source > Format</b> (<span class="code">CTRL+SHIFT+F</span>). </p>
+ <p align="center"><img src="images/wnd_pref_code_styles.png" width="658" height="562" /></p>
+ <p align="center" class="figure">Figure 1 - Code Style preference panel </p>
<h5>Related references </h5>
<ul>
<li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_c_code_style_pref.htm">Code Style preferences</a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_reformatting_sources.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_reformatting_sources.htm Wed Jun 23 11:20:23 2010 -0500
@@ -14,8 +14,8 @@
<li>Open an editor view with the source file you want to reformat</li>
<li>Right-click and choose <b>Source > Format</b> (<span class="code">CTRL+SHIFT+F</span>)</li>
</ol>
- <p align="center"><img src="images/menu_reformat_source_file.png" width="444" height="431" /></p>
- <p align="center" class="figure">Figure 1 -Selecting Source > Format from an editor view </p>
+ <p align="center"><img src="images/menu_reformat_source_file.png" width="604" height="258" /></p>
+ <p align="center" class="figure">Figure 1 -Selecting Source > Format from within an editor view </p>
</div>
<h5>Related references </h5>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_workspace.htm Wed Jun 23 11:17:17 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_workspace.htm Wed Jun 23 11:20:23 2010 -0500
@@ -1,5 +1,5 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
-<title>Code Styles preferences</title>
+<title>Setting the Workspace Code Style</title>
<link rel="StyleSheet" href="../../book.css" type="text/css"/>
</head>
<body>
@@ -7,8 +7,8 @@
<p>You can set the default code style for a workspace using the <img src="../images/command_link.png" alt="" width="16" height="12" border="0" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferences.CodeFormatterPreferencePage)")'> Code Style</a> preference panel. Once set, the specified code style is applied to all new files and projects created in the workspace. To update a source file already in the workspace, see <a href="code_style_reformatting_sources.htm">Reformatting a Source File</a>.</p>
- <p align="center"><img src="../reference/images/wnd_pref_code_styles.png" width="627" height="544"></p>
- <p align="center" class="figure">Figure 1 -Select a profile from the Select a profile list</p>
+ <p align="center"><img src="../reference/images/wnd_pref_code_styles.png" width="658" height="562"></p>
+ <p align="center" class="figure">Figure 1 -Select a profile from the Select a profile list</p>
<p align="left">You can also create your own profiles based on the one's included with Carbide. Simply click <b>Edit</b> and change the options presented in the <b>Profile <<i>profile_name</i>></b> window that appears. </p>
<div class="step">
<h4>To set the workspace code style</h4>
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/images/menu_reformat_source_file.png has changed
