Short Dog said
I'm a serious J2ME developer. I bought this book because it claimed to solve the 600 phone problem. It also promised to do some fancy GUI which are otherwise completely lacking in J2ME.
However, right out of the box the first demo, the menu sample, fails utterly. Ant crashed because I didn't put an Ant jar file in the any classpath then the menu sample didn't work. I had to search some forum to find there is a bug in the latest RC4 download. Apparently no one at Enough caught or fixed it. To fix it I had to patch a css file deep inside the project. If that wasn't enough the actual menu demo looked horrible on WTK 2.5. Couldn't see the menu highlights and it scrolled incorrectly.
Then I tried the roadrunner game. But the game didn't fit on the screen properly--isn't this the 600 phone issue? Ultimately, when I tried to exit, the game (or emulator) crashed. I looked at the jar file size and it was a whopping 462 KB on just 1,433 lines of source! Unreal.
I tried the tabbing demo which looked decent and worked well enough but it was 430 KB on just 200 lines of source. This is awful.
J2ME Polish depends on Ant and preprocessing of #ifdefs which were recognized a bad idea when C introduced them 30 years ago. C++ introduced const (and Java, final) partly for this reason. Actually, in J2ME Polish (and NetBeans) they're not #ifdefs but //#ifdefs because Java never bothered, and rightly, with this silliness--and here they are back again. They make the code less readable and they're virtually impossible to debug.
Then there's this matter of integration of the IDE (I use Eclipse) and Ant. I mean, why bother with an IDE if you must still use Ant? Throw in some .css files, too, for good measure. I just don't get it.
Indeed, I'm returning the book for a refund. I had enough from Enough.
Mark Spritzler said
When you first learn J2ME, you learn about this fantasy world where all devices follow the J2ME specification to a tee. But in the real world, because of the interpretive nature of the specifications, no two devices really implement the specification exactly the same. So this requires either targeting a particular device or have many versions of you app to run on different devices.
Man what a pain. But that is where J2ME Polish comes to the rescue. J2ME Polish provides pre-compiler directives to allow you to write code such that J2ME Polish's build script can automatically create different versions for you on the fly however you want. There is a lot more to J2ME Polish than just that, but this is a book review.
So let's get to that review. Well, first Robert Virkus is J2ME Polish, well he is the architect and lead programmer for J2ME Polish. Who better to write a book about it? Consider this book the hard copy of the manual for J2ME Polish. If you are going to use J2ME Polish, then this book is a must. It is the reference book that you will need to find anything you need to know about J2ME Polish.
Now, it isn't really a read all the way through the book and you can be J2ME Polish expert. You really need to be actually using J2ME Polish at the time, to better grasp what is being explained. The book can be hard to understand, not because of the writing, but because J2ME Polish is feature rich and there is lots to learn.
I highly recommend using J2ME Polish and buying this book if you will be developing for more than one device, and also to get their cool looking GUI screens, rather than MIDP 2.0 High Level GUIs.
Milosz Weckowski said
I searched for something like that so long. The tool is definetely already state of the art to enable Developers producing professionell applications under the J2ME Plattform. This book supplement the already existing and good documentation and explains everything from higher perspective.
Very Well done !
Comments