Creating New Projects in Tasks

# Date 1265834307 21600 # Node ID fbd0e7c75ee186927a49e56d50e1eff231537544 # Parent ddd7e0935476d71d2632a21a863f829fdea6892d# Parent 6743933eec70aa90ae86c94bd11616be5623e189 daily merge diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/images/step1.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step1.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/images/step2.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step2.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/images/step4.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step4.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/images/step5.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step5.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/images/step6.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step6.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/images/step7.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step7.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Wed Feb 10 14:32:22 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Wed Feb 10 14:38:27 2010 -0600 @@ -1,112 +1,101 @@ - - - - Creating New Projects in Tasks - - - -

Creating New Projects

A new Symbian OS C++ project can be created using the New Project - Wizard. A number of templates are available that support different SDKs and executable types.

NOTE There must be at least one recognized SDK installed before you can create a project. See the SDK Preferences panel to determine if the installed SDKs are recognized by Carbide.c++ IDE. If the SDK you have is not recognized, you may still be able to add it to the Discovered Symbian OS SDK list.

NOTE When creating or importing projects the sources and SDK must be on the same drive. This is due to many of the internal SDK tools using an implicit working drive to calculate paths (e.g. \epoc32\tools). Avoid spaces in SDK paths since this will also cause problems.

Creating New Symbian OS C++ Projects

Select File -> New > Symbian OS C++ Project to invoke the New Project wizard.

The New Symbian OS C++ Project wizard appears. Select a template related to an installed SDK. Select the "Filter templates based on enabled SDKs" option to list only SDKs enabled in the SDK Preferences panel. Unselect this option to list SDKs that can be used with Carbide. Click Next.

A project template provides an initial set of source files and project settings appropriate for the project type that you have chosen. The text at the bottom of the window provides a brief description of each template. The project type determines the type of program that you are writing.

NOTE If the selected template requires user input, additional wizard pages will collect data from the user before creating the project.

Enter a name for your project. Enable the Use default location option to save the project in the current workspace. Unselect this option to save your project to another location. Enter the path in the Location field or click Browse button to locate the directory. Click Next.

new project

NOTE There will be two builders available in Carbide, one for SBSv1 (current version of Symbian Build System) and one for SBSv2 (newer version). The Builder option will only be displayed when a SBSv2 installation is detected.

SBSv2 only works with recent versions of Symbian OS9.5. Both SBSv1 and SBSv2 are GNU make based build systems. SBSv1 uses Perl to generate make files, while SBSv2 uses Python. Select the appropriate builder for your project.

For SBSv2, all build configurations (platform/target), including the built-in platforms (WISNCW, ARMV5), are declared in xml files in the \sbs\lib\config directory. The Build Configurations selection page will display only those kits known to support SBSv2.
-

Select the SDKs and Build Configurations. Enable the Filter SDKs based on selected template option to show only the build configurations based on the SDK template you previously selected. Uncheck this option to show all enabled SDKs and their related build configurations.

The Symbian OS SDKs wizard page shows a tree of the SDKs that are available to be used, and for each - SDK, the type of builds that can be done. You can select a single SDK - if you are developing the program for just one version of a platform, - or multiple SDKs if you intend to build your program for multiple build platforms or SDK versions.

The build configuration allows you to choose the compiler(s) to - do the build, and whether debug and/or release builds are required. For this example we recommend using the Emulator Debug version as the build configuration. Later, you can switch to another build configuration to create the project for a specific device.

Click Next to set project properties in the Basic Settings page:

-
NOTE The basic properties for a project may change based on the template selected for a particular project type.
-
Fill in the applicable fields, which - may include UID2, UID3, Vendor ID, Author, Support Email, Copyright - notice and Target Type for console EXEs.
- -
Application UID (or UID3) is used to uniquely identify the binary (EXE or DLL) within the system. The purpose of UID 3 is to prevent one executable from interfering the operation of another executable.
-
A Vendor ID (VID) is a unique identifier for the organization that is supplying the program. 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.
-
UID 2 is a unique identifier number that identifies the type of interface that the - project implements. The values are defined by Symbian
- -
-
For GUI applications, it is always 0x100039CE
-
For static interface DLLs, the UID 2 is always 0x1000008d
-
For polymorphic DLLs, the UID2 is defined by the framework which is being implemented
-
- Author, Copyright notice, and Text to be shown are used in comments created by the wizard in the source code.

-
For more information on UIDs - and Vendor IDs, see Symbian Signed, - which allocates these values.
-

- Click Next to move to the Project Directories page.

NOTE The project directories depends on the template - selected. That is, the directories required to store project data may - change based on the template selected.

Accept the defaults or enter the names for Include and Source folders to be created under the project root directory. Generated files will be copied to these directories.
Click Finish to create the project, which will generate the necessary files for the project based - on the template selected and show them in the C/C++ Projects view.

-

-

-
NOTE If the Carbide.c++ perspective is not visible, select the Window -> Open Perspective > Other... command to list all available - perspectives, then select the Carbide.c++ perspective and click OK.
-

Concepts

Tasks

- - - - - + + + + Creating New Projects + + + +

Creating New Projects

New projects are created using the New Project Wizard. Carbide includes a number of templates that make creating projects for different SDKs and executables quick and easy.

NOTE You must have at least one recognized SDK installed before you can create a project. See the SDK Preferences panel to determine if the installed SDKs are recognized by Carbide.c++ IDE. If the SDK you have is not recognized, you may still be able to add it to the Discovered Symbian OS SDK list.

Creating New Symbian OS C++ Projects

Select File > New > Symbian OS C++ Project to invoke the New Project wizard.

The New Symbian OS C++ Project wizard appears. Select a template related to an installed SDK.

A project template provides the initial source files and project settings appropriate for the chosen project type. A brief description of each template appears below the list. The project type determines the type of program that you are writing.

NOTE If the selected template requires user input, additional wizard pages will collect data from the user before creating the project.

Checkmark the Filter templates based on enabled SDKs option to only list SDKs enabled in the SDK Preferences panel. Uncheck this option to list SDKs that can be used with Carbide. Click Next.

Enter a name for your project.

Checkmark the Use default location option to save the project in the current workspace by default or uncheck it to save to another location. Enter the path in the Location field or click Browse button to locate the directory. Click Next.

new project
+

Select the SDKs and Build Configurations.

Checkmark the Filter SDKs based on selected template option to only show build configurations based on the selected SDK template, or uncheck to show all enabled SDKs and their related build configurations.

The Symbian OS SDKs wizard page shows a tree of the SDKs and the type of builds available within that SDK. Select a single SDK + if the program you are developing is for just one version of a platform, + or select multiple SDKs to build the program for multiple build platforms or SDK versions.

The build configuration allows you to specify the compiler(s) to + do the build, and whether debug and/or release builds are required. For this example we recommend using the Emulator Debug version as the build configuration. Later, you can switch to another build configuration to create the project for a specific device.

Click Next.

Set the project properties in the Basic Settings page.

+
NOTE The basic properties for a project may change based on the template selected for a particular project type.
+
Fill in the applicable fields, which + may include UID2, UID3, Vendor ID, Author, Support Email, Copyright + notice and Target Type for console EXEs.
+ +
Application UID (or UID3) is used to uniquely identify the binary (EXE or DLL) within the system. The purpose of UID 3 is to prevent one executable from interfering the operation of another executable.
+
A Vendor ID (VID) is a unique identifier for the organization that is supplying the program. 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.
+
UID 2 is a unique identifier number that identifies the type of interface that the + project implements. The values are defined by Symbian
+ +
+
For GUI applications, it is always 0x100039CE
+
For static interface DLLs, the UID 2 is always 0x1000008d
+
For polymorphic DLLs, the UID2 is defined by the framework which is being implemented
+
+ Author, Copyright notice, and Text to be shown are used in comments created by the wizard in the source code. +
For more information on UIDs + and Vendor IDs, see Symbian Signed, + which allocates these values.
+

+ Click Next to move to the Project Directories page.

NOTE The project directories depends on the selected template. That is, the directories required to store project data may + change based on the template used.

Accept the defaults or enter the names for Include and Source folders to be created under the project root directory. Generated files will be copied to these directories.

Click Finish to create the project.

This generates the necessary files for the project based on the template selected and show them in the Project Explorer view.

+

+

+
NOTE If the Carbide.c++ perspective is not visible, select the Window +> Open Perspective > Other... command to list all available + perspectives, then select the Carbide.c++ perspective and click OK.
+

Concepts

Tasks

+ + + + + diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/images/new_proj_name_location.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/images/new_proj_name_location.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/build_console.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/build_console.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/run_config_new.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/run_config_new.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_build_config_select_tgt.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_build_config_select_tgt.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_launch_configuration_blank.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_launch_configuration_blank.png has changed diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Wed Feb 10 14:32:22 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Wed Feb 10 14:38:27 2010 -0600 @@ -1,83 +1,83 @@ - - - - - - -Building Projects - - - - -

Building Projects and Symbian Components

Building projects consists of a new abld-based build system that wraps build functionality around existing SDK build tools that invoke makmake commands (e.g. bldmake bldfiles and abld build).

The plug-ins provide extra functionality to set up suitable build configurations for Symbian OS C++ projects. The initial selection of a build configuration is done when you create a project, as described in Creating New Projects. You can later change the Active Build Configuration. The Build Configurations also provides a command (Project > Build All Configurations) to build all the selected build configurations in a batch.

Building Symbian OS C++ projects can involve the use of Symbian OS specific tools, such as the Symbian OS resource compiler. For detailed information on such tools, see the documentation for the SDK that you are using.

You build projects to process the source files that comprise a program and - generate object code. The compiler flags syntax errors in the source files. Use the Properties for <project_name> window to control how the project is built. The following methods build a project:

Build All Configurations—builds all build configurations for a project
Build Working Set—specify which projects to build in a working set
Build Project—(CTRL+B) builds the entire project if it has never been built before or on subsequent builds only those files that have changed since the last build operation

Figure 1 - Right-click project name to build a project

Building a Project

Right-click the project name in the C/C++ Projects view and select Build Project (Figure 1)

Select the Project > Build Project menu item

Click the Build icon in the tool bar (Figure 2) to build the current build configuration

Figure 2 - Build icon

or -

Select a build configuration using the Build icon’s dropdown list in the tool bar (Figure 2)

Carbide.c++ builds the project. During the build a build dialog will appear on screen and a task bar is shown at the bottom right of the perspective when the build is run in the background. All output as the build progresses is shown in the Console view and all build errors and warnings appear in the Problems view.

Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be - built. So Carbide will always check that makefiles are up-to-date and - check dependencies.

A project is also built if you make a change to a project and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

NOTE If you want to turn off building before launching, uncheck the Build (if required) before launching option in the Window > Preferences > Run/Debug > Launching preference panel.

When performing a build, output is displayed in the Console window. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build Console preference panel (figure 2).

Not clearing the console can be useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.

Figure 4 - Build Console Preference Panel

Concepts

Projects

Tasks

- - - + + + + + + +Building Projects + + + + +

Building Projects and Symbian Components

Building projects consists of a new abld-based build system that wraps build functionality around existing SDK build tools that invoke makmake commands (e.g. bldmake bldfiles and abld build).

You build projects to process the source files that comprise a program and + generate object code. The compiler flags syntax errors in the source files. Use the Properties for <project_name> window to control how the project is built. The following methods build a project:

Build All Configurations—builds all build configurations for a project
Build Working Set—specify which projects to build in a working set
Build Project—(CTRL+B) builds the entire project if it has never been built before or on subsequent builds only those files that have changed since the last build operation

Figure 1 - Right-click project name to build a project

Building a Project

Right-click the project name in the Project Explorer view and select Build Project (Figure 1)

Select the Project > Build Project menu item

Click the Build icon in the tool bar (Figure 2) to build the current build configuration

Figure 2 - Build icon

or +

Select a build configuration using the Build icon’s dropdown list in the tool bar (Figure 2)

Carbide.c++ builds the project. A build dialog and a task bar appear during a build process. All build output is shown in the Console view while build errors and warnings appear in the Problems view.

Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be + built. Carbide always checks that makefiles are up-to-date and + dependencies present.

Project is also built if you make a change to it and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

NOTE If you want to turn off building before launching, uncheck the Build (if required) before launching option in the Window > Preferences > Run/Debug > Launching preference panel.

When performing a build, output is displayed in the Console window. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build Console preference panel (figure 2).

Not clearing the console is useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.

Figure 4 - Build Console Preference Panel

Concepts

Projects

Tasks

+ + + \ No newline at end of file diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Wed Feb 10 14:32:22 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Wed Feb 10 14:38:27 2010 -0600 @@ -18,23 +18,21 @@

Creating a Default Launch Configuration

NOTE Carbide.c++ only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide.c++ launches that instead.

NOTE Carbide only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide launches that instead.

Click the Run () or Debug () icon in the tool bar
or
Choose Select Run > Run menu option to launch the project or Run > Debug menu option to debug the project

Carbide.c++ creates a default launch configuration for the project and begins running or debugging the project. If the project already has a defined launch configuration, clicking Run or Debug uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration:

Carbide creates a default launch configuration for the project that is used to run or debug the project. If the project already has a defined launch configuration, clicking Run or Debug uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration:

for emulator targets - an emulator launch configuration is created based on the project settings
for emulator targets - an emulator launch configuration is created based on the project settings
for target devices - the New Launch Configuration Wizard appears asking for additional information

NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Open Run Dialog... or Run > Open Debug Dialog... menu items. - -

In the event that the default launch configuration settings need to be changed, it is possible to edit them in the Debug window, or create a new launch configuration for the project that deviates from the default settings.

NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Run As or Run > Debug As menu items.

In the event that the default launch configuration settings must be changed, edit them in the Debug window, or simply create a new launch configuration for the project that deviates from the default settings.

Creating a Custom Launch Configuration

The appropriate Run or Debug launch configuration window appears (Figure 1).

Undefined launch configuration

Figure 1 - Initial blank Debug launch configuration window

Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new configuration of that type. -
A new configuration appears in the Configuration list under the +
A new configuration appears in the configuration list under the appropriate section using the project name and target to create the configuration name.
-
NOTE By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.
+
NOTE Project information is used to fill in the Project and Process to launch text boxes by default when you click New. You should not have to edit these for a normal run/debug project. If a bld.inf has multiple MMP files listed, then the first executable in the list is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.

New launch configuration

Figure 2 - New launch configuration with name and settings filled in (emulator)

View the information to define the project and executable @@ -94,7 +92,7 @@
Building Projects
Debugging DLLs

Debugging a Symbian OS Program

Use the Carbide.c++ debugger to debug a compiled Symbian OS program in an emulator or on-device. The same process works for other emulators and target devices as well.

NOTE This example uses an emulator. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

NOTE This example uses the emulator included with the S60 5th Edition SDK. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

Debugging a Symbian OS program

NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file if you do not already have an executable in the project. You will also need a symbolics ( .sym) file for debugging on a target device. Ensure that a .sym file has been created. If you are importing an existing application, you may have to rebuild the application and create a related .sym file. Make sure a .sym file has been created in the output directory.

NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file if you do not already have an executable in the project. A symbolics (.sym) file is also required for debugging on a target device. Ensure that a .sym file has been created. If you are importing an existing application, you may have to rebuild the application and create a related .sym file. Make sure a .sym file has been created in the output directory.

Set a breakpoint in the HelloCarbide program

Open the \src\CHelloCarbideAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

Figure 1 - Breakpoint set in CHelloCarbideAppUI::HandleCommandL routine.

Launch the Carbide.c++ debugger and S60 EPOC Emulator

Start the Carbide debugger which launches the S60 EPOC Emulator and installs the HelloCarbide application. For on-device debugging, the application is installed on the target device.

Figure 2 - S60 Emulator launches

Open the Installed directory within the S60 Emulator or your target device

Figure 3 - Open the Installed directory

Launch the HelloCarbide application

Use the S60 Emulator or target device controls to launch the HelloCarbide application (Figure 4). -

Figure 4 - Launch the HelloCarbide application

The HelloCarbide application launches (Figure 5).

Figure 5 - HelloCarbide application running on S60 Emulator

Click the Options soft-key on the S60 Emulator to display the Select menu.
Choose the Message menu item and press the Select soft-key to send a message (Figure 6).

Figure 6 - Send Message to HelloCarbide application

The HandleCommandL breakpoint is hit in the program and control returns to the Carbide.c++ debugger (Figure 7). You can now set additional breakpoints, examine variables, or use the Debug view buttons to control the program.

Figure 7 - Back in the CHelloCarbideAppUI::HandleCommandL routine

Set a breakpoint in the MyProject program

Open the \src\MyProjectAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

Figure 1 - Breakpoint set in MyProjectAppUI::HandleCommandL routine.

Launch the Carbide debugger and S60 SDK Emulator

Start the Carbide debugger which launches the S60 SDK Emulator, installs and launches the executable. For on-device debugging, the application is installed on the target device.

The HelloCarbide application launches (Figure 2).

Figure 2 - MyProject application running on S60 Emulator

NOTE For SDKs prior to the S60 5th Edition it may be necessary to locate the installed application and manually launch it in the emulator or on the target device.

Click the Options soft-key on the S60 Emulator to display the Options menu.
Choose the Message menu item and press the Select soft-key to send a message (Figure 3).

Figure 3 - Send Message to MyProject application

The HandleCommandL breakpoint is hit in the program and control returns to the Carbide debugger (Figure 4). You can now set additional breakpoints, examine variables, or use the Debug view buttons to control the program.

Figure 4 - Back in the CMyProjectAppUI::HandleCommandL routine

That's it for this basic introduction to debugging with Carbide.c++.

Building Projects
Creating a Launch Configuration

New technologies support:
- PnP On-device Debugging
- Hover Help
- Qt SDK for S60
diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp/html/intro/migrateExtensionContent.xml --- a/core/com.nokia.carbide.cpp/html/intro/migrateExtensionContent.xml Wed Feb 10 14:32:22 2010 -0600 +++ b/core/com.nokia.carbide.cpp/html/intro/migrateExtensionContent.xml Wed Feb 10 14:38:27 2010 -0600 @@ -9,7 +9,6 @@ style="carbide.css" path="migrate/@"> - diff -r 6743933eec70 -r fbd0e7c75ee1 core/com.nokia.carbide.cpp/plugin.xml --- a/core/com.nokia.carbide.cpp/plugin.xml Wed Feb 10 14:32:22 2010 -0600 +++ b/core/com.nokia.carbide.cpp/plugin.xml Wed Feb 10 14:38:27 2010 -0600 @@ -139,11 +139,9 @@ configId="org.eclipse.ui.intro.universalConfig" content="html/intro/webresourcesExtensionContent2.xml" /> -