How langaracpsc/langaracourseplanner works
Main Components
a) Frontend Layer:
• Static Content
• HTML pages (templates directory)
• JavaScript modules (static/js directory)
• CSS styles (static/styles.css)
• Third-party libraries (static/libraries)
• Client-side Features
• Calendar functionality (Calendar.js)
• Course management (Course.js)
• Client-side database (Database.js)
• Save functionality (SaveManager.js)
b) Backend Layer:
• Flask Web Server (main.py)
• Route handlers for:
• Dynamic course pages
• Static content serving
c) Data Layer:
• SQL.js (client-side database)
• Course data storage
[Client Browser]
• ↕
[Frontend Layer]
• ↕
[Backend Layer]
Component Relationships
• HTTP requests between client and server
• Data flow between frontend JavaScript modules
• Database interactions
• Static asset serving paths
Detailed Component Breakdown
Frontend:
[Static Assets] → [HTML Templates]
• ↓
[JavaScript Modules]
• Calendar.js
• Course.js
• Database.js
• SaveManager.js
• ↓
[Third-party Libraries]
• FullCalendar
• Fuse.js
• SQL.js
Backend:
[Flask Server]
• Course routes
• Static file serving
Implementation Details
• How the client-side database interacts with the UI
• Course planning workflow
• Demonstrate how the calendar integration works
• Static vs. dynamic content handling