--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_symbian_sdk.htm Fri Sep 24 11:34:18 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_symbian_sdk.htm Fri Sep 24 12:50:36 2010 -0500
@@ -10,6 +10,7 @@
color: #FF0000;
font-weight: bold;
}
+.style3 {color: #EE0000}
-->
</style>
</head>
@@ -30,7 +31,8 @@
<td class="Cell"><p>Lists all the installed and recognized SDKs that are supported by the IDE. SDKs no longer supported by Carbide are not shown. You can double-click the <b>SDK ID</b> or <b>Location</b> entry to edit them directly.</p>
<p>Checked SDKs indicate build configurations available for creating projects. Unchecked SDKs are not displayed when creating new projects. </p>
<p>SDKs shown in <span class="style2">RED</span> indicate a problem, usually no <span class="code">EPOCROOT</span> or unsupported Symbian OS version. </p>
- <p>Click on a SDK name to see its <span class="code">EPOCROOT</span> location and build configuration status in the SDK Information area. </p> </td>
+ <p>If you see a <span class="code style3">BAD_SDK_ROOT</span> error message in the Location column, it indicates you have a bad build configuration. To correct this you must remove the bad configurations from all the projects in your current workspace. Once that is done, you can delete or redirect the SDK or point it to the correct one.</p>
+ <p>Click on a SDK name to see its <span class="code">EPOCROOT</span> location and build configuration status in the SDK Information area. </p> </td>
</tr>
<tr valign="top">
<td class="Cell"><b>Add </b></td>
--- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Fri Sep 24 11:34:18 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Fri Sep 24 12:50:36 2010 -0500
@@ -197,7 +197,6 @@
<topic label="Symbian OS Device (Install SIS)" href="html/projects/launch/run_mode.htm" />
<topic label="Symbian OS Device (Attach to Process)" href="html/projects/launch/attach_process.htm" />
<topic label="Symbian OS Emulator" href="html/projects/launch/emulation.htm" />
- <topic label="Symbian OS Simulator" href="html/projects/launch/simulator.htm" />
<anchor id="launch_config_ANCHOR"/>
</topic>
<topic label="Configuration panes" href="html/projects/launch/pages_overview.htm" >
--- a/core/com.nokia.carbide.cpp/html/help_home.html Fri Sep 24 11:34:18 2010 -0500
+++ b/core/com.nokia.carbide.cpp/html/help_home.html Fri Sep 24 12:50:36 2010 -0500
@@ -18,22 +18,35 @@
<table width="100%" >
<tr>
- <td width="50%"><h4>Getting started... </h4>
+ <td width="50%"><h4>What's new... </h4>
<ul>
- <li>New technologies support:
- <ul>
- <li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_overview.htm">Nokia Qt SDK 1.0</a></li>
+ <li><strong>Eclipse Debugger for C/C++</strong><strong> </strong>— Carbide now uses the <strong>Eclipse Debugger for C/C++</strong> (EDC) as its default debugger. EDC provided an entirely new Debug view with all of the standard debug features like variables, breakpoints, watchpoints, disassembly, and all the other views required to run a debugging session. In addition, EDC provides the framework to add new debug features like snapshots.</li>
+ <li><b>TCF Debug Agents</b> – Using Eclipse’s Target Configuration Framework, a new set of debug agents are used with the new EDC debugger to provide a completely new end-to-end debug environment. </li>
+ <li><b>CODA</b> replaces <b>TRK</b> as the debug agent on remote devices. CODA (Carbide On-device Debug Agent) uses the TCF interface to provice improved communication support between the Carbide debugger and the remote device.</li>
+ <li><b>Plug-n-Play Debug Discovery</b> – a new method where Carbide can detect a debug target (phone device, PlatSim, etc) and automatically connect and configure the target so debugging can be initiated.</li>
+ <li><b>Snapshots</b> – Save the state of a debug session for later review. Multiple snapshots are stored in a debug album to be shared with others or used for comparing different debug sessions.</li>
+ <li><b>New SDK Manager</b> – The developer can add and manage SDKs in the Symbian SDKs panel. The tool lists all available SDKs and can rescan system drives for newly installed and supported SDKs.</li>
+ <li><b>Improved Raptor support</b> – The Build Configuration Filter selects which platforms are visible when creating new projects or build configurations. The results of this preference panel are used to populate the build configurations when importing new projects. · </li>
+ <li><b>New Carbide.c++ portal view</b> – The new <a href="reference/view_carbide_portal.htm">Carbide.c++ Portal</a> view provides easier access to
+ <ul>
+ <li> Welcome and getting started information including videos, blogs, and much more</li>
+ <li>Installing and updating Symbian SDKs using the SDK Manager</li>
+ <li>Customizing the Carbide workspace to better suit your needs</li>
+ <li>Support information</li>
</ul>
</li>
- <li>Carbide Portal
+ <li><strong>Customized Carbide environment</strong> — Carbide introduces Plugin Discovery Sites where you can search for and download Carbide plugins to customize your Carbide environment. Think of it as an app store for plugins. It uses the Eclipse P2 feature to provide a common framework for finding, installing, updating, and removing plugins from the Carbide environment.</li>
+ <li><strong>Improved UI</strong> — Carbide's UI has been streamlined and minimized to a core set of functionality, mainly that of creating Symbian projects, building and debugging them. Context menus have been reworked to show a minimum set of options. If your favorite option is missing, you can use the <strong>Capability</strong> preference panel or the <strong>Customize Perspective</strong> dialog to add favorite commands back onto the context menus.</li>
+ <li><strong>Performance improvements</strong> — We continue to address known performance issues as they reveal themselves. This release provides improvements for:
<ul>
- <li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/reference/view_carbide_portal.htm">Install Extensions</a></li>
+ <li><strong>Stack frames</strong> — in the Debug view stack frames were displayed once the symbol tables were completely read. For large symbol files this sometimes slowed down the display and hence the ability to continue debugging. Now the Debug view will show a subset of stack frames after a set time and update the remainder once it has finished scanning the symbol file.</li>
+ <li><strong>Executables view</strong> — eliminated several use cases that forced the Executables list to update to frequently.</li>
+ <li><strong>Large symbol tables</strong> supported — The Carbide symbol reader has been rewritten to provide faster access to symbols and to handle very large symbol files (larger than 10GB).</li>
</ul>
</li>
<li>Carbide examples and tutorials
<ul>
<li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_00.htm">Emulator Application Project Tutorial</a></li>
- <li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_dll_example_00.htm">DLL Project Tutorial</a></li>
<li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_00.htm">Remote Project Debugging (Run-mode)</a></li>
</ul>
</li>