How pauljackways/goblingauntlet works
Main Components
a) Presentation Layer (GUI):
• FXML Views (represented by the multiple .fxml files)
• Controllers (all the *Controller.java classes)
• FXWindow and FXWrapper as window management components
b) Core Game Logic:
• Game Entities (Player.java, Tower.java)
• Game Items (Item.java, Buyable.java, Sellable.java)
• Game State (Round.java)
• Enums (EnumGamechangers.java, EnumItems.java, EnumResources.java)
c) Services Layer:
• CounterService
d) Models Layer:
• Counter
e) Resources:
• CSS Styles
• Images
• FXML Layouts
Component Relationships
• GUI Layer → Game Core (Controllers interact with game entities)
• GUI Layer → Services (Controllers use services)
• Services → Models (Services manipulate models)
• GUI Layer ↔ Resources (GUI uses CSS and FXML resources)
Architectural Pattern Representation
The project follows an MVC-like pattern:
• Model: Game Core + Models
• View: FXML files
• Controller: Controller classes in the GUI package
Additional Elements
A section showing:
• Build System (Gradle)
• Test Components (unit tests package)
Important Notes
• Clear separation between the JavaFX/FXML-based UI and the game logic
• Controller pattern used for different screens
• Resource management for FXML, CSS, and images
• Relationship between game entities (Player, Tower, Items)
• Test coverage indication
This will provide a comprehensive view of the application's architecture while maintaining clarity about the game's structure and component interactions.