# HG changeset patch # User fturovic # Date 1246032989 18000 # Node ID 2cf1147ef3f922c62a0bf843ad918a0d44d9a1f0 # Parent 2ea049cecf524290179f8e8db01f70dc93caeed4 creating new project task needed reordering and updated images diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/book.css --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/book.css Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/book.css Fri Jun 26 11:16:29 2009 -0500 @@ -12,7 +12,7 @@ /* Set default font to serif style, 12-pt and plain */ body, p, table { - font-family: Verdana, Arial, Helvetica, sans-serif; + font-family: Verdana, Helvetica, sans-serif; font-size: 13px; font-weight: normal; } @@ -69,7 +69,7 @@ .step { /* background-color: #EEE; */ /* margin: 10px 0px; */ - color: #111; + /* color: #111; */ /* border-bottom:2px solid #EEE; */ } @@ -99,7 +99,7 @@ /* 20070522-replaced gray with green background to match gradiant color for title */ th { - background-color:#FDDD1F; /* background-color:#acd79b; + background-color:#FFC550; /* background-color:#acd79b; background-color:#999; color:#FFF; */ } @@ -121,7 +121,7 @@ /* Make all H4 and H5 items appear in bold gray against a light green background */ div h5, div h4 { padding:5px 0px 5px 12px; - background-color:#FFFF66; + background-color:#FDCB2F; /* background-color: #EEE; */ font-weight:bold; color: #000000; diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-00.png Binary file uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-00.png has changed diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-01.png Binary file uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-01.png has changed diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-02.png Binary file uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-02.png has changed diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-03.png Binary file uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-03.png has changed diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-04.png Binary file uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-04.png has changed diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-05.png Binary file uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-05.png has changed diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-07.png Binary file uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/images/proj_new-07.png has changed diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/reference/views/ref_edit_image_property.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/reference/views/ref_edit_image_property.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/reference/views/ref_edit_image_property.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,91 +1,91 @@ - - - - - -Edit Image Property Dialog - - - -

Edit Image Property Dialog

-

Use the Edit Image Property dialog to select the images and masks from a Multi-Image File (.mbmdef or .mifdef). Only images that are being built into the application are available for editing.

-

When the multi-image file is an .mbmdef file, a bitmap and mask are selected and composed to create an image with transparent pixels. The mask may be empty, in which case the bitmap is opaque. When the multi-image file is an .mifdef file, an SVG-T image is selected, which has an implicit mask described by the bounding rectangle of the SVG drawing.

-

When selecting a mask, a one-bit image defines a hard mask, where the black pixels in the mask select pixels from the bitmap and white pixels in the mask are transparent. Any other mask image depth (typically 8) defines a soft mask, seen visually as a grayscale image, where the value of each pixel is the alpha or transparency value of the pixel from the bitmap. In a soft mask, a white pixel is fully opaque, and a black pixel is fully transparent. A gray pixel is partially transparent. In this respect, a soft mask looks roughly inverted compared to a hard mask.

-

NOTE The MIFDEF compiler does not support .bmp files, so S60 3.0 applications cannot use .mifdef files to add bitmaps to .mif files. Instead, create a different .mbmdef file using a different basename than the .mifdef file, to add your .bmp files.

-

edit image property

-

Figure 1 - The Edit Image Property dialog

-
Table 1. Edit Image Property dialog—items
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemExplanation
Multi-Image File Select the project's .mbmdef or .mifdef file containing the image to display.
Image

Select the image in the chosen multi-image file to display in the image component. The image appears to the right of the Image dropdown with image canvas size and color depth information below. If a mask is associated with the image, it is selected in the Mask section.

-

The combined image + mask appears in the Appearance section with canvas size and color depth information below. This is the best indicator of how the image will appear in the application.

-

Choose <No image> to clear the selection.

Mask

Select the image mask from the dropdown menu. The mask image is then shown to the right of the Mask dropdown with mask canvas size and color depth information below.

-

Choose <No image> to clear the selection.

Add Image... / Add Bitmap... For .mbmdef files, click Add Icon to add a new icon. For .mifdef files, click Add Bitmap to add a bitmap.
OKClick OK to close the dialog and apply changes.
CancelClick Cancel to close the dialog without applying any changes.
-
Image Validation
-

Images are validated and rendered on a per-component basis. Each component may have different restrictions or guidelines for the type or size of images that appear. In S60 2.x, or an S60 2.8 project without scalable icon support, images are cropped to the size of the context icon, navi image, or image controls. In S60 2.8 with scalable icon support and S60 3.0 projects, images are scaled to the size of the controls.

-
Supported Components
-

The following components currently support images:

- -

Other components may be supported in future releases.

-
-

Opening the Edit Image Property Dialog

- -

Figure 2 - Browse control appears when Appearance > image property is selected

- -
-
Related references
- -
Related tasks
- - - - - - - + + + + + +Edit Image Property Dialog + + + +

Edit Image Property Dialog

+

Use the Edit Image Property dialog to select the images and masks from a Multi-Image File (.mbmdef or .mifdef). Only images that are being built into the application are available for editing.

+

When the multi-image file is an .mbmdef file, a bitmap and mask are selected and composed to create an image with transparent pixels. The mask may be empty, in which case the bitmap is opaque. When the multi-image file is an .mifdef file, an SVG-T image is selected, which has an implicit mask described by the bounding rectangle of the SVG drawing.

+

When selecting a mask, a one-bit image defines a hard mask, where the black pixels in the mask select pixels from the bitmap and white pixels in the mask are transparent. Any other mask image depth (typically 8) defines a soft mask, seen visually as a grayscale image, where the value of each pixel is the alpha or transparency value of the pixel from the bitmap. In a soft mask, a white pixel is fully opaque, and a black pixel is fully transparent. A gray pixel is partially transparent. In this respect, a soft mask looks roughly inverted compared to a hard mask.

+

NOTE The MIFDEF compiler does not support .bmp files, so S60 3.0 applications cannot use .mifdef files to add bitmaps to .mif files. Instead, create a different .mbmdef file using a different basename than the .mifdef file, to add your .bmp files.

+

edit image property

+

Figure 1 - The Edit Image Property dialog

+
Table 1. Edit Image Property dialog—items
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ItemExplanation
Multi-Image File Select the project's .mbmdef or .mifdef file containing the image to display.
Edit MBM/MIF File...Click to select the MBM or MIF file to use.
Image

Select the image in the chosen multi-image file to display in the image component. The image appears to the right of the Image dropdown with image canvas size and color depth information below. If a mask is associated with the image, it is selected in the Mask section.

+

The combined image + mask appears in the Appearance section with canvas size and color depth information below. This is the best indicator of how the image will appear in the application.

+

Choose <No image> to clear the selection.

Mask

Select the image mask from the dropdown menu. The mask image is then shown to the right of the Mask dropdown with mask canvas size and color depth information below.

+

Choose <No image> to clear the selection.

OKClick OK to close the dialog and apply changes.
CancelClick Cancel to close the dialog without applying any changes.
+
Image Validation
+

Images are validated and rendered on a per-component basis. Each component may have different restrictions or guidelines for the type or size of images that appear. In S60 2.x, or an S60 2.8 project without scalable icon support, images are cropped to the size of the context icon, navi image, or image controls. In S60 2.8 with scalable icon support and S60 3.0 projects, images are scaled to the size of the controls.

+
Supported Components
+

The following components currently support images:

+ +

Other components may be supported in future releases.

+
+

Opening the Edit Image Property Dialog

+ +

Figure 2 - Browse control appears when Appearance > image property is selected

+ +
+
Related references
+ +
Related tasks
+ + + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,33 +1,33 @@ - - - - - -Project Tasks - - - -

Project Tasks

- -

The Carbide.c++ UI Designer uses standard interface conventions for all tasks. This section describes the specific steps needed to create projects for use with the UI Designer, as well as how to examine, modify, and/or delete existing projects that contain UI designs.

-

Topics in this section include:

- - - - - - + + + + + +Project Tasks + + + +

Project Tasks

+ +

The Carbide.c++ UI Designer uses standard interface conventions for all tasks. This section describes the specific steps needed to create projects for use with the UI Designer, as well as how to examine, modify, and/or delete existing projects that contain UI designs.

+

Topics in this section include:

+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-00.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-00.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-00.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,34 +1,34 @@ - - - - - -Starting the New Project Wizard - - - -

Starting the New Project Wizard

- -

The New Project wizard guides you through the tasks needed to create a new S60 C++ GUI project for use with the UI Designer. Each page of the wizard allows you to customize the new project to meet your specific needs.

-

Use the File > New submenu to start the wizard.

-

start wizard

-

Figure 1 - Starting the New Project wizard

-
-

Starting the New Project Wizard

-
    -
  1. Click File > New > C++ Application for S60 Project as shown in Figure 1.
    2. -

    The New C++ Application for S60 Project Wizard - Symbian OS C++ Project window will appear.

    -
-
-
Related tasks
- -
Related references
- - - - - + + + + + +Starting the New Project Wizard + + + +

Starting the New Project Wizard

+ +

The New Project wizard guides you through the tasks needed to create a new S60 C++ GUI project for use with the UI Designer. Each page of the wizard allows you to customize the new project to meet your specific needs.

+

Use the File > New submenu to start the wizard.

+

start wizard

+

Figure 1 - Starting the New Project wizard

+
+

Starting the New Project Wizard

+
    +
  1. Click File > New > Symbian OS C+ Project as shown in Figure 1.
    2. +

    The Symbian OS C++ Project window appears.

    +
+
+
Related tasks
+ +
Related references
+ + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-01.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-01.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-01.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,37 +1,37 @@ - - - - - -Setting the Project Name - - - -

Setting the Project Name

- -

The New Project wizard guides you through the tasks needed to create a new S60 C++ GUI project for use with the UI Designer. Each page of the wizard allows you to customize the new project to meet your specific needs.

-

Use the Symbian OS C++ Project page of the New Project Wizard window to name the new project and specify where to store project files.

-

naming the project

-

Figure 1 - Naming the project

-
-

Naming the New Project

-
    -
  1. Enter a unique project name in the Project name field (Figure 1)
    2. -
  2. Specify where to store Project related files using Project contents (optional)
    3. -

    When Use default is enabled, project files are stored in the default workspace directory for projects. If you disable Use default, click the Browse button to select where project files should be stored.

    -
  3. Click the Next > button
    4. -

    The Templates Page appears.

    -
-
-
Related tasks
- -
Related references
- - - - - + + + + + +Setting the Project Name + + + +

Setting the Project Name

+ +

The New Project wizard guides you through the tasks needed to create a new S60 C++ GUI project for use with the UI Designer. Each page of the wizard allows you to customize the new project to meet your specific needs.

+

Use the Symbian OS C++ Project page of the New Project Wizard window to name the new project and specify where to store project files.

+

naming the project

+

Figure 1 - Naming the project

+
+

Naming the New Project

+
    +
  1. Enter a unique project name in the Project name field (Figure 1)
    2. +
  2. Specify where to store Project related files using Project contents (optional)
    3. +

    When Use default is enabled, project files are stored in the default workspace directory for projects. If you disable Use default, click the Browse button to select where project files should be stored.

    +
  3. Click the Next button
    4. +

    The Symbian OS SDK page appears.

    +
+
+
Related tasks
+ +
Related references
+ + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-02.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-02.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-02.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,37 +1,37 @@ - - - - - -Selecting a Template - - - -

Selecting a Template

- -

Use the Templates page of the New Project Wizard to select a template for your GUI project.

-

select a template

-

Figure 1 - Selecting the template

-

NOTE The list of templates is specified by the SDKs installed on the machine. Your list may be different.

-
-

Selecting a template

-
    -
  1. Click the "S60 3rd Ed. GUI Application with UI Designer" option from the list of templates (Figure 1)
    2. -

    Read the descriptive text to learn more about the currently selected template.

    -
  2. Click the Next > button.
    3. -

    The Symbian OS SDKs window will appear.

    -
-
-
Related tasks
- -
Related references
- - - - - - + + + + + +Selecting a Template + + + +

Selecting a Template

+ +

Use the Select a type of project page of the New Project Wizard to select a template for your GUI project.

+

select a template

+

Figure 1 - Selecting the template

+

NOTE The list of templates is specified by the SDKs installed on the machine. Your list may be different.

+
+

Selecting a template

+
    +
  1. Click the "GUI Application with UI Designer" option from the list of templates (Figure 1)
    2. +

    Read the descriptive text to learn more about the currently selected template.

    +
  2. Click the Next button.
    3. +

    The New Symbian OS C++ Project page appears.

    +
+
+
Related tasks
+ +
Related references
+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-03.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-03.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-03.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,38 +1,38 @@ - - - - - -Selecting Project SDKs - - - -

Selecting Project SDKs

- -

Use the Symbian OS SDKs page of the New Project Wizard to select the SDKs for your project.

-

selecting SDKs

-

Figure 1 - Selecting the SDKs

-

NOTE Your list of SDKs may be different. You must select a S60 3.0 or other supported SDK.

-
-

Selecting Project SDKs

- -
    -
  1. Check the box for the "S60_3rd" option (or its equivalent among your SDKs) from the list of SDKs as shown in Figure 1.
    2. -
  2. Check the boxes for all desired build configurations.
    3. -
  3. Click the Next > button.
    4. -

    The Application Properties Page will appear.

    -
-
-
Related tasks
- -
Related references
- - - - - - + + + + + +Selecting Project SDKs + + + +

Selecting Project SDKs

+ +

Use the Symbian OS SDKs page of the New Project Wizard to select the SDKs for your project.

+

selecting SDKs

+

Figure 1 - Selecting the SDKs

+

NOTE Your list of SDKs may be different. You must select a S60 5.0 or other supported SDK.

+
+

Selecting Project SDKs

+ +
    +
  1. Check the box for the "S60_3rd" option (or its equivalent among your SDKs) from the list of SDKs as shown in Figure 1.
    2. +
  2. Check the boxes for all desired build configurations.
    3. +
  3. Click the Next button.
    4. +

    The Application Properties Page will appear.

    +
+
+
Related tasks
+ +
Related references
+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-04.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-04.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-04.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,37 +1,37 @@ - - - - - -Setting Basic Application Properties - - - -

Setting Basic Application Properties

- -

Use the Application page of the New Project Wizard to set the application name, baseline SDK, and initial language used by your application.

-

fig 1

-

Figure 1 - Selecting name, design, and language, or accept default values

-
-

Selecting Application Properties

- -
    -
  1. Enter a unique name for your application
    2. -
  2. Select the baseline SDK from the dropdown list
    3. -
  3. Select the initial language from the dropdown list
    4. -
  4. Click Next
    5. -
-
-
Related tasks
- -
Related references
- - - - - - + + + + + +Setting Basic Application Properties + + + +

Setting Basic Application Properties

+ +

Use the Application page of the New Project Wizard to set the application name, baseline SDK, and initial language used by your application.

+

fig 1

+

Figure 1 - Selecting name, design, and language, or accept default values

+
+

Selecting Application Properties

+ +
    +
  1. Enter a unique name for your application
    2. +
  2. Select the baseline SDK from the dropdown list
    3. +
  3. Select the initial language from the dropdown list
    4. +
  4. Click Next
    5. +
+
+
Related tasks
+ +
Related references
+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-05.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-05.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-05.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,36 +1,36 @@ - - - - - -Selecting Initial Content - - - -

Selecting Initial Content

- -

Use the S60 UI Design Selection page of the New Project Wizard to select the initial design pattern used by the application. Many applications use common design types, like forms, or lists, for their intended purpose. Select the Empty design if your application does not follow any of the standard types.

-

new 05

-

Figure 1 - Selecting the Initial Content Type

-
-

Selecting Initial Content

- -
    -
  1. Select the appropriate initial content type by clicking on its picture.
    2. -
  2. Click the Next > button.
    3. -

    The Content Variants Page will appear if your initial content type is ListBox, else the Container Name and Type Page will appear.

    -
-
-
Related tasks
- -
Related references
- - - - - - + + + + + +Selecting Initial Content + + + +

Selecting Initial Content

+ +

Use the S60 UI Design Selection page of the New Project Wizard to select the initial design pattern used by the application. Many applications use common design types, like forms, or lists, for their intended purpose. Select the Empty design if your application does not follow any of the standard types.

+

new 05

+

Figure 1 - Selecting the Initial Content Type

+
+

Selecting Initial Content

+ +
    +
  1. Select the appropriate initial content type by clicking on its picture.
    2. +
  2. Click the Next > button.
    3. +

    The Content Variants Page will appear if your initial content type is ListBox, else the Container Name and Type Page will appear.

    +
+
+
Related tasks
+ +
Related references
+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-07.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-07.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new-07.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,40 +1,40 @@ - - - - - -Setting Base Name and Container Type - - - -

Setting Base Name and Container Type

- -

Use the Container Name and Type Page of the New Project Wizard to set the base name and container type for your UI design.

-

base name and container

-

Figure 1 - Setting the Base Name and Container Type

-
-

Setting Name and Type

- -
    -
  1. Enter a unique Base Name for your UI Design or accept the default value.
    2. -
  2. Select the container type from the context menu or accept the default value.
    3. -
  3. Uncheck the Support View Switching checkbox if you do not wish to use this feature.
    4. -

    Support for Avkon View switching requires that the application's AppUi class be derived from the SDK's CAknViewAppUi class. The UI Designer will initialize your application's AppUi class to derive from that parent class if this box is checked. If you uncheck the box, the UI Designer will instead derive your application's AppUi class from class CAknAppUi.

    -

    NOTE For most applications this box should remain checked. Once set, this option and the effect which it has on your applications ability to support Avkon View Switching, cannot be changed by the UI Designer. Significant manual effort would be required to manually adjust your project to support this feature should you decide later to incorporate it.

    -
  4. Click Next
    5. -

    The Basic Settings page appears.

    -
-
-
Related tasks
- -
Related references
- - - - - - + + + + + +Setting Base Name and Container Type + + + +

Setting Base Name and Container Type

+ +

Use the Container Name and Type Page of the New Project Wizard to set the base name and container type for your UI design.

+

base name and container

+

Figure 1 - Setting the Base Name and Container Type

+
+

Setting Name and Type

+ +
    +
  1. Enter a unique Base Name for your UI Design or accept the default value.
    2. +
  2. Select the container type from the context menu or accept the default value.
    3. +
  3. Uncheck the Support View Switching checkbox if you do not wish to use this feature.
    4. +

    Support for Avkon View switching requires that the application's AppUi class be derived from the SDK's CAknViewAppUi class. The UI Designer will initialize your application's AppUi class to derive from that parent class if this box is checked. If you uncheck the box, the UI Designer will instead derive your application's AppUi class from class CAknAppUi.

    +

    NOTE For most applications this box should remain checked. Once set, this option and the effect which it has on your applications ability to support Avkon View Switching, cannot be changed by the UI Designer. Significant manual effort would be required to manually adjust your project to support this feature should you decide later to incorporate it.

    +
  4. Click Next
    5. +

    The Basic Settings page appears.

    +
+
+
Related tasks
+ +
Related references
+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/projects/task_proj_new.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,57 +1,57 @@ - - - - - -Creating New GUI Projects for the UI Designer - - - -

Creating New GUI Projects for the UI Designer

- -

The New Project wizard will guide you through the steps needed to create a new GUI project.

-

This page provides a list of the steps needed to create a new S60 C++ GUI project using the wizard. The links in the discussion of each step take you to a page which contains a detailed description of the subtasks needed to perform that step.

-

Some common New Project Wizard actions include:

- -
-

Creating New S60 C++ GUI Projects

-
    -
  1. Start the New Project Wizard
    2. -

    Select the C++ Application for S60 Project wizard from the File > New submenu.

    -

    The wizard will guide you through the tasks needed to create a new S60 C++ GUI project.

    -
  2. Set the project name
    3. -

    Specify the project name and the location to store project contents in the Symbian OS C++ Project page.

    -
  3. Select the project's template
    4. -

    Select the template to use when creating the project in the Templates page.

    -
  4. Select the project SDK's
    5. -

    Assign one or more SDKs to the project in the Symbian OS SDKs page.

    -
  5. Set basic application properties
    6. -

    Set the application name, baseline SDK, and language in the Application Properties page.

    -
  6. Select the UI Design initial content
    7. -

    Select the initial content type for your UI Design in the S60 UI Design Selection page.

    -
  7. Select the UI Design content variant (optional based on choice for initial content)
    8. -

    Select the desired variant of the initial content type in the Content Variants page.

    -
  8. Set the base name and container type
    9. -

    Set the base name and container type for the initial content in the Container Name and Type page.

    -
  9. Enter the Application UID
    10. -

    Fill in a unique Application UID in the Basic Settings page. In most cases you may use the default value which is provided.

    -
  10. Assign project directories
    11. -

    Fill in the project directory names to use when creating the project and copying files in the Project Directories page.

    -

    NOTE The default directory names should be used except where local software development practices specify other directory names.

    -
-

Once all of these steps are complete, a new Symbian OS project is created on disk and displayed in the Project Explorer view.

-
-
Related references
- - - - - - + + + + + +Creating New GUI Projects for the UI Designer + + + +

Creating New GUI Projects for the UI Designer

+ +

The New Project wizard will guide you through the steps needed to create a new GUI project.

+

This page provides a list of the steps needed to create a new S60 C++ GUI project using the wizard. The links in the discussion of each step take you to a page which contains a detailed description of the subtasks needed to perform that step.

+

Some common New Project Wizard actions include:

+ +
+

Creating New S60 C++ GUI Projects

+
    +
  1. Start the New Project Wizard
    2. +

    Select the C++ Application for S60 Project wizard from the File > New submenu.

    +

    The wizard will guide you through the tasks needed to create a new S60 C++ GUI project.

    +
  2. Select the project's template
    3. +

    Select the template to use when creating the project in the Templates page.

    +
  3. Set the project name
    4. +

    Specify the project name and the location to store project contents in the Symbian OS C++ Project page.

    +
  4. Select the project SDK's
    5. +

    Assign one or more SDKs to the project in the Symbian OS SDKs page.

    +
  5. Set basic application properties
    6. +

    Set the application name, baseline SDK, and language in the Application Properties page.

    +
  6. Select the UI Design initial content
    7. +

    Select the initial content type for your UI Design in the S60 UI Design Selection page.

    +
  7. Select the UI Design content variant (optional based on choice for initial content)
    8. +

    Select the desired variant of the initial content type in the Content Variants page.

    +
  8. Set the base name and container type
    9. +

    Set the base name and container type for the initial content in the Container Name and Type page.

    +
  9. Enter the Application UID
    10. +

    Fill in a unique Application UID in the Basic Settings page. In most cases you may use the default value which is provided.

    +
  10. Assign project directories
    11. +

    Fill in the project directory names to use when creating the project and copying files in the Project Directories page.

    +

    NOTE The default directory names should be used except where local software development practices specify other directory names.

    +
+

Once all of these steps are complete, a new Symbian OS project is created on disk and displayed in the Project Explorer view.

+
+
Related references
+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/uidesign/task_uid_enable_view_switching.htm --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/uidesign/task_uid_enable_view_switching.htm Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/html/tasks/uidesign/task_uid_enable_view_switching.htm Fri Jun 26 11:16:29 2009 -0500 @@ -1,81 +1,86 @@ - - - - - -Enabling Avkon View Switching - - -

Enabling Avkon View Switching

- -

The New Project wizard allows you to specify that you want automated support for Avkon View Switching in your project. This option must be set when the project is first created or the UI Designer will not generate the AppUi level code necessary to support view switching. Checking this option is sufficient to implement view switching automatically within projects that you have created with the wizard.

-

Legacy applications may already be configured to support view switching. If your legacy application is so configured, a few relatively simple manual edits to UI designs created with the S60 UI design wizard will add them to the switching group.

-
-

Implementing Avkon View Switching in a Project

-
    -
  1. Add Avkon View initialization code to <ProjectName>AppUi::ConstructL().
    2. -

    You must manually instantiate your view, and register it with the View Server.

    -

    Adopt the following code for your view's name, and add it to the ConstructL() method of your <ProjectName>AppUi class.

    -

    iMyView = CMyView::NewL();
    - AddViewL( iMyView );
    - SetDefaultViewL( *iMyView ); // if this view is the default

    -
  2. Add an enumerator for your view to the view id enumeration.
    3. -

    Open the <ProjectName>.hrh file. It will look something like this:

    -

    /*
    - ============================================================================
    - Descriptive Information
    - ============================================================================
    - */
    - #ifndef __LEGACYPROJ_HRH__
    - #define __LEGACYPROJ_HRH__

    -

    // LegacyProj enumerate command codes
    - enum TLegacyProjIds
    - {
    - ECommand1 = 0x6001, // start value must not be 0
    - ECommand2
    - }

    - -

    // LegacyProj view identifiers
    - enum TLegacyProjViewUids
    - {
    - ELegacyViewUid = 1
    - };

    -

    #endif // __LEGACYPROJ_HRH__

    -

    You must manually edit this file to add a Uid for your view to the enumeration. Add your new identifier to the end of the list. After editing the file, it could look like this:

    -

    /*
    - ============================================================================
    - Descriptive Information
    - ============================================================================
    - */
    - #ifndef __LEGACYPROJ_HRH__
    - #define __LEGACYPROJ_HRH__

    -

    // LegacyProj enumerate command codes
    - enum TLegacyProjIds
    - {
    - ECommand1 = 0x6001, // start value must not be 0
    - ECommand2
    - }

    - -

    // LegacyProj view identifiers
    - enum TLegacyProjViewUids
    - {
    - ELegacyViewUid = 1,
    - EMyDesignViewUid // UID for new view, named EViewUid
    - };

    -

    #endif // __LEGACYPROJ_HRH__

    -
-

When you have completed these steps, the view-switching aspects of this design should build and operate successfully.

-
-
Related tasks
- -
Related references
- - - - - - + + + + + +Enabling Avkon View Switching + + + +

Enabling Avkon View Switching

+ +

The New Project wizard allows you to specify that you want automated support for Avkon View Switching in your project. This option must be set when the project is first created or the UI Designer will not generate the AppUi level code necessary to support view switching. Checking this option is sufficient to implement view switching automatically within projects that you have created with the wizard.

+

Legacy applications may already be configured to support view switching. If your legacy application is so configured, a few relatively simple manual edits to UI designs created with the S60 UI design wizard will add them to the switching group.

+
+

Implementing Avkon View Switching in a Project

+
    +
  1. Add Avkon View initialization code to <ProjectName>AppUi::ConstructL().
    2. +

    You must manually instantiate your view, and register it with the View Server.

    +

    Adopt the following code for your view's name, and add it to the ConstructL() method of your <ProjectName>AppUi class.

    +

    iMyView = CMyView::NewL();
    + AddViewL( iMyView );
    + SetDefaultViewL( *iMyView ); // if this view is the default

    +
  2. Add an enumerator for your view to the view id enumeration.
    3. +

    Open the <ProjectName>.hrh file. It will look something like this:

    +

    /*
    + ============================================================================
    + Descriptive Information
    + ============================================================================
    + */
    + #ifndef __LEGACYPROJ_HRH__
    + #define __LEGACYPROJ_HRH__
    +
    + // LegacyProj enumerate command codes
    + enum TLegacyProjIds
    + {
    + ECommand1 = 0x6001, // start value must not be 0
    + ECommand2
    + }
    +
    + // LegacyProj view identifiers
    + enum TLegacyProjViewUids
    + {
    + ELegacyViewUid = 1
    + };
    + #endif // __LEGACYPROJ_HRH__

    +

    You must manually edit this file to add a Uid for your view to the enumeration. Add your new identifier to the end of the list. After editing the file, it could look like this:

    +

    /*
    + ============================================================================
    + Descriptive Information
    + ============================================================================
    + */
    + #ifndef __LEGACYPROJ_HRH__
    + #define __LEGACYPROJ_HRH__
    +
    + // LegacyProj enumerate command codes
    + enum TLegacyProjIds
    + {
    + ECommand1 = 0x6001, // start value must not be 0
    + ECommand2
    + }
    +
    + // LegacyProj view identifiers
    + enum TLegacyProjViewUids
    + {
    + ELegacyViewUid = 1,
    + EMyDesignViewUid // UID for new view, named E + + ViewUid
    + };
    + #endif // __LEGACYPROJ_HRH__

    +
+

When you have completed these steps, the view-switching aspects of this design should build and operate successfully.

+
+
Related tasks
+ +
Related references
+ + + + + + diff -r 2ea049cecf52 -r 2cf1147ef3f9 uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/toctasks.xml --- a/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/toctasks.xml Thu Jun 25 13:45:49 2009 -0500 +++ b/uidesigner/com.nokia.carbide.cpp.uidesigner.doc.user/toctasks.xml Fri Jun 26 11:16:29 2009 -0500 @@ -1,164 +1,164 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +