[JAVA][Beginning Java 8 Games Development]

Chapter 12 ■ Setting Boundaries for Your Action Figure in 2D: Using the Node Class LocalToParent Attribute
Figure 12-11. Change declaration statement for HBox object named buttonContainer from a static modifier to private
I had originally declared these fields static because I had read on the Internet, on several of the Java coding sites,
that this is an “optimization trick,” which allows the JVM to set aside fixed areas of memory, and make the code run
more optimally. I have decided to make the objects for my game as encapsulated as possible first, here during the
development process, and then look at optimization later on, if and when it becomes necessary.
As long as we are making our InvinciBagel.java class completely encapsulated, let’s make the other variables
private as well. I tested this game after making each of the variables (after the Bagel iBagel declaration) private, and it
ran just fine. When I make the Bagel iBagel private, the game hangs on a white (background color) screen, so I left the
Bagel iBagel declaration package protected (no access control modifier keyword signifies package protected access).
Making the Remaining Variables Private: Finish Encapsulating InvinciBagel Class
My work process for making the other eight lines of variable declarations private rather than package protected was
to place the private Java access control keyword in front of the (simple or compound) variable declaration, and then
use the Run ➤ Project work process (or click the green play icon at the top of NetBeans, which is faster) to test the
code and see if all of the features, including the Button UI, splashscreens and character movement, work as they have
been, using package protected access control. If for some reason at a later point in the software development we need
www.it-ebooks.info
263