The various options you can use are summarized in Table 1-1 when developing a Series 60 project. Symbian, Nokia and Development Tools Manufacturer Borland, Metrowerks are offering more choices. However, it seems like Microsoft development tools, although it is currently feasible and widely used, in the foreseeable future cannot be supported. There are currently some payable differences between the various IDEs of Microsoft, Borland and Metrowerks. The enhancement of the latter two development environments is underway. EMCC Software Co., Ltd. uses all three of the three vendors as the foundation of their own development activities. We also use command line tools every day - not because of our origin, but because we can only do this. This is the basic operation of establishing a program and an automated overnight compilation process for the target device. C Builderx and CodeWarrior IDE can now be used to create programs for target devices - but not all basic setup operations are supported by all IDE. When writing this article, the easiest and most versatile starting point for any Series 60 project is to define a pair of BLD.INF and .MMP project files. In EMCC Software, these files are used for the generation of any particular IDE project file, and can be used during any required command line. This method is also the method of Symbian and NOKIA in their SDK and each simple project provided in the document. It is not feasible to use a dedicated IDE in the event that the current situation is constantly changing. Various situations will change soon, and this is a true life of the Symbian OS and Series 60 developers. Table 1-1. Synthesis of development options based on PC
Option Description The command line establishment Operation Use the Symbian OS tool to compile and link, use the Microsoft Visual C Compiler / Link to create an action to make an action from the command line. The simulator can also call from the command line. The debugging of the source code layer on the PC simulator needs to be performed in the IDE. The cross-platform compiler and linker of the GNU C for the ARM target device are called from the command line prompt. Microsoft Visual C IDE uses Microsoft Visual C compiler / linkers to build operations to compile and link for the simulator in IDE. The cross-platform compiler and linker of the GNU C for the ARM target device are called from the command line prompt. Borland C IDE is currently available in both IDE selection. Both use the Borland C compiler and linker in the IDE to create an operation. The cross-platform compiler and linker of the GNU C for the ARM target device are called from the command line prompt. Metrowerks CodeWarrior C IDE uses the MetrowerKs compiler and the linker inside the IDE to create an emulator. Call the ARM target device directly from the command line or the CodeWarrior IDE to establish the GNU cross-platform compiler and linker required for the ARM target device.
In the remainder of this article, we use the HelloWorld sample project to demonstrate all steps in the development, debugging, and deployment procedures of the Series 60 simulator.
We also provide other files required by the sample application, such as header file (.h), source file (.cpp), and user interface resource files (.RSS).
You can use the Series 60 emulator to test the application, or start it in an IDE, or run it from the command line prompt. However, debugging applications on the simulator must be performed inside the IDE.
After developing, running, testing, and debugging applications on an emulator, you usually want to build and run the program on the target device. So we also demonstrate how to establish sample applications for target devices, how to deploy it, and run it on the target Series 60 hardware.
The development, debugging and initial testing of Series 60 simulator Series 60 applications are generally performed on the PC simulator, which provides an implementation of the SERIES 60 device based on Microsoft Windows. In most cases you will find the operation of the simulator's development process and the operation of the application running on a real device; so your main job can be made before the hardware device can be used. The precise interface of the simulator is very different from the graphics provided, depending on the target platform you use, the version of Series 60 and the selected IDE. In addition, you may also add or delete some buttons or other operating elements to simulate the configuration of a reality device. Similarly, applications that can be used on the simulator also depends on the selection of the platform and device manufacturers. Some differences between simulators and real devices cannot be avoided. Real Series 60 devices may have hardware attachments (eg, photo heads) and other features (for example, background vibration). So sometimes hardware is necessary for development and testing. In addition, the PC-based simulator cannot accurately simulate the problem of application performance and memory management. For PC-based development, editing / compilation / establishment cycle is based on Microsoft Windows Development Tools. However, linking and establishing different from the Win32 or MFC class library, developers will rely on the header files installed by the Series 60 SDK and the class library for the PC format for links and establishment. The binary executable as a result of the binary executable can be run on the PC's simulator. During the development process, the project file of a particular IDE manages all links and established detail information. It ensures that all outputs and other resource files (such as application resource files) required for operation (such as application resource files) are placed and debugged in an emulator environment. According to Figures 1-2, the Series 60 display logically is divided into three areas: status block, main block, and control block. Figure 1-2. SERIES 60 Simulator
The status block is the scale bar on the top of the screen (blue on the emulator) plus it above the area. The main block is part of the soft button (Soft Key) tag located between the screen and the bottom of the screen and the bottom of the screen. The control block is immediately fast, including a soft button tag. The status block can display some normal information of the current application and some normal information of the device (such as signal strength and battery). It is visible in most situations, but sometimes it is hidden. For example, many games use the entire screen. The main block is the main area of the screen, and the application can display data here. Typically, this area is used as a client rectangular reference, which is usually filled by the application's data display. The control block occupies the lower part of the screen, which shows the label related to the two soft buttons and displays the scroll bar as needed. Similar to the status block, the control block can sometimes be hidden. In this case, in SERIES 60, the pattern is guided to assume that the user can use the Options menu (the default tag of the soft button on the left), even if it is not visible (see the NOKIA Series 60 Game UI provided by Series 60 SDK) Style Guide "). The two buttons below the control block are left and right soft buttons for selecting the currently associated Options menu or tag operation. The four-way navigation buttons can be scrolled up and down, and if you press (click), you can choose. You can make navigate between the objects on the display via the PC mouse or the cursor button to interact with the simulator. We can use the mouse click to select a folder or other displayed object without the need to use four navigation buttons (only on the emulator). We can use the PC keyboard to input data or by clicking on the 12-bit keys on the simulator. Therefore, it is similar to the interaction of the simulator, but is not completely like using real series 60 - there is no pen input on a real device, so all movements and options are done by cursor navigation. Author: Tao Gang build time: 2004-12-03 Source: NEW YORK
Option Description The command line establishment Operation Use the Symbian OS tool to compile and link, use the Microsoft Visual C Compiler / Link to create an action to make an action from the command line. The simulator can also call from the command line. The debugging of the source code layer on the PC simulator needs to be performed in the IDE. The cross-platform compiler and linker of the GNU C for the ARM target device are called from the command line prompt. Microsoft Visual C IDE uses Microsoft Visual C compiler / linkers to build operations to compile and link for the simulator in IDE. The cross-platform compiler and linker of the GNU C for the ARM target device are called from the command line prompt. Borland C IDE is currently available in both IDE selection. Both use the Borland C compiler and linker in the IDE to create an operation. The cross-platform compiler and linker of the GNU C for the ARM target device are called from the command line prompt. Metrowerks CodeWarrior C IDE uses the MetrowerKs compiler and the linker inside the IDE to create an emulator. Call the ARM target device directly from the command line or the CodeWarrior IDE to establish the GNU cross-platform compiler and linker required for the ARM target device.
In the remainder of this article, we use the HelloWorld sample project to demonstrate all steps in the development, debugging, and deployment procedures of the Series 60 simulator.
We also provide other files required by the sample application, such as header file (.h), source file (.cpp), and user interface resource files (.RSS).
You can use the Series 60 emulator to test the application, or start it in an IDE, or run it from the command line prompt. However, debugging applications on the simulator must be performed inside the IDE. After developing, running, testing, and debugging applications on an emulator, you usually want to build and run the program on the target device. So we also demonstrate how to establish sample applications for target devices, how to deploy it, and run it on the target Series 60 hardware.
The development, debugging and initial testing of Series 60 simulator Series 60 applications are generally performed on the PC simulator, which provides an implementation of the SERIES 60 device based on Microsoft Windows. In most cases you will find the operation of the simulator's development process and the operation of the application running on a real device; so your main job can be made before the hardware device can be used. The precise interface of the simulator is very different from the graphics provided, depending on the target platform you use, the version of Series 60 and the selected IDE. In addition, you may also add or delete some buttons or other operating elements to simulate the configuration of a reality device. Similarly, applications that can be used on the simulator also depends on the selection of the platform and device manufacturers. Some differences between simulators and real devices cannot be avoided. Real Series 60 devices may have hardware attachments (eg, photo heads) and other features (for example, background vibration). So sometimes hardware is necessary for development and testing. In addition, the PC-based simulator cannot accurately simulate the problem of application performance and memory management. For PC-based development, editing / compilation / establishment cycle is based on Microsoft Windows Development Tools. However, linking and establishing different from the Win32 or MFC class library, developers will rely on the header files installed by the Series 60 SDK and the class library for the PC format for links and establishment. The binary executable as a result of the binary executable can be run on the PC's simulator. During the development process, the project file of a particular IDE manages all links and established detail information. It ensures that all outputs and other resource files (such as application resource files) required for operation (such as application resource files) are placed and debugged in an emulator environment. According to Figures 1-2, the Series 60 display logically is divided into three areas: status block, main block, and control block.
Figure 1-2. SERIES 60 Simulator
The status block is the scale bar on the top of the screen (blue on the emulator) plus it above the area. The main block is part of the soft button (Soft Key) tag located between the screen and the bottom of the screen and the bottom of the screen. The control block is immediately fast, including a soft button tag. The status block can display some normal information of the current application and some normal information of the device (such as signal strength and battery). It is visible in most situations, but sometimes it is hidden. For example, many games use the entire screen. The main block is the main area of the screen, and the application can display data here. Typically, this area is used as a client rectangular reference, which is usually filled by the application's data display. The control block occupies the lower part of the screen, which shows the label related to the two soft buttons and displays the scroll bar as needed. Similar to the status block, the control block can sometimes be hidden. In this case, in SERIES 60, the pattern is guided to assume that the user can use the Options menu (the default tag of the soft button on the left), even if it is not visible (see the NOKIA Series 60 Game UI provided by Series 60 SDK) Style Guide "). The two buttons below the control block are left and right soft buttons for selecting the currently associated Options menu or tag operation. The four-way navigation buttons can be scrolled up and down, and if you press (click), you can choose. You can make navigate between the objects on the display via the PC mouse or the cursor button to interact with the simulator. We can use the mouse click to select a folder or other displayed object without the need to use four navigation buttons (only on the emulator). We can use the PC keyboard to input data or by clicking on the 12-bit keys on the simulator. Therefore, it is similar to the interaction of the simulator, but is not completely like using real series 60 - there is no pen input on a real device, so all movements and options are done by cursor navigation. Author: Tao Gang build time: 2004-12-03 Source: NEW YORK
