--- a/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/import_examples.htm Mon Apr 27 15:10:32 2009 -0500
+++ b/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/import_examples.htm Tue Apr 28 11:07:47 2009 -0500
@@ -1,42 +1,42 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<title>Importing the SDK example and leavescan plug-ins</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<style type="text/css">
-<!--
-.style1 {color: #000000}
--->
-</style>
-</head>
-<body bgcolor="#FFFFFF">
-
-<h2><a name="import" id="import"></a>Importing the SDK Example </h2>
-<p>You can import any of the plug-ins in Carbide.c++ and examine the source code. However, the SDK provides a plug-in you can import and examine as an example of Carbide.c++ API usage.</p>
-<ul>
-<li>The Examples plugin (<span class="code">com.nokia.carbide.cpp.sdk.examples</span>) is part of the Carbide.c++ Development Kit (CDK). It
-provides examples of installing items in the Carbide menu, creating new projects programatically, and accessing
-project and Symbian build information. See <a href="#showExamplesMenu">below</a> for instructions on how to enable the example menu
-commands inside carbide. </li>
-</ul>
-<p>You can import this and other plugins into your workspace and view/debug all the source to get a better understanding of the
-Carbide.c++ APIs in a functional plugin. Plesae see the page on <a href="env_setup.htm">setting up your development environment</a> for information on how to import a source project. </p>
-<p class="note"><strong>Note</strong> that the example plugins were built with JRE1.5, you will likely receive errors with JRE1.6. Select Window > Preferences > Java > Installed JREs to add currently installed JREs and select the JRE to use.</p>
-<p class="note">When you are done importing you should have new plugins in your workspace and be able to view the
- sources for both plugin projects. Your workspace should look something like this:<br />
- <br />
- <img src="../img/dev_ide_complete.JPG" width="1024" height="757"/></p>
-<h3>Adding a Carbide menu</h3>
- <p>The menu items contributed by the Examples plugin are not visible by default in the Carbide.c++ program. To show the missing menu, follow these steps:</p>
-<ol>
- <li>In Carbide.c++ (not in your Eclipse Java development SDK) choose <b>Window > Customize Perspective...</b></li>
- <li>Select the <b>Commands</b> tab</li>
- <li>Select the checkbox for <b>Carbide.c++ Examples Action Set</b><br/>
- <br/>
- <img src="../img/show_examples_menu.jpg" width="711" height="501"/></li>
-</ol>
- <p>Click OK, and you should now see the Carbide menu in the menu bar. You can now examine the source code and run it in the debugger. See <a href="launchconfig.htm">debugging a debugging a Carbide.c++ plug-in</a> for information on setting up a plug-in debug session. </p>
- <div id="footer">Copyright © 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>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<title>Importing the SDK example and leavescan plug-ins</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+<style type="text/css">
+<!--
+.style1 {color: #000000}
+-->
+</style>
+</head>
+<body bgcolor="#FFFFFF">
+
+<h2><a name="import" id="import"></a>Importing the SDK Example </h2>
+<p>You can import any of the plug-ins in Carbide.c++ and examine the source code. However, the SDK provides a plug-in you can import and examine as an example of Carbide.c++ API usage.</p>
+<ul>
+<li>The Examples plugin (<span class="code">com.nokia.carbide.cpp.sdk.examples</span>) is part of the Carbide.c++ Development Kit (CDK). It
+provides examples of installing items in the Carbide menu, creating new projects programatically, and accessing
+project and Symbian build information. See <a href="#showExamplesMenu">below</a> for instructions on how to enable the example menu
+commands inside Carbide. </li>
+</ul>
+<p>You can import this and other plugins into your workspace and view/debug all the source to get a better understanding of the
+Carbide.c++ APIs in a functional plugin. Plesae see the page on <a href="env_setup.htm">setting up your development environment</a> for information on how to import a source project. </p>
+<p class="note"><strong>Note</strong> that the example plugins were built with JRE1.5, you will likely receive errors with JRE1.6. Select Window > Preferences > Java > Installed JREs to add currently installed JREs and select the JRE to use.</p>
+When you are done importing you should have new plugins in your workspace and be able to view the
+ sources for both plugin projects. Your workspace should look something like this:<br />
+<br />
+<img src="../img/dev_ide_complete.JPG" width="1024" height="757"/>
+<h3>Adding a Carbide menu</h3>
+ <p>The menu items contributed by the Examples plugin are not visible by default in the Carbide.c++ program. To show the missing menu, follow these steps:</p>
+<ol>
+ <li>In Carbide.c++ (not in your Eclipse Java development SDK) choose <b>Window > Customize Perspective...</b></li>
+ <li>Select the <b>Commands</b> tab</li>
+ <li>Select the checkbox for <b>Carbide.c++ Examples Action Set</b><br/>
+ <br/>
+ <img src="../img/show_examples_menu.jpg" width="711" height="501"/></li>
+</ol>
+ <p>Click OK, and you should now see the Carbide menu in the menu bar. You can now examine the source code and run it in the debugger. See <a href="launchconfig.htm">debugging a debugging a Carbide.c++ plug-in</a> for information on setting up a plug-in debug session. </p>
+ <div id="footer">Copyright © 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
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/tasks/sdkMainTopic.htm Tue Apr 28 11:07:47 2009 -0500
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+ <title>Carbide Plug-ins Overview</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+
+<body>
+<h2>Carbide Plug-ins Overview</h2>
+
+<p>Creating a Carbide tool plug-in requires some knowledge and understanding of the Eclipse plug-in environment. There are two methods of creating Carbibe plug-ins, including:</p>
+<ul>
+ <li><a href="../gettingStarted/import_examples.htm">Importing</a> an existing Carbide tool plug-in and modifying it </li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.platform.doc.isv/guide/firstplugin.htm">Creating</a> a new Eclipse plug-in and adding Carbide API calls</li>
+</ul>
+<p>Each has its advantages and disadvantages. Importing an existing Carbide plug-in provides a working plug-in that you can modify and add to easily to get something up and running quickly. However, the plug-in probably doesn't include the API interaction you want to implement and includes a lot of resources you probably don't need or want. Creating a new plug-in from scratch has the advantage of giving you a clean slate upon which to add your own code. It doesn't include any basic Carbide support like menu items and preference panel calls that nearly every tool requires, forcing you to add them on your own.</p>
+<p>Which one you choose depends on the type of plug-in you want to develop and how much support you need to get up and running. In either case, both methods will require access to Carbide projects to allow them to interact with the active project.</p>
+<h2>Accessing Carbide Project Information</h2>
+<p>The following pages describe how to access specific Carbide project information for use in your own tool plug-ins.</p>
+<ul>
+ <li><a href="sdk_getprojinfo.htm">Getting Carbide Project Information</a></li>
+ <li><a href="sdk_getinfmmpinfo.htm">Retrieving INF and MMP Project Information </a></li>
+</ul>
+<h4>Related information</h4>
+<ul>
+ <li><a href="PLUGINS_ROOT/org.eclipse.platform.doc.isv/guide/firstplugin.htm">Simple Plug-in Example</a> (Platform Plug-in Developer Guide)</li>
+ <li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/tasks/carbide_tools.htm">Creating Carbide Plug-ins</a></li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm">Plug-in Development Environment Guide</a></li>
+</ul>
+<div id="footer">Copyright © 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/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/tasks/sdk_getprojinfo.htm Mon Apr 27 15:10:32 2009 -0500
+++ b/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/tasks/sdk_getprojinfo.htm Tue Apr 28 11:07:47 2009 -0500
@@ -1,69 +1,69 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<title>Getting Carbide Project Information</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-
-<h2>Getting Carbide Project Information</h2>
-<p>The following example code fragment demonstrates the use of Carbide.c++ APIs to access Carbide project information.</p>
-<p class="note"><strong>NOTE</strong> There are two perspective IDs that may be useful when using the Carbide APIs. The perspective ID for the Carbide.c++ perspective is <strong>com.nokia.carbide.cpp.CarbideCppPerspective</strong> and for the Debug view it is <strong>org.eclipse.debug.ui.DebugPerspective</strong>.</p>
-<p>Retrieving Carbide.c++ project information starts with knowing your org.eclipse.core.resources.<STRONG>IProject</STRONG> resource and retrieving the com.nokia.carbide.cdt.builder.<STRONG>ICarbideBuildManager</STRONG> instance:</p>
-<p class="listing">ICarbideBuildManager buildMgr = ICarbideBuilderPlugin.getBuildManager();</p>
-<p>Now with your IProject resource you can grab the actual Carbide project in com.nokia.carbide.cdt.builder.<STRONG>ICarbideProjectInfo</STRONG>:</p>
-<p class="listing">// Assumes IProject (project) is known.<br>
- ICarbideProjectInfo cpi = null;<br>
- if (buildMgr.isCarbideProject(project)){<br>
- // check to make sure this is a Carbide project<br>
- cpi = buildMgr.getProjectInfo(project);<br>
-}</p>
-<p>Once you get the ICarbideProjectInfo object you can access all the project data, such as environment variables and SIS builder information via the com.nokia.carbide.cdt.builder.<STRONG>ICarbideBuildConfiguration</STRONG> interface. You can retrieve either the default configuration or the full list:</p>
-<p class="listing">// Get the default build configuration<br>
- ICarbideBuildConfiguration defaultConfig = cpi.getDefaultConfiguration();<br>
-// Get all configurations for this project.<br>
-List<ICarbideBuildConfiguration> configList = cpi.getBuildConfigurations();</p>
-<p>It is important to note that the data retrieved by the ICarbideBuildConfiguration object is what you see in the project properties pages under the Carbide.c++ group. This is separate from the data in the INF and MMP files. </p>
-<h3>Retrieving INF/MMP Project Information</h3>
-<p>All Carbide build stages, with the exception of the post-link SIS Builder stage get their data from INF and MMP files. So naturally Carbide needs a way to retrieve and store this data for doing things like setting up the source indexer and displaying the visual INF and MMP editors. The com.nokia.carbide.cdt.builder.<STRONG>EpocEngineHelper</STRONG> class is a good first stop to retrieve this information. For example, if you want to get all the source files in the first MMP file:</p>
-
-<PRE>// ...assumes ICarbideProjectInformation (cpi) is known.
-List<IPath> mmpPaths = EpocEngineHelper.getMMPFilesForProject(cpi);
-// array length check omitted for brevity....
-List<IPath> srcFilesTest = EpocEngineHelper.getSourceFilesForConfiguration(defultConfig, mmpPaths.get(0));</PRE>
-<h3>SDK Management</h3>
-<p>Each SDK entry in devices.xml is analogous to a com.nokia.carbide.cpp.sdk.core.<STRONG>ISymbianSDK</STRONG> object. If you want to get the entire list of ISymbianSDK objects (same list and properties from the SDK Preferences page) you simply invoke:</p>
-
-<PRE>ISDKManager sdkMgr = SDKCorePlugin.getSDKManager();
-List<ISymbianSDK> sdkList = sdkMgr.getSDKList();</PRE>
-
-<p>Now you can iterate the list and get whatever information you want out of the installed SDKs. For example, using Java 5 iterators we can get the EPOCROOT values of all the SDKs:</p>
-
-<PRE>for (ISymbianSDK currSDK : sdkList){
- String epocRootStr = currSDK.getEPOCROOT();
-}</PRE>
-
-<h3>Reading MMP Statements with the EpocEngine and IMMPData</h3>
-<p>This topic demonstrates how you can read the MMP data for any build configuration (ICarbideBuildConfiguration). The main interface for retrieving MMP data is <strong>com.nokia.carbide.cpp.epoc.engine.model.mmp.IMMPData</strong>. Once you get access to this interface you can learn anything you want about a particular MMP file.</p>
-<p><strong>Prerequisite:</strong> All MMP and bld.inf parsing requires a dependency to the plugin <strong>com.nokia.carbide.cpp.epoc.engine</strong>.</p>
-<p>Typically most keywords of interest are either single string settings (<span class="code">TARGETTYPE</span>, <span class="code">TARGET</span>, <span class="code">EPOCSTACKSIZE</span>) or list of settings (<span class="code">MACRO</span>, <span class="code">CAPABILITY</span>, <span class="code">LANG</span>). Other types can be directly retrieved from IMMPData routines. Check the API documentation for specifics.</p>
-<p>The example provided simply iterates through all the MMP files of a particular build configuration and grabs a list value and single item setting. You'll need to get the particular MMP file you are interested in. Play around with the IMMPData object in the run method and you can quickly get the idea.</p>
-<PRE class="listing">// Assumes buildConfig (ICarbideBuildConfiguration) is known
-for (IPath mmpPath : EpocEngineHelper.getMMPFilesForBuildConfiguration(buildConfig)) {
- Object data = EpocEnginePlugin.runWithMMPData(mmpPath, new
- DefaultMMPViewConfiguration(buildConfig.getCarbideProject().getProject(),
- buildConfig, new AcceptedNodesViewFilter()), new MMPDataRunnableAdapter() {
- public Object run(IMMPData mmpData) {
- // Example, getting a keyword as a list of strings
- List macros = mmpData.getListArgumentSettings().get(EMMPStatement.MACRO);
- // The real return value, getting a single argument setting
- return mmpData.getSingleArgumentSettings().get(EMMPStatement.TARGETTYPE);
- }
- });
-// Make sure to test for and cast to proper Object type!
-String mmpStatement = (String)data; // Now we should have the TARGETTYPE
-}</PRE>
-<div id="footer">Copyright © 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>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<title>Getting Carbide Project Information</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+
+<h2>Getting Carbide Project Information</h2>
+<p>The following example code fragments demonstrate the use of Carbide.c++ APIs to access Carbide project information.</p>
+<p class="note"><strong>NOTE</strong> There are two perspective IDs that may be useful when using the Carbide APIs. The perspective ID for the Carbide.c++ perspective is com.nokia.carbide.cpp.CarbideCppPerspective and for the Debug view it is org.eclipse.debug.ui.DebugPerspective.</p>
+<p>Retrieving Carbide.c++ project information starts with knowing your org.eclipse.core.resources.<STRONG>IProject</STRONG> resource and retrieving the com.nokia.carbide.cdt.builder.<STRONG>ICarbideBuildManager</STRONG> instance:</p>
+<p class="listing">ICarbideBuildManager buildMgr = ICarbideBuilderPlugin.getBuildManager();</p>
+<p>Now with your IProject resource you can grab the actual Carbide project in com.nokia.carbide.cdt.builder.<STRONG>ICarbideProjectInfo</STRONG>:</p>
+<p class="listing">// Assumes IProject (project) is known.<br>
+ ICarbideProjectInfo cpi = null;<br>
+ if (buildMgr.isCarbideProject(project)){<br>
+ // check to make sure this is a Carbide project<br>
+ cpi = buildMgr.getProjectInfo(project);<br>
+}</p>
+<p>Once you get the ICarbideProjectInfo object you can access all the project data, such as environment variables and SIS builder information via the com.nokia.carbide.cdt.builder.<STRONG>ICarbideBuildConfiguration</STRONG> interface. You can retrieve either the default configuration or the full list:</p>
+<p class="listing">// Get the default build configuration<br>
+ ICarbideBuildConfiguration defaultConfig = cpi.getDefaultConfiguration();<br>
+// Get all configurations for this project.<br>
+List<ICarbideBuildConfiguration> configList = cpi.getBuildConfigurations();</p>
+<p>It is important to note that the data retrieved by the ICarbideBuildConfiguration object is what you see in the project properties pages under the Carbide.c++ group. This is separate from the data in the INF and MMP files. </p>
+<h3>Retrieving INF/MMP Project Information</h3>
+<p>All Carbide build stages, with the exception of the post-link SIS Builder stage get their data from INF and MMP files. So naturally Carbide needs a way to retrieve and store this data for doing things like setting up the source indexer and displaying the visual INF and MMP editors. The com.nokia.carbide.cdt.builder.<STRONG>EpocEngineHelper</STRONG> class is a good first stop to retrieve this information. For example, if you want to get all the source files in the first MMP file:</p>
+
+<PRE>// ...assumes ICarbideProjectInformation (cpi) is known.
+List<IPath> mmpPaths = EpocEngineHelper.getMMPFilesForProject(cpi);
+// array length check omitted for brevity....
+List<IPath> srcFilesTest = EpocEngineHelper.getSourceFilesForConfiguration(defultConfig, mmpPaths.get(0));</PRE>
+<h3>SDK Management</h3>
+<p>Each SDK entry in devices.xml is analogous to a com.nokia.carbide.cpp.sdk.core.<STRONG>ISymbianSDK</STRONG> object. If you want to get the entire list of ISymbianSDK objects (same list and properties from the SDK Preferences page) you simply invoke:</p>
+
+<PRE>ISDKManager sdkMgr = SDKCorePlugin.getSDKManager();
+List<ISymbianSDK> sdkList = sdkMgr.getSDKList();</PRE>
+
+<p>Now you can iterate the list and get whatever information you want out of the installed SDKs. For example, using Java 5 iterators we can get the EPOCROOT values of all the SDKs:</p>
+
+<PRE>for (ISymbianSDK currSDK : sdkList){
+ String epocRootStr = currSDK.getEPOCROOT();
+}</PRE>
+
+<h3>Reading MMP Statements with the EpocEngine and IMMPData</h3>
+<p>This topic demonstrates how you can read the MMP data for any build configuration (ICarbideBuildConfiguration). The main interface for retrieving MMP data is <strong>com.nokia.carbide.cpp.epoc.engine.model.mmp.IMMPData</strong>. Once you get access to this interface you can learn anything you want about a particular MMP file.</p>
+<p><strong>Prerequisite:</strong> All MMP and bld.inf parsing requires a dependency to the plugin <strong>com.nokia.carbide.cpp.epoc.engine</strong>.</p>
+<p>Typically most keywords of interest are either single string settings (<span class="code">TARGETTYPE</span>, <span class="code">TARGET</span>, <span class="code">EPOCSTACKSIZE</span>) or list of settings (<span class="code">MACRO</span>, <span class="code">CAPABILITY</span>, <span class="code">LANG</span>). Other types can be directly retrieved from IMMPData routines. Check the API documentation for specifics.</p>
+<p>The example provided simply iterates through all the MMP files of a particular build configuration and grabs a list value and single item setting. You'll need to get the particular MMP file you are interested in. Play around with the IMMPData object in the run method and you can quickly get the idea.</p>
+<PRE class="listing">// Assumes buildConfig (ICarbideBuildConfiguration) is known
+for (IPath mmpPath : EpocEngineHelper.getMMPFilesForBuildConfiguration(buildConfig)) {
+ Object data = EpocEnginePlugin.runWithMMPData(mmpPath, new
+ DefaultMMPViewConfiguration(buildConfig.getCarbideProject().getProject(),
+ buildConfig, new AcceptedNodesViewFilter()), new MMPDataRunnableAdapter() {
+ public Object run(IMMPData mmpData) {
+ // Example, getting a keyword as a list of strings
+ List macros = mmpData.getListArgumentSettings().get(EMMPStatement.MACRO);
+ // The real return value, getting a single argument setting
+ return mmpData.getSingleArgumentSettings().get(EMMPStatement.TARGETTYPE);
+ }
+ });
+// Make sure to test for and cast to proper Object type!
+String mmpStatement = (String)data; // Now we should have the TARGETTYPE
+}</PRE>
+<div id="footer">Copyright © 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/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/tocTasks.xml Mon Apr 27 15:10:32 2009 -0500
+++ b/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/tocTasks.xml Tue Apr 28 11:07:47 2009 -0500
@@ -1,14 +1,14 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="Tasks" link_to="sdkTOC.xml#sdkTasks" >
- <topic label="Adding Items to the Carbide Menu" href="html/tasks/CarbideMenu.htm"/>
- <topic label="Adding Global Preferences to the Carbide Extensions group" href="html/tasks/CarbideExtensionPreferences.htm"/>
- <topic label="Adding Plug-in Help" href="html/tasks/CarbideHelp.htm"/>
- <topic label="Installing Your Own Carbide Plug-ins" href="html/tasks/carbide_adding_plugins.htm"/>
- <topic label="Creating Wizard Templates" href="html/tasks/CreatingWizardTemplates.htm"/>
- <topic label="Creating Plugins to Access Carbide Project Information">
- <topic label="Getting Carbide Project Information" href="html/tasks/sdk_getprojinfo.htm"/>
- <topic label="Retrieving INF and MMP Project Information" href="html/tasks/sdk_getinfmmpinfo.htm"/>
- </topic>
+<?xml version="1.0" encoding="UTF-8"?>
+<?NLS TYPE="org.eclipse.help.toc"?>
+
+<toc label="Tasks" link_to="sdkTOC.xml#sdkTasks" >
+ <topic label="Adding Items to the Carbide Menu" href="html/tasks/CarbideMenu.htm"/>
+ <topic label="Adding Global Preferences to the Carbide Extensions group" href="html/tasks/CarbideExtensionPreferences.htm"/>
+ <topic label="Adding Plug-in Help" href="html/tasks/CarbideHelp.htm"/>
+ <topic label="Creating Wizard Templates" href="html/tasks/CreatingWizardTemplates.htm"/>
+ <topic label="Carbide Plug-in Overview" href="html/tasks/sdkMainTopic.htm" >
+ <topic label="Getting Carbide Project Information" href="html/tasks/sdk_getprojinfo.htm"/>
+ <topic label="Retrieving INF and MMP Project Information" href="html/tasks/sdk_getinfmmpinfo.htm"/>
+ </topic>
+ <topic label="Installing Your Own Carbide Plug-ins" href="html/tasks/carbide_adding_plugins.htm"/>
</toc>
\ No newline at end of file