Resources | developer.brewmp.com Resources | developer.brewmp.com

Developer

resources

Brew MP classes and MIFs

Brew MP classes and MIFs

Each Brew® MP module contains one or more Brew MP classes. These classes can be both applet and non-applet classes and are identified by ClassIDs. The applet classes can be run by the device user, while the non-applet classes can implement services used by the module's applet classes. These services are available to the classes of other modules as well.

The MIF contains unique ClassIDs for each of the module's classes and specifies which classes are exported for use by other modules. For each applet class, the MIF contains a text string and one or more graphic icons used to show the applet in the menu of applets available to run. The MIF contains other information that determines the module's privilege level (Brew MP API functions that can be invoked by the module's classes), and the notifications that the module can receive from other Brew MP classes.

The Resource Manager displays applet class specific information contained in the MIF such as applet ClassID, applet name, notifications registered, flags and privileges. Resource Manager also displays module-specific information such as privilege level, dependencies on other classes, access control information, EFS restrictions, MIME types and their handlers, author name, copyright and module version.

To create a MIF for a Brew MP module, you need a Brew MP ClassID (.bid, .h or .idl) file for each class and applet that the module contains. You can get ClassIDs from the Brew MP website.

Each .bid, .h or .idl file contains a unique, 32-bit ClassID and assigns it a name (for example, AEECLSID_APP). The ClassIDs are stored in the MIF, and the .bid, .h or .idl files are included in the module source file (for example, app.c). This allows the module to create an instance of any of its classes given a ClassID supplied by the Brew MP AEE.