How dev-du-bled/games-sae1 works
Main Components
a. Core System Components:
• Main Menu System (menu.cpp)
• Game Launcher (main.cpp)
• Utility Library (libs/utils)
• Terminal Kit Library (libs/termkit)
b. Game Modules:
• Connect4
• Gravier Carton Couteau (Rock Paper Scissors variant)
• Hangman
• Reflex
• Right Price
• Shipwar
• Tic Tac Toe (with its MVC architecture)
┌─ User Interface Layer ─────────────────────┐
• Terminal Interface (TermKit) │
• Menu System │
• Game Management Layer ────────────────────┤
• Game Launcher │
• Player Management │
• Game Modules Layer ──────────────────────┤
• ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ │
• Game1│ │Game2│ │Game3│ │Game4│ │Game5│ │
• ┘ └─────┘ └─────┘ └─────┘ └─────┘ │
• Utility Layer ───────────────────────────┤
• Utils Library │
• Common Functions │
• ┘
┌─ Model ─────┐ ┌─ Controller ─┐ ┌─ View ──────┐
• Board.hpp │◄──►│ Game.hpp │◄──►│ Terminal UI │
• Player.hpp │ │ Game Logic │ │ Display │
• ┘ └──────────────┘ └────────────┘
Integration Points
• How TermKit interfaces with each game for display
• Common utility functions used across games
• Relationship between the main launcher and individual games
Additional Elements
• Version information and system requirements
• Platform-specific considerations (Windows Terminal, iTerm2, Linux Terminal)
Implementation Notes
• The modular nature of the game system
• How new games can be added to the system
• The common interface pattern used across games
• Platform independence of the core system
Remember to:
• Clear boundaries between different system layers
• Flow of control and data between components
• Error handling and user input validation flows
This structure will provide a clear understanding of how the various components interact while maintaining the flexibility to add new games to the system.