How keypang/swe-yutgame works
Project type and purpose
• This is a standalone Java desktop application that implements the traditional Yut board game.
• It follows the Model-View-Controller (MVC) pattern and uses Swing for its UI, Maven (pom.xml) for build/dependencies, and JUnit for tests.
File structure
• Top-level files:
• pom.xml → Maven build, dependency management, entry point.
• README.md, LICENSE, .gitignore → project metadata.
• src/Main.java → application entry point.
• src/controller → controllers for screens: StartScreenController, GameScreenController.
• src/view → Swing-based views and configuration/play screens, plus an images folder.
• src/model → core domain classes (Board, Cell, Piece, Player, Yut, etc.) and GameManager (game logic).
• test/ → unit tests organized by package mirroring src.
README for additional insights
• README only gives the project name. We infer from code organization: Swing-MVC desktop Yut game, no external services.
Key points to capture
• Clear separation of MVC layers.
• The flow of control and data throughout the game lifecycle (configuration → play → result).
• The use of PositionDTO and YutResult as data transfer between Model and Controller.
• The absence of external systems or persistent storage—focus on in-memory game logic.