Customer Reviews

J2ME Games With MIDP2

5 star:		(1)
4 star:		(1)
3 star:		(1)
2 star:		(1)
1 star:		(0)

 

 

I really wanted to like this book, but it turned out to be just a collection of very long code fragments with no annotation and little explanation. There is a great topic here, and there are some good ideas, but the knowledge is locked in the code.

If you are the type of person that learns by reading code then you will already have learned the APIs by looking at the sample code. The reason we buy technical books is to teach us how to use the APIs through a combination of well annotated example code, well organized reference material for the APIs, and illustrations that demonstrate best practice code flow. This book only has the code and a little explanation, the reference material, and effective illustrations are missing.

I recommend this book only if you can't find any other material on MIDP2.

Recently, on buses and trains, I've noticed people using cellphones to play games. On these dinky little screens, with a keypad instead of a keyboard, and with tinny audio. But even having all these constraints, such games have their attraction.

This should be the draw to you, to program one of these mobile devices. If the hardware runs Java, then, as Hamer explains, J2ME is used. She describes how Sun stripped out a lot of Java classes, to arrive at a minimal subset that is aware of the severe constraints you face. Limited power. Small screen. Small memory. Intermittant and low bandwidth. No mouse. No keyboard. Get the picture?

Yet even under all these limitations, Hamer shows how you can use J2ME and version 2 of MIDP to construct cool games. In many ways, it is harder than writing for a desktop or laptop or game console. But the best attitude is to regard this as a challenge of your ingenuity. Perhaps using this book, you will be the author of the next Tetris.

I'm only half joking when I say this. Because there is something about this field that I don't think Hamer explicitly points out. If you go through the book, you should come to the conclusion that you can code an entire game by yourself. Realistically, this is no longer true for games on the other platforms. These are now storyboarded and written by a team of programmers, with often a million dollar budget. With J2ME and this book, you can still do it all.

I really enjoyed this book. The author does a solid job of explaining everything you need to know to write games for MIDP devices. If you are familiar with Jonathan Knudsen's book on J2ME (probably the best book on the subject), this book expands the single games chapter into a fun and interesting book.

The book starts with a quick sample showing us how to use the Sun IDE and how to run our games on the emulator and how to download our games to a phone. The author shows a couple of example games, a maze and a jumping game, that give a good overview of the basic techniques games use on MIDP devices. She then expands those examples by showing proper use of threads and shows how to play tones and music during a game. Storing information (such as high scores or user preferences) is demonstrated. Downloading game enhancements such as new levels for a dungeon game are also demonstrated. The book is full of well-commented code samples (worth stealing) that show the techniques being discussed.

The author of this book has a nice, easy to read style of writing. Her enthusiasm for the topic comes through and makes you want to try the many sample games. If you have been spending too much time on enterprise programming then playing around with some MIDP games might be just the antidote and this book will get you started on the fun.

This the the right title for this book. It is basically a review of the code of a few simple games (like a cowboy jumping tumbleweeds, or a simple 2d maze) with very little space devoted to theory and explanations.. both of the APIs and of the internal logic and algorithms. Not that this book isn't useful.. it is but you have to wade through a lot of code, and I think the author could have done a much better job if for example she had taken the time to EXPLAIN the maze generation algorithms instead of just saying "look at the code". In short, more time and effort on the author's side, less on the reader.. and I think this book was written in very little time and with very little effort.