Basic GUI Design: The Game of Craps

Background

The rules of the Game of craps are as follows:

$-$ A player rolls two dice where each die has six faces in the usual way $($values $1$ through $6).$

$-$ After the dice have come to rest the sum of the two upward faces is calculated.

$-$ The first roll$/$throw

$-$ If the sum is $7$ or $11$ on the first throw the roller$/$player wins.

$-$ If the sum is $2,3$ or $12$ the roller$/$player loses, that is the house wins.

$-$ If the sum is $\backslash (4,5,6,8,9\backslash ),$ or $10,$ that sum becomes the roller$/$player$\text{'}$s 'point'.

$-$ Continue rolling given the player's point

$-$ Now the player must roll the 'point' total before rolling a $7$ in order to win.

$-$ If they roll a $7$ before rolling the point value they got on the first roll the roller$/$player loses $($the 'house' wins$).$

Specifications

For our implementation of the game, will we will track how many wins the player has versus how many wins the house does. We will also show the value of each rolled die, the total of the roll, and the point $($as necessary$).$ When the player wins$/$loses a round, this should be reported on the window$/$frame$.$ Below the program details are screenshots of how you might model your solution $($you can change your layout a bit if you wish$)$:

Write a program using Java Swing to implement the game of Craps. Include the following items:

$-$ A menu that has $($at least$)$ the following selections $($NOTE: all selections should include some form of keyboard shortcuts$)$

$-$ Game Menu with the following sub$-$menus

$-$ Start: This MUST be chosen before the game can begin. It enables the necessary items on the window$/$frame and initializes any underlying values as necessary

$-$ Reset Session: Clears all data including win totals and restarts game

$-$ Exit: Exits the application. The user should be asked $($via a JOptionPane$)$ if they are sure they want to exit

$-$ Help Menu with the following sub$-$menus

$-$ About: Displays a JOptionPane that should include your name, what version the app is$,$ what version of Java the code was written against, and anything else important about the application

$-$ Rules: Displays a JOptionPane that describes how the game is played $-$ Rules: Displays a JOptionPane that describes how the game is played

$-$ A button to roll the dice $($include a keyboard shortcut to the button$)$

$-$ Should only be enabled when the game has been started and is in process

$-$ After a roll, the results should be displayed as appropriate in Jlabels for each die, the total, and as necessary, the point

$-$ When the game is won$/$lost$,$ a message should be displayed on the window $($perhaps using a Jlabel$)$

$-$ A button to play the game again $($include a keyboard shortcut to the button$)$

$-$ This button is disabled during gameplay and becomes enabled when the current game is over

$-$ Clicking this button should reset current roll information but NOT the win totals

$-$ JLabels for die results and win totals $($unless you do the extra credit specified below$)$

$-$ Jlabels to describe each of the other items on your window as necessary

$-$ NOTE: enable and disable buttons and menu items as necessary based on current state of game

$-$ e$.$g$.$ once the game is started the Start option on the game menu should be disabled

$-$ NOTE $2$: feel free to incorporate other components as you deem necessary. Creativity of design is welcome :$-)$

Once the above is functional, add to your solution the ability for the user to enter a starting bank account value. The user can then place a bet before starting each game. If the user wins, the bet is doubled and the bank account is updated accordingly. You are welcome to gather user input for starting bank account value and bets in any fashion you wish. You must ensure the user enters valid data $($numeric$).$ More specifically, the starting bank account must be non$-$negative. Furthermore, a bet may never exceed the current bank account. Should the user's bank account reach $0,$ the entire session is over. Below is a possible representation of your program interface. You are allowed variations on the layout provided the above functionality is in place. Use of Model View Controller

$-$ The logic for your game should be placed in files inside a package named model

$-$ The entry point for your game $($main method$)$ and items to control game execution should be placed in a package named controller

$-$ GUI components should go in a package named view

$-$ It is ok for listeners $($which constitute controller code$)$ to go in the view

$-$ Look at previous assignments for ideas on how to manage the interactions between the model, view, and controller code. Note that controller code will move data back and forth between the model and the view, modifying the data as necessary to make it usable by the model$/$view$.$ Controller code can contain your listeners.

$-$ PropertyChangeListener can be super helpful for this. It more or less follows the Observer pattern where the subject $($model$)$ can notify the observer $($view$)$ when a change occurs $($e$.$g$.$ a new value is produced from rolling the dice$)$

Final Requirements and Thoughts

$-$ Note that the user should not be able to crash your program or make it misbehave in any way. Be sure and enable and disable input items $($button