Getting started with JME - Part I / III
Are you one of those that are very interesting on developing something to mobile devices? Or, Are your boss pushing you to show THAT report on his phone ? And so, you decided to visit some sites and mailing lists about, but you found just a "letter soup" like CLDC, CDC, MIDP and others ?????
Oh yeah, IÂ´ve already done the same... and because this IÂ´m going to show you the "stones path": What you have to do to know how this platform works (configurations, profiles, life-cycle, etc). And, for not be a large post, IÂ´ll write divided in 3 parts. ;-)
First, to understand this platform lets look to the above picture:
As you can see, the bars are separated by the kind of device you wanna run your application. Because, with this you will be able to know witch APIs will be available to develop you application. And of course, itÂ´s a good idea read your device specification to know witch optional API will be available too.
My objective today is show you the path to find the best resource of documentation. In this case, the best option is to visit http://java.sun.com/javame/reference/apis.jsp .
There you can read a lot about CLDC, CDC, MIDP and others documentations and APIs, and so, you will know exactly what youÂ´ll have available to develop your application.
Yet on SunÂ´s site, you can find at http://java.sun.com/javame/downloads/index.jsp the oficial toolkit to different JME configuration and profiles.
At this point, probably, youÂ´ve already choose the bar (on the JME Platform image) where you going to run your application and so you can make the choice: Sun Java Wireless ToolKit to CLDC or CDC! ;-)
And now ?!?!?! :/
Well, now you probably have the minimum necessary to start a JME application development for the device youÂ´ve choose. On the next post I going to write about the application life-cycle and with what you must care when going to start you application development.
Also, IÂ´ll write about the IDE that we are going to use to develop our example - a JME applcation that connects on Internet by HTTP ! ;-)
Any doubt? I forgot something? Wrote something wrong?
Let me know!! Send an e-mail to email@example.com or do your comment here !! ;-)