Lab Coding Exercise: Learning OpenJFX and Making Classes

This exercise is intended for you to practice the basic GIT workflow commands (add, commit, and push), get used to OpenJFX, create a Java class, and begin to think about how to organize code within a project.

Submission

There will not be an official submission for this exercise, instead show your progress to a UTA during lab when you think you are finished to get feedback.

Specifications

In pairs, complete as many of the following tasks using your forked version of the example_animation project (they will all help prepare you for the Breakout project):

• Make the grower rectangle move horizontally to the right at whatever speed you want forever (i.e., don't worry for this step about it going past the edge of the window).
• Make the grower rectangle "wrap around" the window: when its getX() value reaches the edge of the window (the Scene's getWidth() value), change its X-coordinate to 0 so it appears at the other edge.
• Make a second grower rectangle the same distance above the mover image as the first is below, that moves to the left at whatever speed you want, and also wraps around the window.
• Make a Grower class (or whatever name you prefer since it is much more than just a "grower" now) with a constructor and appropriate methods; then create two instances of that class as instance variables and replace the code written in the ExampleAnimation class with calls to those methods.

• Make the mover image reset to its initial position instead of changing color when it collides with any grower rectangle.
• Detect when the mover has "won" by reaching the top of the screen (getY() of 0), then pause() the game's Timeline (to do this, you will need to make it an instance variable) and change the mover's color.
• Make a collection of growers positioned "evenly" along the center of the window, i.e., for a scene with a height of 400 pixels, 8 of them should be 50 pixels apart that move at random speeds and randomly left or right across the window.
• When the game is won, remove all the shapes and display a congratulatory message centered in the now empty scene (use the OpenJFX Text class to display the message). Update your test to verify the message is correctly created instead of the color being changed.

For each task, you may make any changes to the code you think are warranted. After you think you have completed each task, make a GIT add and commit with an appropriate comment, so there should be at least 8 commits in your project history. After every two commits, push your changes up to Gitlab so your online example_animation repository reflects the work you have done today.

Pair Programming

Labs in this course expect you to work either in pairs or with your project team.

Professionally, this practice is called Pair Programming: working closely with another programmer, sharing a "single computer" that we will simulate using a shared computer, shared repository or use IntelliJ's new Code With Me feature. To ensure both people do some coding, you will switch which person actually writes the code every 10-15 minutes (in industry this switch happens only 1-3 times per day). The person who is not actively coding can be advising, suggesting better names, looking up documentation, or searching the Internet for solutions to small problems you are likely to face, but not multi-tasking (i.e., doing their own work or socializing).