How domhnallmorr/pitwall works
Project type and purpose
• Pitwall is a desktop F1 manager simulation game written in Python.
• It follows an MVC-style architecture and uses Flet for its UI.
• Key responsibilities include: simulating seasons, races, driver/staff markets, car development, facilities, emails, and persistence via load/save.
File structure
• Top-level:
• src/ — contains all application code
• src/pw_view/ — presentation layer (Flet views & assets)
• src/pw_controller/ — application layer (controllers & page logic)
• src/pw_model/ + src/race_weekend_model — domain layer (game models, simulation engines)
• src/1998_Roster/ + load_save subfolder — data layer (initial data & persistence)
• README.md, pyproject.toml — configuration & metadata
• tests/ — automated unit and integration tests
• Patterns:
• MVC/MVVM: Views ←→ Controllers ←→ Models
• Layered separation: presentation, application, domain, data
• Persistence:
• roster.db, season.txt, and save_game.db for initial data & save games
• load_save modules under pw_model handle serialization
README for insights
• Confirms Flet-based UI, Python/Poetry toolchain, GPLv3 license.
• Features highlight core modules: simulation, email, car dev, load/save.
a. Main components
1. Presentation Layer (pw_view + Flet)
2. Application Layer (pw_controller)
3. Domain Layer
• Core Models (pw_model)
• Race Simulation Engine (race_weekend_model)
4. Data Layer
• Data sources (src/1998_Roster roster.db & track files)
• Persistence (load_save modules → save_game.db)
5. Assets (images, logos under pw_view/assets)
b. Relationships & interactions
• User interacts via Presentation Layer → events routed to Controllers
• Controllers invoke Domain Layer APIs to update game state
• Domain Layer reads/writes via Data Layer (load/save, roster)
• Controllers push updates back to Presentation for rendering
c. Architectural patterns
• MVC: clear separation of concerns
• Layered architecture: UI, application logic, domain logic, data access
• Modularization by feature: car_development, driver_negotiation, finance, etc.
d. Key technologies
• Python 3.x, Poetry for dependency management
• Flet for cross-platform UI
• SQLite (via roster.db, save_game.db) or file-based persistence
• pytest for testing