How manoharkonala/zomato-clone-with-python-tkinter-and-mysql works
Project type and purpose
• This is a desktop “full‐stack” application:
• Frontend: Python Tkinter GUI
• Backend: Python application logic (authentication, menu browsing, order processing)
• Persistence: MySQL database
File structure
• Top‐level directories:
• GUI → Tkinter code modules (main.py, Main_window.py, user_authentication_zomato.py)
• No separate “services” or microservices; it is a monolithic client application with a remote DB
README for additional insights
• Features: user signup/login, restaurant browsing by cuisine, menu viewing, order placement, order history
• Dependencies: mysql-connector-python, Pillow (for Images)
a. Main components
1) Presentation Layer (GUI)
• Tkinter windows and widgets
• Images module loaded via Pillow
2) Application Layer (Business Logic)
• Authentication module
• Restaurant/Menu/Order management module
3) Persistence Layer (Database)
• MySQL server with tables: users, restaurants, menus, orders, order_details
4) External/Infrastructure
• mysql-connector-python driver
• File system for Images
b. Component interactions
• GUI → Business Logic: user actions (clicks, form entries) call Python functions
• Business Logic → Database: CRUD operations via mysql-connector
• Business Logic → GUI: updates views based on query results (e.g., populate menus)
c. Architectural patterns
• Three‐tier/Layered architecture:
• Tier 1: View (Tkinter)
• Tier 2: Controller (Python modules handling UI events and business rules)
• Tier 3: Model (MySQL tables accessed via connector)
• MVC‐inspired separation (View vs. Model with controller logic in between)
d. Key technologies/frameworks
• Python 3.x, Tkinter, mysql-connector-python, MySQL, Pillow
Detail checklist
• Break business logic into sub‐components (Authentication, Restaurant service, Order service)
• Image asset loader module (Pillow) as a dependency of GUI
• Mysql-connector-python library as the interface between logic and DB