[JAVA][Beginning Java 8 Games Development]

Chapter 7 ■ The Foundation of Game Play Loop: The JavaFX Pulse System and the Game Processing Architecture
Figure 7-22. Run the Threads Profiler
Given the empty .handle() method processing from the GamePlayLoop object in Thread-6 (see Figure 7-18), you
can assume that the pulse events in Thread-6 are from the GamePlayLoop AnimationTimer subclass. This means that
the pulse events showing in the JavaFX Application Thread are showing where the .handle() method is accessing a
buttonContainer HBox object contained in a stackPane Scene Graph root in the InvinciBagel class.
Now, you have a low-overhead, extremely fast game processing loop in place, and you can start to create your
other (sprite, collision, physics, scoring, logic, and so on) game engines! One down, and a whole bunch to go!
Summary
In this seventh chapter, you wrote the first of the many game engines that you will be designing and coding over the
course of this book, the GamePlayLoop game play timing class and object, which allow you to tap into the powerful
JavaFX pulse event processing system.
First, you examined the different classes in the javafx.animation package and the different ways to use the
Animation, Transition, Timeline, and AnimationTimer classes to harness the JavaFX pulse event processing system.
After that, you learned how to create a new Java class in NetBeans and then extended the AnimationTimer
superclass to create the GamePlayLoop subclass, which will process your game play logic at 60FPS. You saw how
to use NetBeans to help you write the majority of the code for this new subclass, including the package and class
statement, the import statement, and the bootstrap .handle() method.
www.it-ebooks.info
163