How ava0509/cinema-reservation-system works
This is a Tkinter cinema reservation application backed by MySQL. The customer workflow is account registration or login, movie/show selection, seat selection, booking, and later booking search or cancellation. The graph separates customer-facing stages, seat selection, and persistence; the admin page is a separate, partial capability. Source excerpts do not show the full booking/cancellation implementation, and the SQL schema and seed data were not sampled, so those details are represented only at the documented level.
Main entry points: customer.py Customer app · database.py MySQL connection · Seat_selection.py Seat picker · database_structure.sql Cinema schema
Components 12
Customer experience
- Customer app
customer.py - Registration and login
customer.py - Movies and showtimes
customer.py - Booking and confirmation
customer.py - Booking search and cancellation
customer.py
Seat selection
- Seat picker
Seat_selection.py
Database access
- MySQL connection
database.py - Cinema schema
database_structure.sql - Seat initializer
Seats insertion (one-time execution).py
Admin access
- Admin page
admin.py
Other components
- Customer
- MySQL
Connections 12
- Customer → Customer app: uses
README.md - Customer app → Registration and login: offers
README.md - Customer app → Movies and showtimes: lists
customer.py - Customer app → Booking and confirmation: books
README.md - Customer app → Booking search and cancellation: manages
README.md - Customer app → Seat picker: opens
customer.py - Seat picker → MySQL connection: reads availability
Seat_selection.py - Customer app → MySQL connection: queries and updates
customer.py - MySQL connection → MySQL: connects
database.py - Cinema schema → MySQL: defines schema
- Seat initializer → Cinema schema: seeds seats
- Admin page → MySQL connection: uses
admin.py