How julian-florez/oliso works
Project Type and Purpose
• The README reveals that Oliso is a modern variation of Tic Tac Toe with enhanced gameplay mechanics, developed as part of a university project.
• Key features include unique gameplay mechanics, cross-platform compatibility (Java-based), and an intuitive UI, with different win conditions (Same Size, Ascending Order, Stacked Win).
File Structure
• The top-level structure includes configuration and project files (.gitignore, .iml, META-INF) along with the README.
• All source code lives under the “src” directory which is divided into distinct subdirectories for:
• assets – containing multimedia elements (audio files, font files, and graphical bases for markers).
• controller – holding the game logic controllers such as GameController.java and SoundManager.java.
• model – featuring the business logic and game data (e.g., Board, GameModel, Player, Pieces, Turn, Square, etc.) along with exception handling (InvalidMoveException.java).
• view – covering the graphical user interface (GUI) classes including the main game window (GameWindow.java), graphical management (GraphicalManager.java), and custom UI elements (RoundJTextField.java).
a. Main Components to Include:
• Frontend/UI Layer: Represent the view (GameWindow, GraphicalManager, and custom UI widgets like RoundJTextField) which renders the game interface.
• Application Logic: Capture the controller(s) like GameController and SoundManager that manage user input, game flow, and sound effects.
• Data/Model Layer: Include core game logic components (GameModel, Board, Piece, Player, Turn, etc.) and error handling (InvalidMoveException).
• Assets: Show resource management (audio clips, fonts, and visual assets in assets folder) that support UI and gameplay.
• External/Configuration Components: Note build configurations (META-INF, .gitignore), which are environment-related supporting files.
b. Relationships and Interactions:
• The View (UI) sends user inputs to the Controller (GameController) and receives updates for rendering.
• The Controller manipulates the Model (GameModel and related classes) to update game state based on user actions.
• The Model computes game logic (valid moves, win/tie conditions, board state) and informs the Controller of any state changes.
• The Controller also interacts with the SoundManager to play audio cues, pulling media from the assets folder.
c. Architectural Patterns & Design Principles:
• The project is structured in an MVC-like pattern:
• Model: Represents the domain/business logic.
• View: Handles all UI rendering.
• Controller: Manages game flow and orchestrates actions between the model and view.
• Points such as dependency management (controller accessing both model and assets) and custom exception handling used for invalid moves.
d. Relevant Technologies, Frameworks, or Libraries:
• Core language: Java (JDK 21 or later).
• No external libraries are explicitly mentioned but the project’s structure implies standard Java GUI components.
• Assets include audio files (WAV format) and a custom font (SaedaBold.otf).