How kirakrabu/todolist works
Project type and purpose
• This is a desktop application written in C# using Windows Forms.
• Purpose: A “Daily Planner” with a splash screen (Form2) and a planner interface (Form1).
• There is also a console-based reference implementation in C++ (ToDoListCpp), but the primary deliverable is the WinForms app (To Do List.exe).
File structure
• Top-level files:
• Form2.Designer.cs / Form2.cs – splash screen UI and logic
• Form1.Designer.cs / Form1.cs – main planner UI and event handlers
• README.md – project description & UI behavior
• To Do List.exe – compiled WinForms executable
• ToDoListCpp – legacy/reference console code
• No external database config – storage is likely file-based (e.g., XML/JSON/serialization).
README for additional insights
• Workflow: Splash → “Начать планировать” → Main planner.
• Main form features:
• Task text field
• Notes text field
• Deadline date picker
• Save, Delete, Edit, Exit buttons
• Data grid/table showing saved tasks
Elements
• Clear labels:
• “SplashForm (Form2)”
• “PlannerForm (Form1)”
• “BusinessLogic (Form1.cs event handlers)”
• “Local File Store (tasks.json/xml)”
• “Legacy: ToDoListCpp” (optional)
• UI → BusinessLogic (on button clicks)
• BusinessLogic → File Store (read/write)
• File Store → UI (on startup/load)
• Green for persistence