Book Image

Learning Java by Building Android Games - Second Edition

By : John Horton
Book Image

Learning Java by Building Android Games - Second Edition

By: John Horton

Overview of this book

Android is one of the most popular mobile operating systems presently. It uses the most popular programming language, Java, as the primary language for building apps of all types. However, this book is unlike other Android books in that it doesn’t assume that you already have Java proficiency. This new and expanded second edition of Learning Java by Building Android Games shows you how to start building Android games from scratch. The difficulty level will grow steadily as you explore key Java topics, such as variables, loops, methods, object oriented programming, and design patterns, including code and examples that are written for Java 9 and Android P. At each stage, you will put what you’ve learned into practice by developing a game. You will build games such as Minesweeper, Retro Pong, Bullet Hell, and Classic Snake and Scrolling Shooter games. In the later chapters, you will create a time-trial, open-world platform game. By the end of the book, you will not only have grasped Java and Android but will also have developed six cool games for the Android platform.
Table of Contents (30 chapters)
Learning Java by Building Android Games Second Edition
Contributors
Preface
Index

Errors, warnings, and bugs


The most common getting started errors are the syntax errors. They most frequently occur when we mistype a Java keyword or forget to leave a space after a keyword.

The error below occurs if you forget to leave a semicolon at the end of a line of code.

Note

There are occasions when we don't need semicolons. We will see these as we proceed.

Look at this image that shows the error when we type a word the compiler doesn't recognize.

Also, notice that Android Studio is giving us a warning that we have some unused variables. Warnings for example like Field 'horizontalTouched' is never used. You can see these warnings if you hover the mouse pointer over the little yellow lines on the right of the editor window just as we did when looking at the unused import statements. There are other warnings like this one that indicates that method boom is never called.

Warnings do not have to be fixed for the code to execute but are worth keeping an eye on as they often prompt us to avoid...