How sammarxz/pomerode works
Main Components
• UI Layer
• GTK4/libadwaita front-end built from data/ui/*.ui and data/css/style.css
• Window, Preferences and Help overlays defined in .ui files
• Application Core
• Vala source in src/
• Timer engine, session management, smart break logic, configuration loader
• Configuration & Resources
• GSettings schemas (data/com.github.sammarxz.pomerode.gschema.xml) for storing preferences
• System Integration
• System notifications via libnotify or GTK API
• Autostart via freedesktop service file (data/com.github.sammarxz.pomerode.service.in)
• Build & Packaging
• Meson build files at root, src/, data/, po/ for translations
• Ninja as build executor
• External Dependencies
• elementary OS platform (Granite)
• GTK4, libadwaita
Relationships & Data Flow
• UI Layer → emits signals (Start, Stop, Preferences changed) → Application Core
• Application Core ↔ GSettings store (read/write durations, preferences)
• Application Core → triggers Notifications → System Notification Service
• Application Core → updates UI (session counters, progress bars)
• Build System → compiles Vala → links GTK4, libadwaita, Granite → generates executable with embedded GResource
Architectural Patterns & Design Principles
• MVC-like separation:
• View: UI files + CSS (data/ui, data/css)
• Controller/Model: Vala classes in src/ (application.vala, util.vala, preferences.vala, window.vala)
• Resource bundling via GResource for single-bundle deployment
• Use of GSettings for centralized, persistent configuration
Essential Elements
• All Vala classes in the core and their roles (main, application, window, preferences, util)
• UI files and CSS as part of the View layer
• GSettings schema XML and service file templates in the configuration layer
• Build artifacts: meson.build files orchestrating compile/link steps
• External dependencies (GTK4, libadwaita, Granite, elementary-sdk)