Description

• Set the game progress on the stats screen to the original default values. For example, the total score will be set back to 0.

Description

• Update text across GUI screens with a chosen font. This will be done via the input stream

• Main Start Screen
• How To Play Screen

Description

As a user with limited mobility I want to be able to use the software without a mouse so that I can access it.

Implementation Details

Provide the user with a textbox to type their words in and store them. This would allow users with disabilities to avoid using a mouse which could cause physical strain. For example, adding a JTextField is an option which will help in displaying words or allowing the user to type words.

Display In-Game Stats for Normal Gamemode

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Closes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Test A
• Test B

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

Move it to the center and maintain the grid layout of the board

Description

• Make use of JavaFX animations across various elements.
• Add an animation to change the colour of a button or a window panel every 10 seconds using JFrame

User stories 1.1 & 1.2 should be expanded upon to allow the user to access all features using only only keyboard input.

Description

• This will be done by making the BoggleStats class implement the Serializable interface. Since the user’s stats will be stored in a BoggleStats object, the information captured by this object will be serialized into a byte file stored on the user’s computer. When they run the program again, the file will be deserialized in order to maintain the stats determined by the previous program instance.

• Connect the scenes together via a button so the user can directly see the game summary stats as well.

Description

• Implement the Template Model Design Pattern for CommandCenter to provide a default implementation that might be common for all subclasses

• Stats Screen
• Grid Selection Screen

• Implement the singleton design pattern for BoggleStats, so only one instance gets used throughout

Add JavaDOC comments describing the methods in detail

• Display Boggle Board

Description

As a user, I want to see the stats for the current round I played or for the particular game mode I’m on.

Implementation Details

Use the stats variables from BoggleStats to display the stats for the current round. Use GUI elements to display the stats on the screen and provide buttons for the user to select if they want to end the game or play another round.

Normal gamemode Scene must display the characters of a given BoggleBoard rather than using numbers as placeholders.

Populate the stats screen with attributes of an instance of BoggleStats. Ensure that only one instance of BoggleStats exists at any single time via the Singleton Design Pattern.

• Add methods/getters for the clearing of player/computer words and other stats attributes accordingly, and also refactor some of the GUI elements in the summary screens

• 6 x 6 Boggle Dice

Description

• Use JFrame objects to implement the colours and, for instance, change the background colours of each feature.

• Ensure round and game stats are being properly displayed via the DisplayRoundStats and DisplayGameStats commands
• Ensure boggleGame is correctly processing the user's decisions to play another round or end the game without error

gameWindow should be modified so that ProcessInformationCommand objects can properly communicate stored information with gameWindow. This implementation will likely involve creating an instance of BoggleGame which will process the choices made by the user, and making this instance of BoggleGame an attribute of gameWindow so that all commands made from the application directed to the invoker (CommandCenter) can relay information to BoggleGame once executed.

Description

As a user I want to clearly decide when I want the round to end.

Implementation Details

Add an end round button which takes the user to the round summary screen.

Fix the bug where pressing N does not cause End Round Button to fire on the Normal Gamemode Screen. This is because N is being taken as a letter the user is typing into the textfield.

• When you end the whole game (by clicking the button only), and u start a game, the player score starts at 1 instead of 0

Description

As a user, I want to see the accurate stats for the total number of rounds I have played. In other words, the whole game’s stats including each round.

Implementation Details

Similar to Normal Game Mode Round Summary Screen (#21), make use of the BoggleStats variables such as total_rounds and display the stats on the screen for the user using GUI elements.

The buttons are causing the wrong commands to be executed, so this needs to be looked tinto and fixed.

• Displayed real-time stats on the Normal Game Mode screen
• Implemented a method that saves the scores and rounds in a hashmap

e.g. user info must be updated before the game can be started

Carry out a final refactoring of the code before pulling production into main to ship our final product. The following refactoring guide will be a useful tool for this. This will be reviewed and delegated as a team during our final meeting.

This issue is a combination of processing the information and displaying/capturing the info via the GUI. To be discussed during meeting on 28th of November.