Purposes of this assignment:

• To get you started with Swing GUI programming

General idea of the assignment:

In Assignment 5 you created a text-only version of the Battleship game. In that assignment, the Ocean class did all the computational work; the Battleship class managed input and output.

In this assignment you will start with an already written Ocean class--either yours or your new partners, whichever you prefer, but not the one I posted--and replace the Battleship class with one that uses GUIs. You can use my posted OceanTest class, or one of your own. You will need two GUIs, one to create a new game, and one to play the game.

The "ocean" will be displayed as a 10 by 10 grid in a JPanel, and will look somewhat like the following.

Details:

As before, your Battleship class will be in charge of input/output. This time, however, the input/output will be graphical.

We will assume two players, the "creator" and the "destroyer." The creator sets up a game by placing all the ships; the destroyer tries to sink them.

Creating a new game

When the program starts, the creator should see an empty ocean. The creator can place ships wherever he/she wants, and can also remove them.

• The creator should not have to type in row and column numbers. Instead, a particular location should be selected by clicking on it with the mouse. (Hint: Add a MouseListener or MouseAdapter to the JFrame. Eclipse can help with the details, or you can read the API.)
  
  
• There should be a Random button, to place all ships randomly. If this button is clicked, this will create an entirely new arrangement; any previous ship placements are discarded. However, the creator may then modify this random placement by removing and replacing ships.
  
  
• There should be a Play button. When the creator is satisified with the ship placement, clicking this button will cause the creator's GUI to be closed, and the player's GUI (with all ships hidden) to open. (Do not automatically move on to game play when all ships are placed; the creator may still want to move them around.)
  
  
• The program should enforce legal placement of the ships. No ships may be adjacent to each other, and all ships must be placed, before the game can be played. You can do checking as you go along, or wait until the Play button is clicked, or some of each.

Most of the details of the interface are left up to you. Make the GUI as obvious and intuitive as you can--we will test the program by using it, and you will lose points if it's difficult to figure out what to do.

Playing the game

When the creator is done, the player is presented with an ocean that looks empty, but contains hidden ships.

The player should be able to "shoot at" locations in the ocean by clicking on individual squares with the mouse. (Hint: Add a MouseListener or MouseAdapter to the JFrame. Eclipse can help with the details, or you can read the API. You may need to remove a previous MouseListener.)

Keep the player informed about what is going on.

• Change the appearance of the ocean (as before, the player should see three kinds of squares--apparently empty squares, known (because shot at) empty squares, and squares containing a ship of some kind.
  
  
• Make some kind of highly visible change to the ocean when the game has been won.
  
  
• Display messages to the user after each shot--you can use JTextFields, JTextAreas, and/or JLabels.
  
  
• Have a Play Again button that can be clicked to start a new game. If this is clicked before the current game has been won, use a dialog box to ask the user to confirm (or cancel) the request.
  
  
• Provide some way for the player to start a new, randomly generated game, without having to go back to the creator's interface.

Most of the details of the interface are left up to you.

Additional requirements:

• Every method, except test methods, should have javadoc comments. Use Eclipse's Source -> Generate Element Comment to get the correct form.
  
  
• The program should be properly formatted. Use Eclipse's Source -> Format to get it right.
  
  
• Every method should be short enough to see all at once on the screen.
  
  
• If you write additional methods that do computation (as opposed to those dealing with the GUI), write JUnit tests for those computational methods.

Due date:

Thursday, November 8, before midnight. Turn in your program electronically, using Blackboard. (See my Instructions for Using Zip Files and Blackboard). Only assignments submitted via Blackboard will be accepted--do not send your program by email. The usual late penalty of 5 points per day (out of 100 points) will apply.