This guide will take you through setting up a build environment for J2ME in Windows and in writing a few sample applications for the A780 phone. There are some notes at the end if you are on another platform, but we strongly recommend using a Windows environment so that you can make full use of the simulator and debug output. Setting up Eclipse, Setting up the Motorola J2ME SDK, Setting up EclipseME J2ME Plugin, Creating a simple J2ME application, Debugging J2ME applications in the simulator, This section will cover debugging and the use of the M3 simulator in conjunction with Eclipse. It is recommended that you try to run applications in the emulator before trying to run them on the phone. Installing the application on the phone. There are two files needed to install your J2ME application on the phone. One is the jar file which contains all of your compiled java code. The other is the jad file while contains metadata about your application and permissions information. Both of these are generated by Eclipse. You may now launch your application from the main menu by clicking on its icon. Note: Since you don’t have a debugging console when you are running applications on the phone, it is recommended that you catch all exceptions and call the following method with the toString() of your exception: A word about permissions, When you use various classes in J2ME, you need to make sure you set the permissions in your JAD file appropriately. You can do this by clicking on the JAD file in your main project (not the one in “deployed”) and going to the “optional” tab. Under “Midlet Permissions:” add the appropriate permissions comma separated.
Tags:motorola a780, jad file, j2me application, j2me applications, sample applications
If you see unrelated pdf files with the description or copyrighted material published, please report to us, we'll correct/delete it it as soon as possible.NONE OF THOSE MATERIALS ARE HOSTED IN THIS SERVER NOR UPLOADED BY ME IN SOMEONE'S SERVERS. Read our DISCLAIMER for more detail.
We are neither affiliated with authors and brands nor responsible for its content and change of content.
Information contained herein is provided "as is" without warranty of any kind, either expressed or implied, including any warranty of merchantability or fitness for a particular purpose. In no event shall ANYONE be held liable for any loss of profit, special, incidental, consequential, or other similar claims.