How degisew/school-management-system works
This is a Flutter school-management app with a small PHP/MySQL backend. The likely user journey is role-based access to school tasks such as registrations, attendance, timetables, and payments, but the README describes no product capabilities and the Dart sources were not sampled; those screen areas are therefore represented as broad subsystems, not a verified runtime flow. The PHP endpoints’ database dependency and the Windows host’s Flutter startup are evidenced. No inspected source establishes how the app reaches the PHP endpoints.
Main entry points: screens Role dashboards · flutter_window.cpp Flutter window · main.dart App entry · PHP PHP endpoints
Components 14
Flutter application
- App entry
lib/main.dart - App services
lib/services
School workflows
- Login and registration
lib/screens - Role dashboards
lib/screens - School operations
lib/screens - Administration
lib/screens
PHP backend
- PHP endpoints
lib/PHP - MySQL connection
lib/PHP/connection.php
Platform host
- Windows entry
windows/runner/main.cpp - Flutter window
windows/runner/flutter_window.cpp - Win32 window
windows/runner/win32_window.cpp - Plugin registry
windows/flutter/generated_plugin_registrant.h
Other components
- School user
- MySQL database
Connections 11
- School user → App entry: opens app
- App entry → Login and registration: starts workflow
- Login and registration → Role dashboards: routes by role
- Role dashboards → School operations: offers tasks
- Role dashboards → Administration: offers administration
- App services → PHP endpoints: calls endpoints
- PHP endpoints → MySQL connection: includes connection
lib/PHP/adddirector.php - MySQL connection → MySQL database: connects to
lib/PHP/connection.php - Windows entry → Flutter window: creates window
windows/runner/main.cpp - Flutter window → Win32 window: inherits and delegates
windows/runner/flutter_window.cpp - Flutter window → Plugin registry: registers plugins
windows/runner/flutter_window.cpp