Sun Microsystems J2ME User Manual Page 48
- Page / 134
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
36 J2ME Wireless Toolkit User’s Guide • October 2004
When the emulator is running, choose MIDlet > Pause from the emulator
window’s menu. The running MIDlet is paused and the screen displays an
“Incoming Call...” message.
To resume the MIDlet’s operation, choose MIDlet > Resume from the menu.
4.5 Running the Emulator Solo
During development, you will most often run the emulator directly from KToolbar
by pressing the Run button or using the Project > Run via OTA feature. For testing
or demonstrations, you might wish to run the emulator by itself. Several different
approaches are described in this section. The program group created by the J2ME
Wireless Toolkit installer includes several items that pertain to running the
emulator by itself.
To run an application directly, which is analagous to pressing KToolbar’s Run
button, choose the Run MIDP Application... item. The toolkit prompts you to
locate a MIDlet descriptor file on your local disk. Note that the corresponding
MIDlet suite JAR must also be present.
To run the emulator’s Application Management Software (AMS), choose the OTA
Provisioning item, which is roughly analagous to KToolbar’s Run via OTA feature.
The emulator pops up with the AMS welcome screen, and you can install
applications by typing in a URL.
To change the emulator’s preferences, choose the Preferences item from the toolkit
program group. This pulls up the same preferences window as choosing Edit >
Preferences... from the KToolbar menu.
The J2ME Wireless Toolkit utilities are also accessible without running KToolbar.
Just choose the Utilities item.
Finally, you can change which emulator skin is used by default. Choose the
Default Device Selection item, and choose one of the available emulator skins.
Next time you launch the emulator the selected skin is used.
You can also run the emulator from a command prompt. See Appendix B,
“Command Line Reference,” for more information.
4.6 Using Third Party Emulators
Third party companies, like device manufacturers and wireless carriers, sometimes
create device emulators that are compatible with the J2ME Wireless Toolkit. You
can gain experience running your application on a wider variety of
implementations by installing additional emulators into the toolkit. The procedure
- User’s Guide 1
- Contents 3
- Contents v 5
- Contents vii 7
- Index 119 8
- Who Should Use This Book 9
- Related Documentation 9
- How This Book Is Organized 10
- Preface xi 11
- Typographic Conventions 12
- We Welcome Your Comments 12
- Introduction 13
- 1.2 The Tools in the Toolkit 14
- 1.3 Toolkit Features 15
- 1.4 Supported Technology 15
- Developing MIDlet Suites 17
- The KToolbar window 18
- Creating a new project 18
- 2.2.1 Edit Source Code 19
- 2.2.2 Build 20
- 2.2.3 Run 21
- List of project MIDlets 22
- TinyMIDlet in action 22
- 2.3.1 Package 23
- 2.3.2 Install 24
- URL prompt 25
- Confirming the installation 25
- 2.3.3 Run 26
- 2.4 Using an Obfuscator 27
- 2.5 Using a Debugger 29
- ■ From the command line, run: 30
- The project settings window 32
- 3.3 Manipulating MIDlets 35
- 3.4 Using the Push Registry 36
- Project directory structure 37
- 3.7 Configuring KToolbar 38
- Using the Emulator 41
- 4.2 Using the Emulator 42
- 4.3.1 Network Proxies 44
- 4.3.2 Heap Size 45
- 4.3.3 Storage and Cleaning 45
- 4.4 Pausing and Resuming 47
- 4.5 Running the Emulator Solo 48
- Monitoring Applications 51
- Turning on the profiler 52
- The method profiler 52
- 5.1.1 The Call Graph 53
- 5.2 Using the Memory Monitor 54
- 5.3 Using the Network Monitor 56
- 5.3.1 Filtering Messages 57
- 5.3.2 Sorting Messages 58
- Information 58
- Security and MIDlet Signing 61
- 6.2 Protection Domains 62
- 6.3 Signing a MIDlet Suite 63
- 6.4 Managing Keys 64
- 6.4.2 Getting Real Keys 65
- 6.5 Managing Certificates 66
- 6.5.1 Importing Certificates 67
- 6.5.2 Removing Certificates 68
- Setting WMA preferences 70
- The WMA console 71
- Sending a binary message 73
- 7.3.4 Sending MMS Messages 74
- Using the Mobile Media API 77
- 8.2 Using MediaControlSkin 78
- 8.3 Media Capture 78
- 8.4 Well-Behaved MIDlets 78
- 9.1 JSR 184 Overview 79
- 9.2 Immediate Mode 79
- 9.4 Trading Quality for Speed 80
- 9.3 Retained Mode 80
- 10.1 The FileConnection API 83
- 10.2 The PIM API 84
- Using the Bluetooth and OBEX 85
- 11.3.1 OBEX Preferences 86
- BCC properties 87
- Using Web Services 89
- Application Demonstrations 91
- WMADemo is contained in 92
- A.2 General Instructions 93
- A.3 BluetoothDemo 94
- A.4 Demo3D 96
- A.4.2 PogoRoo 97
- A.4.3 retainedmode 98
- A.5 JSR172Demo 99
- A.6 mmademo 99
- A.6.1 Simple Tones 100
- A.6.2 Simple Player 100
- Simple Player commands 101
- A.6.3 PausingAudioTest 102
- A.6.4 Video 102
- A.7 ObexDemo 103
- A.8 PDAPDemo 106
- A.8.2 The PIM API 108
- An empty contact list 109
- Adding contact fields 109
- A.9 WMADemo 110
- Sending a text message 111
- An incoming text message 112
- Addressing an MMS message 113
- WMADemo receives the image 114
- Command Line Reference 115
- B.2.1 Build 116
- B.2.2 Package 117
- B.2.3 Run 118
- B.2.4 Debugging 119
- Toolkit component commands 120
- B.5 Using Security Features 122
- B.5.2 Signing MIDlet Suites 123
- B.5.3 Managing Certificates 124
- B.6 Using the Stub Generator 125
- B.6.1.1 Example 126
- Internationalization 127
- C.2 Emulated Locale 128
- C.3 Character Encodings 128
- Index 121 133
Related products and manuals for Software manuals Sun Microsystems J2ME
(256 pages)
(50 pages)© 2020, manymanuals.com. All rights reserved. | 0.527 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals