Chapter 5 is the start of 3D graphics and this is generally where games start to get difficult. It makes use of OpenGL in Processing, which is a fun way to learn 3D graphics and even to do some simple things, but for games you need to know about game engines like Unity, or at the very least modeling software, that will get you a realistic 3D model in no time at all - I lied about no time at all.

Chapter 6 takes us into the interesting world of collisions. Good collision detection is important and this is a nice, if somewhat mathematical, explanation of how to go about it and how to think of it. I'm not sure how many games programmers know this much about collision detection, however.

Chapter 7 changes to considering control and here we have a state machine controlling a car. Again, it's all a bit too academic, even if I am a fan of state machines. Chapter 8 is an example of a very simple 3D game with minimal animation. Chapter 9 is about HTML5 games, but as it uses Processing.js it is still really Processing. I'm not sure this is a way I'd consider to create HTML game, but if you disagree the chapter tells you how to do it. Chapter 10 is on animation, which I think is a little late in a book on games, but you should find it interesting in a theoretical sort  of way. Finally, Chapter 11 is on Android and Processing - again not the way I'd do the job.

The final verdict has to be that the book is good, but only for a very narrow group of readers. If you want to learn game design in an academic context using Processing you have found a book that does just this. It seems to me like a book about games that avoids having to learn a suitable language like C++ or a suitable game engine. If you actually want to create a game or move into the professional games world I doubt this has much to offer you. 

To keep up with our coverage of books for programmers, follow @bookwatchiprog on Twitter or subscribe to I Programmer's Books RSS feed for each day's new addition to Book Watch and for new reviews.