CompSci 308 Spring 2024 |
Advanced Software Design and Implementation |
This exercise is intended for you to practice the basic GIT workflow commands (add
, commit
, and push
), get used to OpenJFX, and create a Java class.
There will not be an official submission for this exercise, instead show your progress to the Teaching Team during lab to get feedback.
Complete as many of the following tasks using your forked version of the lab_bounce project (they will all help prepare you for the Breakout project):
Bouncer
class (or whatever name you prefer), with a constructor, as well as appropriate instance variables and methods (basically any code that refers to those instance variables); Example
class that refers to those instance variables with calls to the new class's methods Bouncer
's constructor as needed or use randomnessFor each task, you may make any changes to the code you think are warranted (functional, organizational, or creating new classes). After you think you have completed each task, make a GIT add
and commit
with an appropriate comment, so there should be at least 6 commits in your project history. After every two commits, push
your changes up to Gitlab so your online repository reflects the work you have done today.
OpenJFX is a framework for creating Graphical User Interfaces (GUIs) that can run across a wide variety of platforms. As a modern framework, it replaces Java's (very old) Swing GUI framework and uses standard technologies that make it well-suited for creating visually-intensive applications, such as games, simulations, and data visualizations. While it contains many components for organizing and interacting with complex GUIs, for this lab and the first project, you only need to focus on the concepts in this example code: drawing, animating, and interacting with shapes and images (you will learn more with each successive project). Learning OpenJFX will help you learn any other modern GUI framework, for the web, mobile, or on the desktop.
Version control is a way to manage the many changes that occur to your files over time, but that simple idea changes everything! It allows you to revisit previous versions of your code, work with different versions at the same time, and work in teams and track who made which changes. At its best, version control is like a journal that you use to track major, and minor, events in your project. At its most practical, it is like a backup system that prevents you from losing significant work if something happens to your machine. At its worst, it is simply a submit system where you only track your work when told to. Knowing how to use a source control system will be an invaluable tool for you going forward, perhaps personally or even potentially for changes in laws, but especially in a team setting.
Using source control well is not difficult, but it does take some practice and a little bit of command-line savvy (we do not suggest using visual GIT tools, even the one built into IntelliJ, until you are confident in your version control skills).