Documentation

Everything you need to understand, run, and extend SchedX.

System Architecture

       [Next.js Frontend]
       Port 3000 / React / TypeScript
       │
       │ HTTP POST /api/simulate (JSON)
       ▼
       [Express Backend]
       Port 3001 / Node.js
       │
       │ child_process.spawn()
       │ stdin: JSON Config
       ▼
       [C Scheduler Engine]
       High-Performance Native Binary
       │
       │ stdout: JSON Execution Trace
       ▼
       [Express Backend]
       │
       │ HTTP 200 OK (JSON)
       ▼
       [Next.js Frontend]
       Gantt Chart & Analytics Render

Why C?

OS scheduling is deeply tied to low-level systems programming. Writing the core engine in C ensures the project maintains academic rigor and mimics how the Linux scheduler actually operates, rather than just faking it in JavaScript.

Why Next.js?

While C is great for computing logic, it is terrible for drawing interactive charts. Next.js, combined with shadcn/ui and Recharts, provides a modern, accessible, and highly interactive layer to visualize the C engine's output.