In Parts 1 and 2 of this series, we covered the basic features of the various
MIDP APIs. We looked at creating and packaging a MIDlet, creating a user
interface, and some basic graphics operations. We also discovered how to
store data with the record management system and how to communicate over the
network.
This time around, we're going to talk about MIDP in the enterprise sense
(which has nothing to do with "Star Trek"), and put together a basic example
that shows how a MIDlet fits into the big picture.
As mentioned before, and it bears repeating, a J2ME developer will
undoubtedly not be spending all of his or her time developing on the client
side. J2ME applications, particularly MIDlets, will involve a degree of
interaction with the server - and unless you're working on an exceptionally
large system with a very big team, it seems likely you'll be the developer ... (more)
Convergence. A word loved by PR companies and feared by nontechnical
consumers. If you believe industry pundits, we'll all be carrying combination
mobile phone-PDA-TV-toasters in the next few years. You'll be able to make a
phone call, write a memo, watch the morning news, and cook your breakfast all
at the same time while on your way to work. How close reality comes to the
dream (or nightmare, depending upon your point of view) is anyone's guess,
but the first devices that might fit a definition of "convergence" are
emerging on the market. Nokia's 9210 Communicator is one such c... (more)
I was reading a forum discussion recently that argued that J2ME was a mess.
The general consensus (admittedly there weren't that many messages) seemed to
be that this conclusion was correct. My automatic response was "What a
complete load of bollocks" (which I think means I've been living in England
far too long). However, upon reflection, I still don't entirely agree, but I
don't disagree either. I am officially in-betwixt camps. Neutral. Unbiased
(yeah, right).
If you mistakenly view J2ME as the sum of all Java technologies for embedded
and mobile devices, then yes, it can be ... (more)
Source Control. The bane of software developers; if only because you have to
interrupt your thought processes in order to make sure you've safely backed
up those preceding thought processes. That fact doesn't change whether you're
a J2EE, J2SE, or J2ME developer... or working in any other language, for that
matter.
It usually only takes once - losing a day's work because of a lack of proper
source control - for something to be implemented; be it a periodically run
batch file to copy files to another location, or a fully fledged application
to handle the process for you.
Personal... (more)
I recently noticed that Qualcomm has licensed the ARM1136J-S microprocessor
core. The interesting thing to note about this announcement is one of the
letters in that microprocessor version: the "J". ARM's 1136J-S is a
Jazelle-enabled chip, meaning it's optimized for the Java instruction set;
Qualcomm has effectively licensed a processor that will run Java applications
more efficiently.
This is not as strange as it sounds: BREW already seems to support Java
applications. However, what is not clear is how much they will charge for
certifying those applications, bearing in mind the... (more)
As well as being a contributing editor for Java Developers Journal, Jason R Briggs is a Java programmer and Development Manager for a wireless technology company, based in Auckland, New Zealand.
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
Ken Guiberson
