Skip to main content

Getting started with JME - Part II / III

Posted by netomarin on May 15, 2007 at 11:56 AM PDT

Hi all !!

Let´s talk today about witch IDE use to JME development and after, about MIDlet (and MIDlet life-cycle) and User Interface.

Part II

IDE

Until few days ago I used to develop my applications with Eclipse, mainly by your excellent code editor and great re-factor stuff thats made faster the code re usability. But, at last Sun Tech Days I was very surprised with the examples using NetBeans 5.5 and since that I´m using NetBeans in some personal projects.
What I can say is, if you are getting start with JME development, maybe NetBeans could be the better choice because it´s allow you to create an entire application without enter a single code line, and also allow you to go directly to the source and make the code like you want!! :-)

But, to start using NetBeans 5.5 to mobile development you´ll need to install also the "Mobility Pack". The responsible to give to NetBeans the "power" of Mobile Development! ;-) Both can be found at:

MIDlet

Well, after this all "bla bla bla" let´s go to the "entrance door" of you JME applcation. :-)
It´s through the MIDlet that your JME application is started and over it your application will make important actions and because it will have at least one class that extends from MIDlet. For example, is from the MIDlet that you´ll be able to get the Display instance for your application.

The life-cycle of a MIDlet is something like the picture:

Taking a look to the picture, we can feel that we´ll hat to develop at minimum 3 methods: startApp, pauseApp and destroyApp. By the own name of the methods, you can suppose the method´s purpose: start, pause and the end of the application, respectably.
An important observation to do is about the startApp method. How we can observe at the picture, this method is called ever when the application goes from paused to active status, and because this you should not create new objects or program this method like it´s called just once per execution. You should program it like a "re-start" method, let the objects creations and attribution to the MIDlet constructor.


User Interface

Now, you already know from where start you JME development, so it´s time to make the user interface and handle the commands that the user will use. On this point the better thing to do is visit the article: MIDP GUI Programming: Programming the Phone Interface thats describes very well the UI development to mobile phones. ;-)

Scenes from next chapter !! :D

On the next post I´ll talk a little about the GCF (Generic Connection Framework) thats allow you to connect your mobile application to the Internet or send a SMS message. Also, I´ll write something about how to distribute and deploy your JME application. It´s just wait!!! ;-)

Cya
[]s
Neto Marin

Related Topics >>