# HG changeset patch # User fturovic # Date 1276100786 18000 # Node ID e1fbef8f8f8c40c7f8efc46dd719e5aa319a54f7 # Parent 97d5a41dc05ac99eb1a47063681d1c36a76e108c added Install Extension view page and related images and links diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/book.css --- a/core/com.nokia.carbide.cpp.doc.user/book.css Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/book.css Wed Jun 09 11:26:26 2010 -0500 @@ -101,7 +101,7 @@ } th { - background-color: #ffd62c; + background-color: #E6E6E6; } div.ol.p { @@ -120,7 +120,7 @@ div h5, div h4 { padding:5px 0px 5px 12px; - background-color: #FFCC00; + background-color: #E6E6E6; font-weight:bold; color: #000000; } diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/concepts/CarbidePerspective.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/CarbidePerspective.html Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/CarbidePerspective.html Wed Jun 09 11:26:26 2010 -0500 @@ -1,48 +1,43 @@ - -Carbide.c++ perspective - - - -

Carbide.c++ perspective

- - -

- The Carbide C/C++ perspective is a set of tools and layout of views provided for Symbian OS development. This perspective is designed to work with Symbian OS C++ projects. The commonly used views include:

- -

NOTE When launching a program to debug, the Debug perspective appears.

- -

-

Figure 1 - Carbide C/C++ perspective

-

NOTE Click the icon to show additional options that may not be visible in the perspective view.

-

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference - > C/C++ Views and Editors.

-

- For more details on the Symbian OS Build Configurations, see - Active Configurations.

-
Related references
- - - - - - + +Carbide.c++ perspective + + + +

Carbide.c++ perspective

+ + +

+ The Carbide C/C++ perspective is a set of tools and layout of views provided for Symbian OS development. This perspective is designed to work with Symbian OS C++ projects. The commonly used views include:

+ +

+

Figure 1 - Carbide C/C++ perspective

+

NOTE Click the icon to show additional options that may not be visible in the perspective view.

+

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference + > C/C++ Views and Editors.

+

+ For more details on the Symbian OS Build Configurations, see + Active Configurations.

+
Related references
+ + + + + + \ No newline at end of file diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/concepts/SampleExampleProjectCreate.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/SampleExampleProjectCreate.html Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/SampleExampleProjectCreate.html Wed Jun 09 11:26:26 2010 -0500 @@ -1,45 +1,45 @@ - - - - - -Simple Example Project in Getting Started - - -

Simple DLL Example

- -

- This example walks through the process of creating a basic - “MyDynamicDLL” DLL project.

-

For more information on creating new projects of all types, see Creating New Projects.

-
-

Creating a DLL Project

-
    -
  1. Click File > New > Symbian OS C++ Project to invoke the New Symbian OS C++ Project wizard.
  2. -
  3. Select Basic dynamically linked library (DLL) project template and click Next.
  4. -

    -

    Figure 1. Select Basic DLL template

    -
  5. Enter a project name and specify a workspace location to store the project.
  6. -

    -

    Figure 2. Project name and location information

    -
  7. Select the Symbian OS SDK and Build Configurations to use for this project, then click Next.
  8. -

    -

    Figure 3. SDK selection for project

    -
  9. Enter Specify UID2 as “0x0000008d”, your name as the Author and your Copyright notice. - For more details on UID2, see Creating New Projects. -

    -
  10. -
-

Figure 4. Basic settings for DLL

-
    -
  1. Click Finish to generate the project.
  2. -

    The simple “MyDynamicDLL” project is listed in the Project Explorer view with the set of files created for the project.

    -
-

-

Figure 5. DLL example project in Project Explorer view

-
- - - - + + + + + +Simple Example Project in Getting Started + + +

Simple DLL Example

+ +

+ This example walks through the process of creating a basic + “MyDynamicDLL” DLL project.

+

For more information on creating new projects of all types, see Creating New Projects.

+
+

Creating a DLL Project

+
    +
  1. Click File > New > Symbian OS C++ Project to invoke the New Symbian OS C++ Project wizard.
  2. +
  3. Select Basic dynamically linked library (DLL) project template and click Next.
  4. +

    +

    Figure 1. Select Basic DLL template

    +
  5. Enter a project name and specify a workspace location to store the project.
  6. +

    +

    Figure 2. Project name and location information

    +
  7. Select the Symbian OS SDK and Build Configurations to use for this project, then click Next.
  8. +

    +

    Figure 3. SDK selection for project

    +
  9. Enter Specify UID2 as “0x0000008d”, your name as the Author and your Copyright notice. + For more details on UID2, see Creating New Projects. +

    +
  10. +
+

Figure 4. Basic settings for DLL

+
    +
  1. Click Finish to generate the project.
  2. +

    The simple “MyDynamicDLL” project is listed in the Project Explorer view with the set of files created for the project.

    +
+

+

Figure 5. DLL example project in Project Explorer view

+
+ + + + \ No newline at end of file diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/concepts/build_configurations.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_configurations.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_configurations.htm Wed Jun 09 11:26:26 2010 -0500 @@ -1,56 +1,56 @@ - - - - - - -Active Build Configuration - - - -

Active Build Configuration

-

Use the Active Configuration option in the Carbide Build Configurations panel to specify the build target. Since a project can contain one or more build targets, the active configuration defines which build configuration to use when the project is run or debugged. A launch configuration consists of the following:

- -

Build configurations are defined when the project is created. A project can have any number of build configurations and more can be added as necessary. Each build configuration can have its own combination of tool settings to precisely control how it is defined and built. Build configurations are maintained in the project Properties window in the Carbide Build Configurations panel. To open the panel, select a project in the Symbian Project Navigator or Project Explorer view and select Project > Properties or right-click and select Properties.

-

-

You can select a build configuration in the Active Configuration dropdown list or use the Project > Active Configuration menu option to set which build configuration to launch when running or debugging a program. The currently selected project can be launched by clicking the Run () or Debug () control on the tool bar to launch the project with the currently active build configuration. When no project is selected the last project debugged will be launched.

-

If no launch configuration is present in the project, one is created on initial launch. Subsequent launches of the project will use either the last launch configuration or if more than one launch configuration exists, it uses the most correct one.

-

NOTE The Carbide Run and Debug buttons are shaded in blue to indicate their behavior differs from the standard Eclipse behavior.

-
Table 1 Carbide Build Configuration items
- - - - - - - - - - - - - -
ItemExplanation
Active Configuration The Active Configuration drop down list allows you to select a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.
Manage...Click the Manage... button to add a new SDK/Configuration or remove an existing configuration.
-
Build Configuration Naming
-

When the Carbide.c++ IDE creates an build configuration it uses a standard naming convention to make it easy to identify. For example, HelloCarbide S60 5.0 Emulator Debug is a typical configuration name. The default name follows the form of:

- -

You can use the Debug window to edit the default build configuration names.

-
Other references
- - - - + + + + + + +Active Build Configuration + + + +

Active Build Configuration

+

Use the Active Configuration option in the Carbide Build Configurations panel to specify the build target. Since a project can contain one or more build targets, the active configuration defines which build configuration to use when the project is run or debugged. A launch configuration consists of the following:

+ +

Build configurations are defined when the project is created. A project can have any number of build configurations and more can be added as necessary. Each build configuration can have its own combination of tool settings to precisely control how it is defined and built. Build configurations are maintained in the project Properties window in the Carbide Build Configurations panel. To open the panel, select a project in the Symbian Project Navigator or Project Explorer view and select Project > Properties or right-click and select Properties.

+

+

You can select a build configuration in the Active Configuration dropdown list or use the Project > Active Configuration menu option to set which build configuration to launch when running or debugging a program. The currently selected project can be launched by clicking the Run () or Debug () control on the tool bar to launch the project with the currently active build configuration. When no project is selected the last project debugged will be launched.

+

If no launch configuration is present in the project, one is created on initial launch. Subsequent launches of the project will use either the last launch configuration or if more than one launch configuration exists, it uses the most correct one.

+

NOTE The Carbide Run and Debug buttons are shaded in blue to indicate their behavior differs from the standard Eclipse behavior.

+
Table 1 Carbide Build Configuration items
+ + + + + + + + + + + + + +
ItemExplanation
Active Configuration The Active Configuration drop down list allows you to select a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.
Manage...Click the Manage... button to add a new SDK/Configuration or remove an existing configuration.
+
Build Configuration Naming
+

When the Carbide.c++ IDE creates an build configuration it uses a standard naming convention to make it easy to identify. For example, HelloCarbide S60 5.0 Emulator Debug is a typical configuration name. The default name follows the form of:

+ +

You can use the Debug window to edit the default build configuration names.

+
Other references
+ + + + \ No newline at end of file diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm Wed Jun 09 11:26:26 2010 -0500 @@ -1,71 +1,71 @@ - - - - - - -Supported Target Types - - - - -

Supported Target Types

-

Carbide.c++ supports a variety of build targets based upon the SDKs and which version of the Carbide tools used by the project. The table below identifies which build targets are possible for a specific SDK.

-

NOTE Check the SDK Preferences page to see if an SDK you have installed and whether its build configurations are supported.

-
Table 1. Supported target types for all versions of Carbide.c++
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Target Types Platform Security
-(S60 3.2, S60 5.0)
RAPTOR, GCCE, ARMV5, ARMV5_ABIV2
WINSCW
- (EKA2)
APP (DLL)
DLL
Yes
Yes
EXE (console)
Yes
Yes
EXE (OS 9.1 GUI)
Yes
Yes
Polymorphic DLL
Yes
Yes
STDLIB
Yes
Yes
-
Related tasks
- - - - + + + + + + +Supported Target Types + + + + +

Supported Target Types

+

Carbide.c++ supports a variety of build targets based upon the SDKs and which version of the Carbide tools used by the project. The table below identifies which build targets are possible for a specific SDK.

+

NOTE Check the SDK Preferences page to see if an SDK you have installed and whether its build configurations are supported.

+
Table 1. Supported target types for all versions of Carbide.c++
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Target Types Platform Security
+(S60 3.2, S60 5.0, Symbian ^3)
RAPTOR, GCCE, ARMV5, ARMV5_ABIV2
WINSCW
+ (EKA2)
APP (DLL)
DLL
Yes
Yes
EXE (console)
Yes
Yes
EXE (OS 9.1 GUI)
Yes
Yes
Polymorphic DLL
Yes
Yes
STDLIB
Yes
Yes
+
Related tasks
+ + + + \ No newline at end of file diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm Wed Jun 09 11:26:26 2010 -0500 @@ -21,7 +21,7 @@

TIP Experiment using the context menu in various views to discover additional capabilities.

Figure 1 shows a sample context menu in the Breakpoints view.

-

+

Figure 1 - Example context menu in Breakpoints view

Using Context Menus

diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/concepts/images/workbench.png Binary file core/com.nokia.carbide.cpp.doc.user/html/concepts/images/workbench.png has changed diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html Wed Jun 09 11:26:26 2010 -0500 @@ -75,8 +75,8 @@ -

The columns in the Remote Connections view include:

+

The columns in the Remote Connections view include:

-

+

Figure 2 - New Connection wizard Serial Connection Settings page

Table 2. Serial Connection Setting page - Set Connection Settings tab

@@ -56,24 +56,16 @@ - - - - - - - - - - + + - - +
Explanation
Serial Port A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Ratea dropdown list of baud rates common to serial connections.
Device OS

A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.

Device OS (used to determine installer version)Select the OS used on the device.
Select a service to test Click to select a listed service for testing.
Test Service Status

Click Test Service Status to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check TRK version operation requires more than a few seconds.

+
Initiate Service Testing

Click Initiate Service Testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check TRK version operation requires more than a few seconds.

NOTE The PC must have an internet connection to perform a remote agent version check.

Once the comparison is complete the Status text is updated with the result and further instructions as required.

@@ -87,7 +79,7 @@

Install Remote Agents pane

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

-

+

Figure 2 - New Connection wizard Serial Connection Settings page

Table 3. Serial Connection Setting page - Install Remote Agents tab

@@ -96,8 +88,8 @@ - - + @@ -113,7 +105,7 @@

 

Related references
diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm Wed Jun 09 11:26:26 2010 -0500 @@ -113,7 +113,7 @@

 

Related references
diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/reference/view_install_extensions.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_install_extensions.htm Wed Jun 09 11:26:26 2010 -0500 @@ -0,0 +1,70 @@ + + + + + + +Install Extensions view + + + +

Install Extensions view

+

The Install Extensions view enables the user to locate and install Carbide plug-ins into a core Carbide.c++ installation. The Install Extensions view links to an online site that lists available plug-ins for installation. Plug-ins are grouped by type for

+

The Install Extensions view appears as part of the C/C++ Perspective. It can be added to a perspective by clicking Window > Show View > Install Extensions.

+

+

Figure 1. Install Extensions view

+

Click on the Show Overview icon (Show Overview) icon to show an information popup with additional information on the selected plug-in.

+

+

Figure 2. Install Extensions Plug-in Information popup

+
Table 1 Install Extensions view—items
+
Explanation
Install remote agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7.

+
Install Remote Agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.x needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 3.2.6.

Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.

+ + + + + + + + + + + + +
ItemExplanation
Find

Filters the plug-ins shown in the view to a subset of the complete list.

Show InstalledToggles the plug-ins shown in the view between those that are currently installed and plug-ins available for installation.
+

Install Extensions view toolbar options

+
Table 1 Install Extensions view— toolbar options
+ + + + + + + + + + + + + + + + + + + + + +
Item
Icon
Explanation
Refresh

Refreshes the plug-in list.

Install Checked Items
Click to download and install all plug-ins that are checked in the plug-in list.
View Menu

Additional options include:

+
    +
  • Check All Items
  • +
  • Uncheck All Items
  • +
  • Advanced Install... – launches the Install New Software wizard.
  • +
+
Related references
+ + + + \ No newline at end of file diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Wed Jun 09 11:26:26 2010 -0500 @@ -38,7 +38,7 @@
Related references
Related tasks
diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Wed Jun 09 11:26:26 2010 -0500 @@ -42,7 +42,7 @@
Related reference
Related tasks
diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm Wed Jun 09 11:26:26 2010 -0500 @@ -40,7 +40,7 @@
Related reference
Related tasks
diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Wed Jun 09 11:26:26 2010 -0500 @@ -19,7 +19,7 @@
Related references
diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Wed Jun 09 11:26:26 2010 -0500 @@ -22,11 +22,11 @@
  • Nokia PC Suite (or equivilent software) for connecting and installing applications to the device
  • -
  • Download and install the current TRK SISX file using the On-Device Setup dialog
  • +
  • Download and install the current TRK SISX file using the On-Device Connections dialog
  • The Application TRK debug agents are stored If not, install it now using the On-Device Connections > New Connection Wizard > Install remote agents pane.

    NOTE The Application TRK versions included with Carbide is for CE versions of devices only. They are not intended for use with RnD devices.

  • Specify the communication method with the on-target device during the debug session
  • -

    Start the Application TRK or System TRK on the device. During startup of TRK on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include Bluetooth and USB or a null serial cable. For Bluetooth, you must pair the device with the PC and a valid serial port assigned. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Setup dialog to make the identification and connection setup quick and easy.

    +

    Start the Application TRK or System TRK on the device. During startup of TRK on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include Bluetooth and USB or a null serial cable. For Bluetooth, you must pair the device with the PC and a valid serial port assigned. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Connections dialog to make the identification and connection setup quick and easy.

    Related concepts
    diff -r 97d5a41dc05a -r e1fbef8f8f8c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm Tue Jun 08 12:00:34 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm Wed Jun 09 11:26:26 2010 -0500 @@ -113,7 +113,7 @@

    Check that Carbide.c++ and your USB Virtual COM port or BT Serial Port agree on the port settings.