- As you read, see if you can answer the self-check questions.
- Bring your questions to class!
- You do this project with your partner; do NOT do it alone. If your partner is unavailable or uncooperative, get help from your instructor.
- Both team members understand all the code the team is turning in.
- You complete the entire project.
- You use good style throughout:
- No errors or warnings should remain in the code that you turn in.
- Control-shift-F is your friend!
- You do NOT need to have any documentation in this exploratory exercise.
- In Eclipse, checkout the Inheritance project from your individual repository.
- Per the UML for the Banking example, implement a CheckingAccount that extends BankAccount.
- Here is a specification of the project:
LinearLightsOut is a one-player game (puzzle). Initially, the user is presented with an array of buttons that are randomly initialized to either Xs or Os, 50% probability each. Clicking on a button changes the symbol of the button and both its left and right neighbors.
- Buttons on the end just change their own symbol and their one neighbor’s symbol; the buttons don’t “wrap around”.
The object of the game is to reach a state where the buttons all show the same symbol, whether Xs or Os doesn’t matter.
The pictures on the right show a game at the start (with buttons set randomly), a game that has been won (with a “We have a winner!” message displayed in the title), and (just for grins) a game in progress on a Mac.
- What you should do:
We’re providing a lot less “scaffolding” for this problem than most of the previous ones.
Everything you need to solve the problem has either appeared in previous homeworks or examples,
or is in the Java API documentation for
JButton. Remember to ask for help if you get stuck.Here are the stages you should use to implement the project:
- Stage 0: Examine the main method in the LinearMain class in the linearLightsOut package
in the Inheritance project that you checked out in class (and used for the BankAccount exercise).
- This is all the code that we supply for the project — you do the rest.
- All your code must be in the linearLightsOut package of the Inheritance project that you checked out in class.
- Stage 1: Display a JFrame with the right title.
-
Stage 2: Display the right number of JButton's in the frame without worrying about event handling or the symbols on the buttons.
- In the code that we supplied (and which you must use), main asks the user for the number of buttons.
- For full credit, you final solution must work with any number of buttons that the user responds.
- You may assume that the user enters a valid integer that is at least 2.
- If you want to display the buttons on a JPanel and add the JPanel to the JFrame,
that's OK. Or, you can add the buttons directly to the JFrame. Your choice.
- But if you choose the latter approach, don't forget to set the layout of the JFrame. (A BorderLayout might be your best choice.)
- Stage 3: The game buttons have random Xs and Os on them (50% probability of each, with a new random set every time you run the game).
- Stage 4: The Quit button is displayed and works.
- Stage 5: The New Game button is displayed and works. This should reset the symbols (Xs and Os) on the game buttons to a new set of random symbols (Xs and Os).
- Stage 6: The game buttons toggle the symbols correctly as described in the above specification.
-
Stage 7: When the game is won, the player is notified in some way.
- Changing the window title would suffice. (If you do that, be sure to change it back when the player clicks New Game.)
Hints:
-
The
setText()andgetText()methods ofJButtonare your friends. -
You do not need to design an inheritance hierarchy to solve this problem;
your BallWorlds project will give you practice at that.
- You may, however, use inheritance in this project if you wish: extending JFrame, JButton, and/or JPanel, for example.
- Here's a sample UML diagram that you may find helpful
- Stage 0: Examine the main method in the LinearMain class in the linearLightsOut package
in the Inheritance project that you checked out in class (and used for the BankAccount exercise).
- You should get through Stage 5 below by the next class period (Session 18). But if you get stuck on Stage 5, just bring your questions about it to class.
- You should attempt ALL of the rest of the project by the session after that (Session 19). But if you get stuck on a stage, just bring your questions about it to class.
- The entire project is due at the beginning of Session 20.