[JAVA][Beginning Java 8 Games Development]

Chapter 7 ■ The Foundation of Game Play Loop: The JavaFX Pulse System and the Game Processing Architecture
As you can see, it only takes a fraction of a millisecond to initialize each of the event queues, including the pulse
event, and all four ActionEvent EventHandler event processing queues. This is in keeping with our maximum game
optimization approach, using static Scene Graph nodes and not doing anything inside the GamePlayLoop that will
use up any more system resources (memory and processing cycles) than are absolutely necessary to accomplish the
various tasks that you will be building up as you create your action-filled arcade game.
Now that you have created and started your GamePlayLoop object, let’s take a look at the Threads Profiler!
Again, scroll down in the Profiler tab, shown at the top left of Figure 7-17, and find the Threads icon, which is
displayed at the top- left of Figure 7-18. NetBeans will ask you if you want to start the threads analysis tool; once you
agree, it will open the Threads tab. As Figure 7-18 illlustrates, the pulse engine is running, and several pulse events are
shown for Thread-6. Interestingly, once JavaFX ascertains that the .handle() method is empty, the pulse event system
does not continue to process this empty .handle() method and use unnecessary pulse events, indicating that the
JavaFX pulse event system has some modicum of intelligence.
Figure 7-18. Click the Threads icon, seen at the left side of the screen, and open a Threads tab; AnimationTimer pulses
can be observed on Thread-6
InvinciBagel Diagram: Package, Classes, and Objects
Next, let’s take a look at your current package, class, and object hierarchy, in the form of a diagram (see Figure 7-19),
to see where you are in terms of creating your game engine. At the right of the diagram is the InvinciBagel class,
which holds the Scene Graph, and Stage, Scene, and StackPane objects, which hold and display your splash screen UI
design. At the left of the diagram is the GamePlayLoop class, which will contain the game processing logic calls and
which gets declared and instantiated as a gamePlayLoop object in the InvinciBagel class but is not part of the Scene
Graph hierarchy. Soon, you will start building the other functional areas displayed in the diagram so that you can
control your sprites, detect collisions between the sprites, and simulate real-world forces of physics to make the game
more realistic. You will see additions to this diagram as you progress through the book and create your Java 8 game.
www.it-ebooks.info
159