[Post] Symbian development entry-Tools

Various options you can use when developing Series 60 projects are summarized in Table 1-1. Symbian, Nokia, and development tool vendors Borland and metrowerks are providing more options. However, it seems that Microsoft's development tool, although currently feasible and widely used, will not be supported in the foreseeable future.

There are some notable differences between the various ide functions of Microsoft, Borland, and metrowerks. Enhancements to the last two development environments are in progress. EMCC software Ltd uses the IDE of all three vendors as the basis for its own development activities. We also use the command line tool every day-not because of our original intention, but because we can only do this currently. This is the basic operation for setting up programs for the target device and automating the overnight compilation process. C ++ builderx and codewarrior IDE can now be used to build programs for the target device-but not all basic setup operations are supported by all ides.

When writing this article, the easiest and most common starting point for developing any Series 60 project is to define a pair of BLD. inf and. MMP project files. In EMCC software, these files are used to generate any specific ide project file and can be used in any command line creation process. This method is also currently used by Symbian and Nokia in each simple project provided in their sdks and documents. It is not feasible to use a dedicated ide when the current situation is constantly changing. Various situations will change soon, and this officially represents the real life of Symbian OS and Series 60 developers.

Table1-1.Based onPCIntegrated development options

Option	Description
Create a command line	Use the Symbian OS tool for compilation and linking. Use the Microsoft Visual C ++ Compiler/linker to create an operation for the simulator and call it from the command line. The simulator can also be called from the command line. Debugging of the source code layer on the PC simulator must be performed in the IDE. Call the gnu c ++ cross-platform compiler and linker for the target arm device from the command line prompt.
Microsoft Visual C ++ ide	In IDE, Microsoft Visual C ++ Compiler/linker is used to compile and link operations for simulators. Call the gnu c ++ cross-platform compiler and linker for the target arm device from the command line prompt.
Borland C ++ ide	Currently, both IDE options are available. Both use the Borland C ++ compiler and the linker In the IDE to establish the simulator. Call the gnu c ++ cross-platform compiler and linker for the target arm device from the command line prompt.
Metrowerks codewarrior C ++ ide	Use the metrowerks compiler and the linker to establish a simulator in the IDE. The GNU cross-platform compiler and linker required to call the arm target device directly from the command line or codewarrior ide To establish an operation.

In the rest of this article, we use the helloworld sample project to demonstrate all the steps of Series 60 simulator development, debugging, and deployment.

We also provide all other files required by the sample application, such as header files (. h), source files (. cpp), and user interface resource files (. RSS ).

You can use the Series 60 simulator to test the application, start it in an IDE, or run it from a command line prompt. However, debugging an application on the simulator must be performed within the IDE.

After developing, running, testing, and debugging an application on the simulator, you generally want to establish and run the application on the target device. Therefore, we also demonstrate how to create a sample application for the target device, deploy it, and run it on the target Series 60 hardware.
　　Series 60 Simulator

The development, debugging, and initial testing of Series 60 applications are generally performed on PC simulators. This simulator provides a Series 60 device implementation based on Microsoft Windows. In most cases, you will find that the simulator-based development process is very similar to the operations of applications running on real devices; therefore, you can focus on the hardware before it can be used. The precise interface of the simulator is very different from the provided graphics. It depends on the target platform you are using, the Series 60 version, and the selected IDE. In addition, some buttons or other operation elements may be added or deleted to simulate real-world device configurations. Similarly, the applications that can be used on the simulator also depend on the platform version and the device vendor selection.

Some differences between simulators and real devices cannot be avoided. Real Series 60 devices may have hardware accessories (such as photo headers) and other features (such as background vibration ). Therefore, sometimes hardware is necessary for development and testing. In addition, PC-based simulators cannot accurately simulate precise timing, application performance, and memory management issues.

For PC-based development, the Edit/compile/Build cycle is based on the Microsoft Windows development tool set. However, different from the link and establishment based on Win32 or MFC class libraries, developers will rely on the header files installed in Series 60 SDK and the PC-format class libraries for Link and establishment. The binary executable file in Windows format as the result can be run on the PC simulator.

During development, all links and detailed information are managed in the project files of a specific IDE. It also ensures that all output and other required resource files (such as application resource files) for creation operations are placed in the appropriate location for running and debugging in the simulator environment.

According to Figure 1-2, the Series 60 display is logically divided into three areas: Status block, main block, and control block.

Figure 1-2. Series 60 Simulator

The status block is the scale bar at the top of the screen (blue on the simulator) plus the area above it. The main block is in the middle of the screen and is located between the soft key labels at the bottom of the screen. The control block is immediately followed by the master and contains soft key labels.

The status block displays information about the current application and some common information about the device (such as signal strength and battery condition ). It is visible in most cases, but sometimes hidden. For example, many games use the entire screen.

The main block is the main area of the screen, where the application can display data. In typical cases, this area is referenced as a client rectangle, which is usually filled by the display of application data.

The control block occupies the lower part of the screen. It displays the labels related to the two soft buttons and displays the scroll bar as needed. Similar to status blocks, control blocks can sometimes be hidden. In this case, in Series 60, the Style Guide assumes that you can use the Options menu (the default label of the soft button on the left ), even if it is not visible (see the "Nokia series 60 game UI Style Guide" provided in the Series 60 SDK documentation ").

The two buttons Under the control block are the left and right buttons, which are used to select the associated Options Menu or marked operation. You can scroll up or down the four navigation buttons. If you press (click), you can select between them.

You can navigate between objects on the display screen with a PC mouse or a cursor to interact with the simulator. You can directly use the mouse to select folders or other displayed objects without the four-way navigation buttons (just on the simulator ). You can enter data on the PC keyboard or by clicking the 12-bit key area on the simulator. Therefore, the interaction with the simulator is similar, but not exactly the same as using the real Series 60-there is no input on the real device, therefore, all movement and selection are completed through the cursor navigation.

Prepared by Tao gang
Time: 2004-12-03
Source: Skynet

Option	Description
Create a command line	Use the Symbian OS tool for compilation and linking. Use the Microsoft Visual C ++ Compiler/linker to create an operation for the simulator and call it from the command line. The simulator can also be called from the command line. Debugging of the source code layer on the PC simulator must be performed in the IDE. Call the gnu c ++ cross-platform compiler and linker for the target arm device from the command line prompt.
Microsoft Visual C ++ ide	In IDE, Microsoft Visual C ++ Compiler/linker is used to compile and link operations for simulators. Call the gnu c ++ cross-platform compiler and linker for the target arm device from the command line prompt.
Borland C ++ ide	Currently, both IDE options are available. Both use the Borland C ++ compiler and the linker In the IDE to establish the simulator. Call the gnu c ++ cross-platform compiler and linker for the target arm device from the command line prompt.
Metrowerks codewarrior C ++ ide	Use the metrowerks compiler and the linker to establish a simulator in the IDE. The GNU cross-platform compiler and linker required to call the arm target device directly from the command line or codewarrior ide To establish an operation.

In the rest of this article, we use the helloworld sample project to demonstrate all the steps of Series 60 simulator development, debugging, and deployment.

We also provide all other files required by the sample application, such as header files (. h), source files (. cpp), and user interface resource files (. RSS ).

You can use the Series 60 simulator to test the application, start it in an IDE, or run it from a command line prompt. However, debugging an application on the simulator must be performed within the IDE.

After developing, running, testing, and debugging an application on the simulator, you generally want to establish and run the application on the target device. Therefore, we also demonstrate how to create a sample application for the target device, deploy it, and run it on the target Series 60 hardware.
　　Series 60 Simulator

The development, debugging, and initial testing of Series 60 applications are generally performed on PC simulators. This simulator provides a Series 60 device implementation based on Microsoft Windows. In most cases, you will find that the simulator-based development process is very similar to the operations of applications running on real devices; therefore, you can focus on the hardware before it can be used. The precise interface of the simulator is very different from the provided graphics. It depends on the target platform you are using, the Series 60 version, and the selected IDE. In addition, some buttons or other operation elements may be added or deleted to simulate real-world device configurations. Similarly, the applications that can be used on the simulator also depend on the platform version and the device vendor selection.

Some differences between simulators and real devices cannot be avoided. Real Series 60 devices may have hardware accessories (such as photo headers) and other features (such as background vibration ). Therefore, sometimes hardware is necessary for development and testing. In addition, PC-based simulators cannot accurately simulate precise timing, application performance, and memory management issues.

For PC-based development, the Edit/compile/Build cycle is based on the Microsoft Windows development tool set. However, different from the link and establishment based on Win32 or MFC class libraries, developers will rely on the header files installed in Series 60 SDK and the PC-format class libraries for Link and establishment. The binary executable file in Windows format as the result can be run on the PC simulator.

During development, all links and detailed information are managed in the project files of a specific IDE. It also ensures that all output and other required resource files (such as application resource files) for creation operations are placed in the appropriate location for running and debugging in the simulator environment.

According to Figure 1-2, the Series 60 display is logically divided into three areas: Status block, main block, and control block.

Figure 1-2. Series 60 Simulator

The status block is the scale bar at the top of the screen (blue on the simulator) plus the area above it. The main block is in the middle of the screen and is located between the soft key labels at the bottom of the screen. The control block is immediately followed by the master and contains soft key labels.

The status block displays information about the current application and some common information about the device (such as signal strength and battery condition ). It is visible in most cases, but sometimes hidden. For example, many games use the entire screen.

The main block is the main area of the screen, where the application can display data. In typical cases, this area is referenced as a client rectangle, which is usually filled by the display of application data.

The control block occupies the lower part of the screen. It displays the labels related to the two soft buttons and displays the scroll bar as needed. Similar to status blocks, control blocks can sometimes be hidden. In this case, in Series 60, the Style Guide assumes that you can use the Options menu (the default label of the soft button on the left ), even if it is not visible (see the "Nokia series 60 game UI Style Guide" provided in the Series 60 SDK documentation ").

The two buttons Under the control block are the left and right buttons, which are used to select the associated Options Menu or marked operation. You can scroll up or down the four navigation buttons. If you press (click), you can select between them.

You can navigate between objects on the display screen with a PC mouse or a cursor to interact with the simulator. You can directly use the mouse to select folders or other displayed objects without the four-way navigation buttons (just on the simulator ). You can enter data on the PC keyboard or by clicking the 12-bit key area on the simulator. Therefore, the interaction with the simulator is similar, but not exactly the same as using the real Series 60-there is no input on the real device, therefore, all movement and selection are completed through the cursor navigation.

Prepared by Tao gang
Time: 2004-12-03
Source: Skynet