Brew advanced and proficient-3G mobile value-added business operation, customization and development-tools in the 58-brew SDK

Brew simulator in 3. the previous versions of X are called emulator, and 3. the version X and later are called simulator. Only functional improvements are available and there is no essential difference. For convenience, the concept of simulator is used here. The Brew simulator can be used to simulate various handheld devices and test applications and extensions developed in the brew environment.

The MIF editor is used to create mfx and MIF files. In earlier versions of brew3.x, only the MIF file is used. mfx is an intermediate file in the XML format used during the development of MIF. Starting from 3.x, MIF is a special type of resource file compiled from the mfx file, which contains information about the module (MOD) file. After creating the command line, the command line is loaded to the target device in binary format. When running an application on a simulator, you must also use the command line interface (MIF.

Before learning about the functions of the MIF editor, you must first understand the concept of classid. The classid in brew must be unique. No two or more applications must have the same classid. If the classid cannot be unique, the aee in the device will be confused when the two classes with the same classid appear in the same mobile phone, and only one of them can be found. As the end user may save the combination of many applications in wireless devices during the download process, the consequences of the uniqueness of classid cannot be guaranteed. You can get the classid In the MIF Editor, or log on to the brew developer's external network and use the brew classid generator to obtain the classid. In this way, a file with the extension. Bid can be generated and downloaded and included in the application. Each bid file contains a unique 32-bit type ID with a specified name (for example, aeeclsid_app ). The classid is stored in MIF, while the bid file is included in the module's source file (for example, app. C. This allows the application to create an instance based on the classid provided by aee.

Enter the necessary information in the MIF editor and compile mfx into MIF. You can use an image suitable for different device displays to create multiple MIF. After the application compiles the link, it generates an executable file, which generates app. DLL for the simulator and App. mod for the target device. To load this application on the simulator, you must specify the directories containing app. MIF and App. dll. When you select to execute this application, the simulator loads app. DLL to create and run the application.

Each brew module contains one or more applications, or extension applications.

It also contains text strings for each application and one or more graphic icons that represent the application in the runable Application menu. It also contains other information that can determine the permission level of the module and the notifications that the application can receive from other applications.

On the mobile phone, the MIF is at the same level as the folder containing the directory of each module. The name of the Module Directory is the same as that of the MIF prefix. The simulator allows you to select a directory independent of the module executable files to simulate application execution on multiple devices.

The resource editor can create resource files that support different mobile phones and languages. By separating resources from the code and loading them at run time, you can avoid confusion between the source code and the independent editing mark of each supported language and mobile phone. The resource editor can use the following file formats:

Brx is an intermediate file in XML format. You can use the resource editor to edit and save the final output. The resource editor does not require this intermediate file to use the brx extension, as long as the file contains valid data in the correct XML format, no matter what the extension is, the resource editor can interpret it. Bar is a binary file generated by the resource compiler as part of the final output. BRH is a header file generated by the resource compiler as part of the final output.

Brew 3.x earlier versions use the binary intermediate format with the bri extension. To be compatible, the resource editor still supports this format, but we recommend that you convert all Bri files to brx files.

 

The mobile phone device configurator can be used to create and configure the device files used by the simulator, that is, the software and hardware properties files related to the mobile phone. Then test applications on various devices through the simulator. The device file first contains the image of the device to be configured, which is generally generated by the image of the actual device. The next step is the image area of each device's buttons. Then, you can define the buttons and the event code that each button will send to the application. You can also define the screen size, Font, supported language, and color depth of the device.

Devices organized by the mobile device configurator include the following components: Device Files (qsc/dpk), which encode information such as general device properties and specific device objects and their properties. It also contains references to device image files. Bitmap image files include the main image file and optional image files generated by pressing the button. In addition, the device and image file must be in the same directory.

For versions 3.x and later, CP/SP generally only uses the mobile phone device configurator to view the information of mobile phone devices, without any other modifications.