How josejesusoh/patolli-game-java-c works
Project type and purpose
• This is a desktop-based, multi-module Java implementation of the Patolli board game with a client–server architecture.
• It uses MVC on the client side, a shared domain model library, and a server engine that runs game sessions.
File structure
• Top-level modules:
• dominioPatolli – domain layer containing plain Java entities (Casilla, Dado, Jugador, Partida, etc.).
• clientePatolli – client application (NetBeans project) organized into MVC:
– src/clientePatolli – entry point (Cliente.java)
– src/control – controllers (CJugador, CPartida, CValidacion, ControlBase)
– src/modelo – client-side models (MJugador, MPartida, MValidacion, ModeloBase)
– src/presentacion – view layer, subdivided into dibujo (Canvas-style drawing classes) and vista (Swing forms and frames)
• servidorPatolli – server application (NetBeans project) organized into:
– src/controlServidor – server-side protocol handler (ProtocoloPartida)
– src/modeloServidor – server-side game state (PartidaServidor)
– src/jugador – player façade for local use (JugadorLocal)
– src/servidorPatolli – main server launcher (Servidor.java, Prueba.java)
• Build and config files: build.xml, manifest.mf, nbproject indicate separate NetBeans modules.
README for additional insights
• Confirms MVC architecture in Java, future C++ port.
• Focus is on game logic, UI, and networked play.
Elements
• Blue for UI components
• Green for control/business logic
• Yellow for domain entities
• Orange for network/protocol