How obsercorma/managerscreen works
Project type and purpose
• Project name: ManagerScreen
• Purpose: A Python‐based “dashboard” application intended to display information on a small hardware screen (likely a ST7920 graphic LCD) about tasks, repositories (“dépôts”), code snippets, etc.
• Status: Development paused (INFO: projet mis en pause).
File structure
Top‑level scripts and directories:
• main.py – entry point, orchestrates page navigation and update loop
• *.py (depotPage, gitPage, homePage, snippetsPage, encoder, st7920, testssh, depotPage)
– individual modules implementing display pages, hardware drivers, and utility functions
• snippets.json – local data source for code snippets
• snippets/ – directory with snippet update/restart scripts
• service.sh – installation or service startup script
• start_process.txt – possibly a log or PID placeholder
• VERSION, README.md, .gitignore
Patterns:
• Modular “Page” classes for each screen
• Hardware abstraction layer (st7920.py for LCD, encoder.py for input)
• Main controller loop (main.py) ties modules together
• External integration: SSH-based Git info (testssh.py, gitPage.py), local JSON data
README for additional insights
• Confirms project role as an information dashboard for tasks and repos
Detailed but not over‑engineered
– Hardware Layer
– Abstraction Layer (st7920.py, encoder.py)
– Application Layer (main.py, Page modules)
– Integration Layer (testssh.py, snippets.json)
– Deployment Layer (service.sh)
– Captures all modules in the file tree
– Shows data/control flow relationships
– Is annotated with technology details (e.g., “SSH → Git host”, “GPIO → LCD”)