Download  Print this page

Sun Microsystems Computer Accessories User Manual

Sun microsystems computer accessories user manual
Hide thumbs

Advertisement

Basic Customization Guide
Wireless Toolkit, Version 2.1
TM
Java
2 Platform, Micro Edition
Sun Microsystems, Inc.
4159 Network Circle
Santa Clara, CA 95054
U.S.A. 650-960-1300
December 2003

Advertisement

Table of Contents
loading

  Related Manuals for Sun Microsystems Computer Accessories

No related manuals

  Summary of Contents for Sun Microsystems Computer Accessories

  • Page 1 Basic Customization Guide Wireless Toolkit, Version 2.1 Java 2 Platform, Micro Edition Sun Microsystems, Inc. 4159 Network Circle Santa Clara, CA 95054 U.S.A. 650-960-1300 December 2003...
  • Page 2 Sun, Sun Microsystems, le logo Sun, Java, Solaris, Sun[tm] ONE Studio, Java 2 Platform, Micro Edition, Wireless Toolkit, J2SE, JDK et le logo Java Coffee Cup sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.
  • Page 3: Table Of Contents

    Contents Preface xi Customizing the Wireless Toolkit 1 How to Customize the Wireless Toolkit 1 Customization Steps 2 Device Property Files and the Default Emulator 2 Creating Device Property Files 5 Make a Copy of an Existing Main Device Property File 5 Obtain and Enter Image Files 6 Obtain and Enter the Screen Properties 7 Screen Location 7...
  • Page 4 Examining Device Property Files 17 Device Property Files 18 Main Device Property File 19 Fonts 19 Fonts Used by the MIDP APIs 19 Default Font 20 System Fonts 20 Bitmap Fonts 20 Font Underlining 22 The Device Image 22 Image without Buttons Pressed 23 Image with Buttons Pressed 23 Image with Buttons Highlighted and Backlight On 23 Scaling 23...
  • Page 5 Assigning Abstract Commands to Buttons 33 Displayed Icons 38 Defining the Icon Location and States 38 Soft Button Label Display 39 Color 40 Sound Alerts 40 Device Software Capabilities 41 Locales 42 Character Encodings 42 Transparent Images 43 Default Emulator Device Property Files 45 Property Files 45 DefaultGrayPhone.properties 46...
  • Page 6 Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 7 Figures FIGURE 1 Specifying Screen Properties 9 FIGURE 2 Specifying a Button Location 11 FIGURE 3 Soft Button Label Areas on the Emulated Device Display 13 FIGURE 4 Specifying Emulator Fonts 21 FIGURE 5 Specifying Screen Properties 25 FIGURE 6 Specifying a Button Location 31 FIGURE 7 Soft Button Labels on the Emulated Device Display 39...
  • Page 8 viii Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 9 Tables TABLE 1 Example of Device Property Files and DefaultGrayPhone Property File 18 TABLE 2 Button Names Available 29 TABLE 3 Abstract Command Types in Order of Precedence 33 TABLE 4 Alert Type Values 41 TABLE 5 Example of Device Property Files 45 TABLE 6 Icon Image Files 53...
  • Page 10 Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 11: Preface

    Preface ™ The Java 2 Platform, Micro Edition, Wireless Toolkit Basic Customization Guide describes how to customize the J2ME property files. Who Should Use This Book This guide is intended for developers who need to configure the J2ME Wireless Toolkit to accommodate device emulators other than the ones provided by the Wireless Toolkit.
  • Page 12 screen properties, button properties, soft button label areas, and icon properties. The tutorial also explains how to set color properties and how to run the emulator for the new device. Chapter 3 describes in depth the components of a device definition and explains how to create a device definition.
  • Page 13: Typographic Conventions

    Typographic Conventions Typeface Meaning The names of commands, files, AaBbCc123 and directories; on-screen computer output What you type, when AaBbCc123 contrasted with on-screen computer output AaBbCc123 Book titles, new words or terms, words to be emphasized Command-line variable; replace with a real name or value Shell Prompts Shell C shell...
  • Page 14 Application CLDC - JSR 30, JSR 139 WMA - JSR 120 MMAPI - JSR 135 JTWI - JSR 185 J2ME Web Services JSR 172 Accessing Sun Documentation Online The Java Developer Connection technical documentation on the Web. http://developer.java.sun.com/developer/infodocs/ Sun Welcomes Your Comments We are interested in improving our documentation and welcome your comments and suggestions.
  • Page 15: Customizing The Wireless Toolkit

    C H A P T E R Customizing the Wireless Toolkit The Java 2 Platform, Micro Edition Wireless Toolkit (J2ME provides an emulation environment for the development of applications compliant with the Mobile Information Device Profile (MIDP). The Java 2 Platform, Micro Edition Wireless Toolkit Basic Customization Guide provides technical details for configuring the toolkit to accommodate new device emulators.
  • Page 16: Customization Steps

    Customization Steps You customize the J2ME Wireless Toolkit for a new device in three simple steps: 1. Obtain the default J2ME Wireless Toolkit. The toolkit includes a default development environment and a Default Emulator. The Default Emulator is supplied with sets of device property files that enable the emulation of several generic wireless devices.
  • Page 17 For example, suppose the J2ME Wireless Toolkit is installed in the directory C:\WTK21. Then, the Main Device Property File for the device DefaultColorPhone is located at C:\WTK21\wtklib\devices\DefaultColorPhone\DefaultColorPhone.pro perties. For the remainder of this document, {j2mewtk.dir}, denotes the installation directory of the J2ME Wireless Toolkit. Chapter 1 Customizing the Wireless Toolkit...
  • Page 18 Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 19: Creating Device Property Files

    C H A P T E R Creating Device Property Files This chapter presents a simple tutorial that walks you through the procedures for creating a device property file. You will learn how to use the new device property files to enable the J2ME Wireless Toolkit to emulate applications for the device. See Chapter 3, “Examining Device Property properties, the custom-tailoring options available, and how to use them.
  • Page 20: Obtain And Enter Image Files

    Note – All directory names in this chapter refer to the installation directory of the J2ME Wireless Toolkit. (If you chose the default option at installation, the directory is C:\WTK21.) 1. Copy the directory wtklib\devices\DefaultColorPhone and its contents as wtklib\devices\NewPhone. 2.
  • Page 21: Obtain And Enter The Screen Properties

    pressed_buttons_image = ph1_press.png highlighted_image = ph1_highlight.png 4. Change the indicator image locations in the following lines in NewPhone.properties, if they are different from the existing locations. The network indicator location property has the following format: netindicator.bounds = x, y, width, height Where x is a horizontal distance in pixels to the network’s indicator left top corner, y is a vertical distance to the network’s indicator left top corner, width is and indicator’s image width and height is an indicator image’s height.
  • Page 22: Total Screen Size

    Total Screen Size Referring to the left image in FIGURE 1, you specify the total screen size by two lines of the form: screen.width = <horizontal distance in pixels> screen.height = <vertical distance in pixels> Enter the following measured values for the total screen size in NewPhone.properties: screen.width = 96 screen.height = 128...
  • Page 23: Display Area In Full Screen Mode

    Screen Location Full Dimension Name: screen.<dimension> width height Specifying Screen Properties FIGURE 1 Display Area in Full Screen Mode The MIDP 2.0 specification allows applications to use the full screen area. The Default Emulator defines the coordinates for a full screen as follows: Upper left coordinate - the upper left coordinate of the display area: (screenPaintableRegion.x, screenPaintableRegion.y).
  • Page 24: Obtain And Enter The Button Properties

    Bottom right coordinate - the bottom right coordinate of the screen area: (screen.x+screen.width, screen.y+screen.height). Customization of the display area will be available in future versions of the Wireless Toolkit. Obtain and Enter the Button Properties 1. By measuring the image file, obtain the button properties. A button on the emulated device is defined in the main device property file by name and screen location in the following form: button.<button_name>...
  • Page 25: Figure 2 Specifying A Button Location

    height width Specifying a Button Location FIGURE 2 2. Enter the following measured values for the button properties in NewPhone.properties: button.0 = 66, 417, 41, 22 button.1 = 21, 319, 41, 22 button.2 = 66, 320, 41, 22 button.3 = 110, 320, 41, 22 button.4 = 20, 352, 41, 22 button.5 = 65, 352, 41, 22 button.6 = 112, 352, 41, 22...
  • Page 26: Obtain And Enter Soft Button Label Areas

    button.7 = 21, 384, 41, 22 button.8 = 65, 384, 41, 22 button.9 = 111, 384, 41, 22 button.POUND = 110, 417, 41, 22 button.ASTERISK = 21, 417, 41, 22 button.SEND = 25, 295, 32, 17 button.END = 114, 295, 32, 17 button.LEFT = 37, 254, 26, 26 button.RIGHT = 114, 253, 23, 27 button.UP = 69, 232, 35, 22...
  • Page 27: Figure 3 Soft Button Label Areas On The Emulated Device Display

    Soft button labels Soft Button Label Areas on the Emulated Device Display FIGURE 3 A soft button label display is defined by a line of the form: softbutton.<number> = <x>,<y>,<width>,<height>,<font>,<align> where the parameters are defined as follows: The coordinates of the soft button label area: x: The x-coordinate of the left edge of the label area, in pixels relative to the left edge of the screen area y: The y-coordinate of the top edge of the label area, in pixels relative to the...
  • Page 28: Obtain And Enter Icon Properties

    softbutton.0=1,112,40,16, softButton, left softbutton.1=56,112,40,16, softButton, right Obtain and Enter Icon Properties An icon in the context of the Emulator is any graphic, constant or variable, that is displayed on the device screen global region (the region that is outside of the drawable area).
  • Page 29 icon.<name> = <x_location>,<y_location>,<initial_state> The icon states are defined by lines of the form: icon.<name>.<state #1> = <state #1 image_filename> icon.<name>.<state #n> = <state #n image_filename> If an icon does not have an image for a particular state, only the name of the icon need be given, and the image field can be left blank.
  • Page 30: Enter Color Properties

    Enter Color Properties Two properties are provided to control the color in the Emulator: The isColor property determines whether the display is grayscale (false) or color (true). The colorCount property controls the number of colors available (when isColor is true) or the number of shades of gray available (when isColor is false).
  • Page 31: Examining Device Property Files

    C H A P T E R Examining Device Property Files This chapter explains in detail the structure and content of device property files for an emulated device. The following is the list of the main behavior items that can be specified in the device property files: device image locations of buttons, and association of PC keys with device buttons...
  • Page 32: Device Property Files

    Device Property Files The device property files consist of a set of files that define the device’s behavior and appearance. Each set of device property files is located in a directory whose name determines the name of the device. {j2mewtk.dir} is used to refer to the directory in which the J2ME Wireless Toolkit is installed.
  • Page 33: Main Device Property File

    Main Device Property File This section describes the device property file that the Default Emulator uses to emulate a device. The Main Device Property file is named in the directory <device_name> where device_name is the name of the device being emulated.
  • Page 34: Default Font

    The font definition is according to the format for describing a system font (see “System Fonts” on page 20) or a bitmap font (see “Bitmap Fonts” on page 20). Example font.system.italic.small: Helvetica-italic-9 The default font (see “Default Font”) is used for any MIDP font combination that is not defined.
  • Page 35: Figure 4 Specifying Emulator Fonts

    Example font.softButton = bitmap_font.properties font.system.bold.medium = bold_font.properties A font property file contains definitions for the following properties: font_image = <image_filename> font_height = <pixel_height_font> font_ascent = <pixel_ascent_font> font_descent = <pixel_descent_font> font_leading = <pixel_space_between_lines_of_text> The first property, font_image, refers to an image file, in PNG, GIF or JPEG format, that contains the font bitmap.
  • Page 36: Font Underlining

    ascii_x-254 = 1149 ascii_x-255 = 1154 ascii_x-256 = 1160 Note – This type of font supports only eight bit ASCII values (256 characters) and not 16 bit unicode characters. Font Underlining The MIDP specification allows underlined fonts. By default, the emulator supports font underlining.
  • Page 37: Image Without Buttons Pressed

    An image with all the active buttons pressed—to show a button being pressed when the user selects it An image with all the active buttons highlighted—to provide a visual indication that the pointer is sufficiently positioned over a button that a mouse click will activate the button.
  • Page 38: Screen Properties

    Screen Properties In this section you specify the properties of the image of the device screen. You need to specify the following screen properties: Screen Location Total Screen Size Display Area Screen Pixel Ratio Screen Background Color Touch Screen Wireless Toolkit Basic Customization Guide • December 2003 (optional) (optional) (optional)
  • Page 39: Screen Location

    Screen Location Full Dimension Name: screen.<dimension> width height Specifying Screen Properties FIGURE 5 Screen Location Referring to the left image in corner of the screen relative to the top left corner of the device image by two lines of the form: Display Area Full Dimension Name: screenPaintableRegion.<dimension>...
  • Page 40: Total Screen Size

    screen.x = <horizontal distance in pixels> screen.y = <vertical distance in pixels> For example: screen.x = 38 screen.y = 82 Total Screen Size Referring to the left image in FIGURE 5 on page 25, you specify the total screen size by two lines of the form: screen.width = <horizontal distance in pixels>...
  • Page 41: Screen Pixel Ratio

    Referring to the right image in FIGURE 5, the full screen display area is defined as the upper left coordinate of the display area, (screenPaintableRegion.x, screenPaintableRegion.y), and the bottom right coordinate of the screen area (screen.x+screen.width, screen.y+screen.height). Customization of the display area will be available in future versions of the Wireless Toolkit.
  • Page 42: Screen Border Color

    Screen Border Color You have the option of setting the color of the icon area, the softbutton area (non- paintable areas), and the device menu. Screen background color is used if this value is not defined. The color is defined as a hexadecimal integer according to the standard Java color map.
  • Page 43: Device Buttons

    Device Buttons This section describes how to define a button on an emulated device and also describes the assignments associated with the buttons including: Assigning a keyboard key press to a button press Assigning a game key to a button press Specifying the character generated by a button press Assigning an abstract command to a button press Keyboard Handler...
  • Page 44 x: The x-coordinate of the left edge of the button image, in pixels relative to the left edge of the device image y: The y-coordinate of the top edge of the button image, in pixels relative to the top edge of the device image width: The width of the button image, in pixels height: The height of the button image, in pixels.
  • Page 45: Assigning A Pc Keyboard Key To A Button

    x1,y1 x2,y2 x7,y7 x3,y3 x6,y6 height x5,y5 x4,y4 width Rectangular Button Form Polygon Button Form Specifying a Button Location FIGURE 6 Assigning a PC Keyboard Key to a Button You can assign a key on the PC keyboard to a device button in order to simulate a button press by pressing the key (instead of clicking on the button with the mouse).
  • Page 46: Assigning A Game Action To A Button

    Note – Virtual key codes are defined by the Abstract Window Toolkit in Java 2 Standard Edition. The definitions are found in the class java.awt.event.KeyEvent at http://java.sun.com/j2se/1.4/docs/api/java/awt/event/ KeyEvent.html For example, key.LEFT = VK_LEFT More than one PC key may be assigned to a single button, using the form: key.<button_name>...
  • Page 47: Assigning Abstract Commands To Buttons

    There are two ways you can do a button press at the same time as pressing Shift or Alt: Map the buttons to the keyboard, as in the previous section, and press the key associated with the button at the same time as the Shift or Alt keys Press the button Shift-Lock or Alt-Lock and then do the button press.
  • Page 48 Abstract Command Types in Order of Precedence TABLE 3 Command Type SCREEN ITEM HELP The MIDP implementation in the Wireless Toolkit allocates a command issued by the application to a device button based on the following considerations: 1. The first consideration is the natural correspondence between the command’s type and a input signal such as a button press.
  • Page 49 2. Use the definition command.keys.<command_type> to assign command types to preferred buttons according to their natural correspondence. See Abstract Command Type to a Button” on page 35 3. Use the secondary button assignments to specify alternate buttons for assigning commands of lower priority. See Note –...
  • Page 50 command.keys.BACK = SOFT1 command.keys.EXIT = SOFT1 command.keys.CANCEL = SOFT1 command.keys.STOP = SOFT1 command.keys.OK = SOFT2 command.keys.SCREEN = SOFT2 command.keys.ITEM = SOFT2 command.keys.HELP = SOFT2 In cases of conflict in the mapping of actual commands to keys, commands are mapped first by command type and then by priority. Secondary Button Assignments Secondary buttons may be defined for a command type.
  • Page 51 The Abstract Command Menu When there are more abstract commands specified by an application than there are buttons to which they can be mapped, the unmapped abstract commands are placed in a command menu. The following operations are defined for the command menu: Display/hide menu Select menu item...
  • Page 52: Displayed Icons

    Displayed Icons An icon in the context of the Emulator is any graphic, constant or variable, that is displayed on the device screen global region (the region that is outside of the drawable area). This includes scrolling indicators, the battery level indicator and any other images of a similar type.
  • Page 53: Soft Button Label Display

    icon.reception: 0, 0, on icon.reception.on: reception.gif icon.battery: 80, 0, full icon.battery.full: batt_3.gif icon.battery.half: batt_2.gif icon.battery.low: batt_1.gif icon.battery.none: batt_0.gif Soft Button Label Display On devices with soft buttons, soft button labels are displayed in the area of the screen that is available to icons. This area is not directly accessible to the application.
  • Page 54: Color

    softbutton.<number> = <x>,<y>,<width>,<height>,<font>,<align> where the parameters are defined as follows: The coordinates of the soft button label: x: The x-coordinate of the left edge of the label area, in pixels relative to the left edge of the screen area y: The y-coordinate of the top edge of the label area, in pixels relative to the top edge of the screen area width: The width of the label, in pixels height: The height of the label, in pixels...
  • Page 55: Device Software Capabilities

    alert.<alert_type>.sound = <sound_file> where the possible values of <alert_type> are as defined by MIDP specification as follows: Alert Type Values TABLE 4 Alert Type Description info Typically provides non-threatening information to the user. error Alerts the user to an erroneous operation. warning Warns the user of a potentially dangerous operation.
  • Page 56: Locales

    Locales A locale is a geographic or political region or community that shares the same language, customs, or cultural convention. In software, a locale is a collection of files, data, and code, which contains the information necessary to adapt software to a specific geographical location.
  • Page 57: Transparent Images

    microedition.encoding: UTF-8 microedition.encoding.supported: UTF-8, UTF-16, ISO-8859-1, ISO-8859-2, Shift_JIS To support all encodings supported by the J2ME platform, leave the microedition.encoding.supported definition blank, as in: microedition.encoding.supported: Note – The encoding ISO-8859-1 is always available to applications running on emulated devices, whether or not it is listed in the microedition.encoding.supported entry.
  • Page 58 Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 59: Default Emulator Device Property Files

    A P P E N D I X Default Emulator Device Property Files This appendix presents a list of the device property files provided with the Default Emulator and information on the Default Emulator properties. Property Files The following property files are used. Example of Device Property Files TABLE 5 Property File...
  • Page 60: Defaultgrayphone.properties

    Example of Device Property Files TABLE 5 Property File {j2mewtk.dir}\wtklib\devices\Share\reception.gif {j2mewtk.dir}\wtklib\devices\Share\right.gif {j2mewtk.dir}\wtklib\devices\Share\secure.gif {j2mewtk.dir}\wtklib\devices\Share\sym.gif {j2mewtk.dir}\wtklib\devices\Share\trusted.png {j2mewtk.dir}\wtklib\devices\Share\unsecure.gif {j2mewtk.dir}\wtklib\devices\Share\up.gif DefaultGrayPhone.properties default_image=..\Share\ph1_neut.png pressed_buttons_image=..\Share\ph1_press.png highlighted_image=..\Share\ph1_highlight.png ## screen properties ## # Screen location, relative to the top-left corner of the # telephone's image ############### screen.x=30 screen.y=131 # Screen size in pixels ############### screen.width=180...
  • Page 61 screenPixelRatio.x = 1 screenPixelRatio.y = 1 # Touchscreen support ############### touch_screen=false # Screen Background RGB Color # examples: 0xffffff = white, 0x000000 = black ############### screenBGColor=0x8f9f8f # Screen border RGB color is a color of softbuttons and icons # area. If not defined, screen background color is used # example: screenBorderColor = 0xf0f0f ############### screenBorderColor=0xb6b6aa...
  • Page 62 button.SELECT = 97, 370, 50, 28 button.DOWN = 97, 398, 50, 22 button.CLEAR = 92, 426, 58, 31 button.SOFT1 = 31, 350, 39, 31 button.SOFT2 = 175, 350, 36, 31 button.POWER = 157, 53, 30, 30 command.keys.BACK = SOFT1 command.keys.EXIT = SOFT1 command.keys.CANCEL = SOFT1 command.keys.STOP = SOFT1 command.keys.OK = SOFT2...
  • Page 63 # <face> is one of # system, monospace, proportional # <style> is one of # plain, bold, italic # <size> is one of # small, medium, large # Default font is defined by # font.default=<font properties filename> | <system font definition> # Soft Button font defined by # font.softButton=<font properties filename>...
  • Page 64 font.monospace.italic.large: Monospaced-italic-14 font.monospace.bold.italic.small: Monospaced-bolditalic-9 font.monospace.bold.italic.medium: Monospaced-bolditalic-11 font.monospace.bold.italic.large: Monospaced-bolditalic-14 font.proportional.plain.small: SansSerif-plain-9 font.proportional.plain.medium: SansSerif-plain-11 font.proportional.plain.large: SansSerif-plain-14 font.proportional.bold.small: SansSerif-bold-9 font.proportional.bold.medium: SansSerif-bold-11 font.proportional.bold.large: SansSerif-bold-14 font.proportional.italic.small: SansSerif-italic-9 font.proportional.italic.medium: SansSerif-italic-11 font.proportional.italic.large: SansSerif-italic-14 font.proportional.bold.italic.small: SansSerif-bolditalic-9 font.proportional.bold.italic.medium: SansSerif-bolditalic-11 font.proportional.bold.italic.large: SansSerif-bolditalic-14 # Font underlining : # Font underlining is enabled by default. It is possible to disable font underlining with # font.all.underline.enabled=false # or per font with...
  • Page 65 icon.down.on: ..\Share\down.gif icon.left: 78, 194, off icon.left.off: icon.left.on: ..\Share\left.gif icon.right: 94, 194, off icon.right.off: icon.right.on: ..\Share\right.gif icon.internet: 64, 1, off icon.internet.off: icon.internet.on: ..\Share\internet.gif icon.reception: 2, 1, on icon.reception.on: ..\Share\reception.gif icon.battery: 164, 2, on icon.battery.on: ..\Share\batt.gif icon.inmode: 83, 2, off icon.inmode.off: icon.inmode.ABC: ..\Share\ABC.gif icon.inmode.abc: ..\Share\abc_lower.gif icon.inmode.123: ..\Share\123.gif...
  • Page 66 alert.error.sound: ..\Share\mid_err.wav alert.confirmation.sound: ..\Share\mid_confirm.wav # Softbuttons support: # softbutton.<number>=<x location>,<y location>,<width>,<height>,<font> # Coordinates are relative to the origin of the screen area. softbutton.0=1,192,78,16, softButton, left softbutton.1=99,192,78,16, softButton, right # Gamma value for gamma-correction # Default value is 1, which means that no gamma-correction is actually performed gamma=2 # Color/Grayscale screen support:...
  • Page 67: Device Image Files

    Device Image Files ph1_neut.png ph1_press.png Images of Device Key Press States FIGURE 8 Icon Image Files The following table lists filenames and their associated images: Icon Image Files TABLE 6 Filename Image batt.gif down.gif up.gif ph1_highlight.png Appendix A Default Emulator Device Property Files...
  • Page 68 Icon Image Files TABLE 6 Filename Image internet.gif reception.gif right.gif left.gif sym.gif kana.gif hira.gif ABC.gif abc_lower.gif 123.gif secure.gif unsecure.gif trusted.gif Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 69: Support For Bytecode Obfuscators

    A P P E N D I X Support for ByteCode Obfuscators The Wireless Toolkit contains a support framework for bytecode obfuscators. It also includes a plug-in for this framework for the ProGuard and Retroguard bytecode obfuscators. You can use a bytecode obfuscator other than ProGuard or RetroGuard, however, you must manually implement the plug-in for it.
  • Page 70: Example

    run(File jarFileObfuscated, String wtkBinDir, String wtkLibDir, String jarFilename, String projectDir, String classPath, String emptyApi) where jarFileObfuscated is the file that holds the obfuscated JAR wtkBinDir is the directory holding the Wireless Toolkit binary files wtkLibDir is the directory holding the Wireless Toolkit JAR files jarFilename is the full path to the JAR file to be obfuscated projectDir is the full path to the main directory of your project classPath is the full path to the set of files that make up the API classpath for...
  • Page 71 You can get the proguard.jar file by downloading the .zip file from and extracting the .jar file. The http://proguard.sourceforge.net/ proguard.jar file must be placed in the Wireless Toolkit’s bin directory: {j2mewtk.dir}\bin. Appendix B Support for ByteCode Obfuscators...
  • Page 72 Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 73: Connecting To The Wireless Toolkit's Wma Emulation Environment

    A P P E N D I X Connecting to the Wireless Toolkit’s WMA Emulation Environment The J2ME Wireless Toolkit supports the Wireless Messaging API (WMA), which enables you to send and receive SMS or CBS messages. The Wireless Toolkit’s support for messaging includes automatically assigning phone numbers to emulators and routing messages between them.
  • Page 74 Wireless Toolkit Basic Customization Guide • December 2003...
  • Page 75: Index

    Index abstract command types assigning to a button, 35 abstract commands assigning to buttons, 33 menu operations, 37 table of, 33 abstract commands, types of, 33 ascii_x-n, 21 bitmap font definition, 20 button assignments, emulating, 34 button properties, setting, 10 byte code obfuscator, 55 character encodings, 42 code obfuscators, adding support for, 55...
  • Page 76 font_image property, 21 game actions, mapping to buttons, 32 generated characters, assigning to buttons, 32 icons setting initial state, 14 setting properties, 14 setting screen location, 14 image files creating and modifying, 6 formats, 23 isColor property, 40 keyboard keys, setting to buttons, 31 keyboard.handler property, 29 Main Device Property file, 2 path, 19...
  • Page 77 device property files, 1 WMA messages, customizing, 59 Index...
  • Page 78 Wireless Toolkit Basic Customization Guide • December 2003...