You're reading from Learning Java by Building Android Games - Third Edition

Product type Book

Published in Mar 2021

Publisher Packt

ISBN-13 9781800565869

Pages 686 pages

Edition 3rd Edition

Languages

Java

Concepts

Mobile Game Development

Author (1):

John Horton

Table of Contents (24) Chapters

Preface

1. Chapter 1: Java, Android, and Game Development

2. Chapter 2: Java – First Contact

3. Chapter 3: Variables, Operators, and Expressions

4. Chapter 4: Structuring Code with Java Methods

5. Chapter 5: The Android Canvas Class – Drawing to the Screen

6. Chapter 6: Repeating Blocks of Code with Loops

7. Chapter 7: Making Decisions with Java If, Else, and Switch

8. Chapter 8: Object-Oriented Programming

9. Chapter 9: The Game Engine, Threads, and the Game Loop

10. Chapter 10: Coding the Bat and Ball

11. Chapter 11: Collisions, Sound Effects, and Supporting Different Versions of Android

12. Chapter 12: Handling Lots of Data with Arrays

13. Chapter 13: Bitmap Graphics and Measuring Time

14. Chapter 14: Java Collections, the Stack, the Heap, and the Garbage Collector

15. Chapter 15: Android Localization – Hola!

16. Chapter 16: Collections and Enumerations

17. Chapter 17: Manipulating Bitmaps and Coding the Snake Class

18. Chapter 18: Introduction to Design Patterns and Much More!

19. Chapter 19: Listening with the Observer Pattern, Multitouch, and Building a Particle System

20. Chapter 20: More Patterns, a Scrolling Background, and Building the Player's Ship

21. Chapter 21: Completing the Scrolling Shooter Game

22. Chapter 22: What Next?

23. Other Books You May Enjoy

Refactoring MainActivity to SubHunter

It is a good practice to use meaningful names for all the different parts of our code. We will see this as we progress through the projects. For now, I think MainActivity is a bit vague and inconclusive. We could make do with it, but let's rename it to something more meaningful. This will also allow us to see how we can use the refactoring tool of Android Studio. The reason that we use the term "refactoring" instead of just "renaming" is that when we change the names we use in our code, there is often much more than just a simple name change going on behind the scenes. For example, later, when we refactor the MainActivity filename to SubHunter, Android Studio will change the name of the file as well as some code in the AndroidManifest.xml file and the MainActivity.java (which will soon be SubHunter.java) file.

In the Project panel, right-click on the MainActivity file and select Refactor | Rename. In the pop-up window...