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

Coding the inanimate and decorative components


In the previous chapter we coded all the interfaces for our component classes. We coded GraphicsComponent, UpdateComponent and InputComponent. Now we will code the three simplest component classes that will be enough to complete quite a few of our specifications.

Let's start with the DecorativeBlockUpdateComponent.

DecorativeBlockUpdateComponent

The update-related components all implement just one method, update. Add a new class called DecorativeBlockUpdateComponent, implement UpdateComponent and add the empty update method as shown next.

class DecorativeBlockUpdateComponent implements UpdateComponent {
    @Override
    public void update(long fps, 
         Transform t, 
         Transform playerTransform) {
        // Do nothing
        // Not even set a collider
    }
}

Yes, the update method is meant to be empty as the decorative objects don't move or collide.

InanmiateBlockGraphicsComponent

Add a new class called InanimateBlockGraphicsComponent...