- Paperback: 688 pages
- Publisher: Apress (April 21, 2011)
- Language: English
- ISBN-10: 1430230428
- ISBN-13: 978-1430230427
- Product Dimensions: 7.5 x 1.6 x 9.2 inches
- Shipping Weight: 3.2 pounds (View shipping rates and policies)
- Average Customer Review: 70 customer reviews
- Amazon Best Sellers Rank: #1,607,581 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Beginning Android Games
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
About the Author
Mario Zechner runs Badlogic Games, a game development shop focused on Android.
Read reviews that mention
Showing 1-2 of 70 reviews
There was a problem filtering reviews right now. Please try again later.
Chapter 9 The Main Activity, (the layout of SuperJumper.java)
The first part of the code until the mistake line --> Public class Settings is correct and from there the remaining code is from the previous Settings.java.. To get the correct code You HAVE to go get the files from them. Otherwise you will make it nowhere.
There are 3 more examples of this in the previous chapters, Code Duplication, and Missing code.
Phone call to the publisher is scheduled for Monday, since I cannot return this book (notes on the pages notating the freaking issues) I intend to seek a refund or reprint from them as the book is useless from this instance alone and I fear the same to happen in Future chapters but will continue to finish the book.
But when your learning this stuff typing your own code is very useful. Using pre-made files makes you loose the interactive learning that is important to put the method into people.
SO if the publisher/author responds to this . . DO NOT GIVE ME THE YOU PROVIDED THE FILE AS AN EXCUSE. Every time you make an issue like the one I point directly to above (the duplicated in the same code is minor in my opinion since when your typing it you will most likely say hey wait I just typed this and fix it) you should be issuing to all owners a re-print or high quality insert to replace the pages of YOUR screw-up.
WHEN YOU MAKE A BOOK FOR EDUCATION YOU NEED TO MAKE SURE YOU ACTUALLY CHECK THE BOOK BEFORE THE PRINT GOES OUT!
Apress Has offered me a solution to the issue per-say, and they won't be fixing this book itself, but are releasing a second edition eventually that will "claimed" these issues fixed. My advice is if you purchase the book or have the book, to call Apress if this bothers you like it did to me.
to make my book good I spent the time with my printer and label paper making personal corrections to size and putting it over the wrong txt, But that is for me as E-books for learning and reference are not my thing, (cant flip as easily)
That being said, I do have a few minor complaints. The organization of the book could be a bit better. Chapters tend to be very long. Chapter 3 could have been safely separated into 3 or 4 chapters with a little bit more time devoted to explaining the interfaces. Not the code itself, but the reasoning behind the code. Most of the explanation is adequate, but there are definitely places that could use clarification. A little more clarification needed is a frequent theme throughout the book. For instance, the author mentions that Java does not have unsigned types, but due to the power of the two's complement we can safely use signed integer types to store unsigned values. It seems like about a decade ago I took a digital logic course where the two's complement came up. I would guess that most of the readers have never heard of the two's complement and out of those that have, probably only a handful remember it well enough to explain it. If it's important enough to bring up in the text, it's important enough to provide a quick explanation of what it is and why it's important. Two or three sentences would have done the job. There are a number of examples like that throughout the book. Places where a couple of extra sentences would have clarified a topic and bumped this up from a 3 to a 4 star review.
My last complaint is the author's use of 'so-called'. We have so-called color cubes and so-called apis and so-called everything under the sun. I would recommend searching the book for 'so-called' and deleting every instance of it. It adds no value to the book. It's similar to a speaker frequently using the word basically to indicate he is about to provide a simple summation of a complex topic. It's just a pet peeve of mine, and it in no way reflects on the quality of the book.