A simple clone of fruit ninja done in java.
- Jaxb : For xml file parsing.
- Javafx_11.0.2 : Main Library used for creating the GUI.
- Always keep a
resfolder for resources that are required during program runtime - Push any changes with meaningful comments describing the changes
- The code folder
- Self-executable jar file (JRE 1.8): The program should be executable by simply double clicking the icon or by double clicking on a bash/ batch file .
- Report should include a thorough description of your design.
- Report should include a Class Diagram showing main classes in your application.
- Report should include Sequence Diagrams showing essential or main behaviour among your classes, showing only necessary and important program flows.
- Report should include the Design Patterns you used and the intent it is used for in your application.
- Report should include snapshots of your GUI.
- Report should include a user guide that explains how to use your application.
- Add Readme.txt file with any assumptions you need to run the program, and with the detailed division of labor among the team members
- migrate game Session variables from the player class into the game Session class
- add observers to the game session class
- add effect for bomb explosions
- make splash sizes of equal width maintaining their ratio's
- fruit on splits
- game modes ie state pattern
- slow rate for fruits
- save/load window ie momento pattern
- add chain of resposibility on app startup
- mediator-observer pattern between game objects and game states
- Uploading to git
git add .&& git commit -m "YOUR CHANGES HERE"&&git push
All team members contributes equivalently to the project. From resources to the creation of the classes and the UML members had their say. For communication and file sharing team members made use of the popular Social communication app Discord, whereby joint coding sessions conducted. Git was mainly used as a form of version control and Project snapshot creation."# FruitNinja" "# FruitNinja" "# javaGame" "# javaGame"