This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: Build Strategy-J2ME
Feed Title: ShareMe Technologies-The Mobile Future
Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology. Old Archive .
As I stated before I had to change my build strategy due to the fact that
microedition.platform string is often null in a mobile device. Be aware!
Most books in J2ME will tell you can rely on this string to automate
choices of wrappers for sounds and shakes which is not the case!
Thus, its back to my orginal build strategy of having the core MIDP1.0
code in a build for each vendor handset series with the calls to closed
apis differentiating the handset builds. I have choosen rather than use
one line preprocessing via Antenna to just code the closed api calls
separately per handset build.
Because I am only using closed api
calls that translate fully 100% to MIDP2.0 calls, my different handset
versions are fully MIDP2.0 compliant which will give me a slight boost
inthe MIDP2.0 push this fall.
Previous Topic
