The award-winning J2ME Wireless Toolkit has become the fact that the J2ME development application is a standard toolkit. Since the beginning of 2000, the toolkit has been developing to catch up with the step of moving the Java technology appearance. Do not be misleaded by small changes since version 2.1. The new toolkit supports the new optional APIs specified by the four important areas to support Java Community Process (JCP), 3D graphics, multimedia communication, Bluetooth Networking, and data management. This article will describe these new APIs and show you how to implement them in the toolkit.
Before this, let us praise the updated DefaultColorPhone simulator skin. Since the 2.1 version, the skin has a larger screen (320 x 240, or qvga) and more colors (4096 color rather than 256 color).
Mobile 3D graphics
JSR 184, MOBILE 3D graphics API for J2ME (M3G) provides three-dimensional graphics function in an integrated package, suitable for supporting the most widely used J2ME Software Stack, Limited Connection Device Configuration (CLDC), and Mobile Information Device Description (MIDP) )device of. The API provides two APIs for display 3D content. Immediate mode API enables the application to create and manipulate 3D elements directly. This layer is a scene map API, also known as the retention mode, which can load and display the entire 3D scene that has been designed early. The application can adopt the most suitable API, or a combination of retention mode and immediate mode. The JSR 184 specification also defines a file format -.m3g for the scene map.
The toolkit simulator fully supports JSR 184, and several MIDLETs show the functionality of the API in the Demo3D project.
Life3D demonstrates the use of immediate mode:
Pogoroo is an interaction show that it is characterized by displaying a jumping kangaroo:
Finally, retainedmode shows how to load and present the scenario file:
Multimedia communication
J2ME Wireless Toolkit has long-term support for JSR 120, Wireless Messaging API (WMA) 1.1 version; new version supports WMA 2.0 (JSR 205), which extends the WMA's functionality to include multimedia communications.
In the toolkit, communication occurs in an analog environment. If you run multiple times, the application on the simulator can communicate with each other, and you can use the toolkit convenient WMA Console utility to exchange messages with the application in the same environment. Communication can follow one of three standard protocols: Short Message Service, SMS, Cell Broadcast Service, CBS, orware 2.2 version of the new protocol-Multimedia Communication Service (MMS).
You can mark the MMS message and add any file collections to the message.
Moreover, now the network monitor can display the MMS message sent or received by the simulator.
Bluetooth and Obex
J2ME Wireless Toolkit Simulator supports JSR 82, Java API for Bluetooth, including two separate APIs:
Bluetooth API provides an interface for Bluetooth Wi-Fi, including device recovery and data exchange. The Obex API allows applications to use object exchange (Object Exchange, Obex) protocols on Bluetooth or other communication channels.
The toolkit allows you to develop and test applications with Bluetooth technology even if there is no actual Bluetooth hardware. The toolkit is analog Bluetooth environments where you can run multiple simulator instances that mutually discovery and exchange data using Bluetooth APIs in this environment. Application Example BluetoothDemo shows how to transfer images from a simulator to another.
J2ME Wireless Toolkit implements OBEX transmission over analog Bluetooth and infrared connections. The analog infrared connection follows the IRDA standard defined by Infrared Data Association. The toolkit is analog infrared transmission between multiple running simulators.
You can use the Bluetooth / Obex tab in the toolkit parameters to configure the Bluetooth and Obex environments. It controls parameters such as how long to find other devices in the simulated Bluetooth environment, and maximum data packet size. See User Guide for Kit Get more details.
Local files and personal information
J2ME Wireless Toolkit supports JSR 75, which PDA Optional Packages for the J2ME Platform, which also includes two separate APIs:
The FILECONNECTION API provides access to local file systems on the device. The Personal Information Management (PIM) optional package includes APIs for manipulating a contact list, schedule, and a list of scheduled lists.
A real device may have a local file system that can be accessed by using the FILECONNECTION API. In the J2ME Wireless Toolkit Simulator, the analog file system exists as a directory on the hard disk.
Applications use FileConnection accessible files in subdirectory
You can select MIDlet> External Events from the menu of the simulator window to manage the available root directory. You will see a small utility window that adds and deletes the root directory. These operations will also generate events for the Registered Listener object.
On a real device, personal information may be stored in memory in a proprietary format. The simulator uses a directory in the hard disk to store this information, and you can use the PIM API to access. All information is stored in the
In the list directory, the list item is stored in the standard format specified by Internet Mail Consortium. Contacts are stored in VCARD format, calendar and program items are stored in Vcalendar.
Conclude
J2ME Wireless Toolkit 2.2 is more than just an excellent tool incremental update. It includes support for exciting four new specifications, while defining six new APIs. With the rapid development of the wireless Java technology, J2ME Wireless Toolkit follows the pace of development and contains all the tools you need.
About author
