How wes1101/exceptionfromcatan works
Project Type & Purpose
• This is a desktop full-stack application (pure Java) with a JavaFX-based GUI and a turn-based game engine (Settlers of Catan mechanics).
• Tech stack: Java 21, JavaFX (FXML), Maven for build, no external database (in-memory or file-based persistence may be added later).
Core Components
a. Presentation Layer (JavaFX UI)
• FXML views (src/main/resources/de/dhbw/app/hello-view.fxml)
• Scene graph, CSS (if any), resource files
b. Application Layer
• HelloApplication.java (entry point: Application.launch)
• HelloController.java (FXML controller binding UI events to logic)
c. Domain (Game) Layer
• GameManager, Board, Player, Resource, DevelopmentCard, TurnController, TradingService, VictoryConditionChecker (to be created under de.dhbw.app or subpackages)
d. Build & DevOps
• Maven (pom.xml, mvnw, .mvn)
• CI workflow (.github/workflows/maven.yml)
e. Documentation
• docs/FirstSetup, docs/ProjectStructure, CONTRIBUTING.md
Relationships & Data Flow
• The user interacts with the JavaFX UI (FXML view).
• UI events propagate to Controller methods (HelloController).
• Controllers invoke services in the Domain Layer (GameManager, TurnController, etc.).
• Domain Layer updates the Model (Board state, Player resources) and notifies the UI via JavaFX property bindings or observer callbacks.
• Maven handles compilation, test execution, packaging. CI workflow executes Maven goals on push/PR.
Architectural Patterns & Principles
• MVC (Model–View–Controller):
· View = FXML + JavaFX scene graph
· Controller = HelloController + any future controllers per view
· Model = domain classes (game state)
• Observer / Data Binding: JavaFX ObservableValue, Property for live UI updates.
• Single Responsibility: separate packages for UI, controllers, domain logic.
• Build isolation: externalize build config (pom.xml) from code.
Detailed Steps for the Principal Software Engineer
2. Under Presentation: place “hello-view.fxml” (UI), annotate with “JavaFX Scene”.