How nickyyayy/wheresmybus works
WheresMyBus is a hardware-independent campus bus tracker: conductors report stop arrivals, the system validates and applies route progress, and students and supervisors view bus status and statistics. At startup, the C++ application loads routes and buses from MySQL, creates dashboard pages, then serves a web bridge or offers a console mode. The graph preserves the documented student, conductor, and supervisor interfaces. Some implementation links are omitted because the relevant source was not excerpted; dashed edges indicate documented or unverified relationships.
Main entry points: BusStatusEngine.cpp Status engine · main.cpp Application startup · DataLoader.cpp Domain data loader · HtmlGenerator.cpp Dashboard generator
Components 20
Startup and data
- Application startup
backend/main.cpp - MySQL access
backend/Database.cpp - Domain data loader
backend/DataLoader.cpp
Route model
- Route registry
backend/RouteRegistry.cpp - Route sequence
backend/Route.cpp - Route stop node
backend/RouteStopNode.cpp - Stop model
backend/Stop.cpp - Route validation
backend/RouteValidation.cpp
Bus operations
- Bus registry
backend/BusRegistry.cpp - Bus state
backend/Bus.cpp - Status engine
backend/BusStatusEngine.cpp - Update records
backend/Update.cpp - Pending updates
backend/Queue.h - Update history
backend/Stack.h
User interfaces
- Dashboard generator
backend/HtmlGenerator.cpp - Web bridge
backend/WebBridge.cpp - Console interface
backend/ConsoleMenu.cpp
Other components
- Student
- Conductor
- Supervisor
Connections 23
- Application startup → MySQL access: connects to
backend/main.cpp - Application startup → Domain data loader: loads data
backend/main.cpp - Application startup → Status engine: initializes
backend/main.cpp - Application startup → Dashboard generator: generates pages
backend/main.cpp - Application startup → Web bridge: starts web mode
backend/main.cpp - Application startup → Console interface: starts CLI mode
backend/main.cpp - Domain data loader → MySQL access: reads MySQL
- Domain data loader → Route registry: loads routes
- Domain data loader → Bus registry: loads buses
- Route registry → Route sequence: owns routes
- Route sequence → Route stop node: links stops
- Route stop node → Stop model: models stop
- Bus registry → Bus state: owns buses
- Status engine → Route registry: looks up routes
backend/BusStatusEngine.cpp - Status engine → Bus registry: looks up buses
backend/BusStatusEngine.cpp - Status engine → Route validation: validates positions
backend/BusStatusEngine.cpp - Status engine → Update records: applies updates
backend/BusStatusEngine.cpp - Status engine → Pending updates: queues updates
backend/BusStatusEngine.cpp - Status engine → Update history: records history
backend/BusStatusEngine.cpp - Dashboard generator → Status engine: reads bus state
- Student → Dashboard generator: views status
README.md - Conductor → Status engine: reports progress
README.md - Supervisor → Dashboard generator: views statistics
README.md