How kaii-lb/overskride works
Project type and purpose
• Type: Native desktop application written in Rust with a GTK4/libadwaita UI.
• Purpose: A GUI Bluetooth & OBEX client (device enumeration, pairing, file transfer) that is DE/WM-agnostic and packaged via Flatpak.
File structure
• Top-level build: Cargo.toml (Rust), meson.build (Meson/Ninja), Flatpak build scripts (build-flatpak.sh, make-pkg.sh).
• src/: application.rs & main.rs (entry), modules:
– bluetooth/: D-Bus wrappers & business logic for BlueZ (agent, profiles, battery, services).
– obex/: OBEX client implementation.
– gtk/: .blp UI templates & CSS for views.
– widgets/: custom GTK widget code (battery indicator, device rows, popovers).
– config.rs: settings management (glib-schemas XML).
– window.rs: top-level window orchestration.
• assets/: static images (splash/screenshots).
• po/: localization support.
• subprojects/: wrap for third-party code (e.g., blueprint-compiler).
Extract insights from README
• Uses systemd-enabled Bluetooth daemon (BlueZ).
• Built & run via Meson + glib-compile-schemas + Flatpak.
• Core features: device listing, pairing/authentication, file send/receive, adapter management, battery & audio profiles.
Core components
a. Frontend (UI Layer)
– GTK4/libadwaita widgets & views (.blp files + CSS)
– Window manager: application.rs → window.rs
b. Backend (Logic Layer)
– Bluetooth Manager (src/bluetooth/*)
– OBEX Client (src/obex/*)
– Configuration Service (src/config.rs + gschema.xml)
c. Data & Storage
– Local user settings (dconf/GLib settings)
– File transfer storage location
d. External Services
– BlueZ D-Bus API (org.bluez)
– systemd (bluetooth.service)
– Flatpak runtime (org.gnome.Platform)
e. Build & Packaging
– Meson build system & Ninja
– Cargo for Rust crates
– Flatpak bundling
Relationships & interactions
• UI Layer emits user events → Logic Layer
• Bluetooth Manager ↔ BlueZ via D-Bus (pair, connect, battery polling)
• OBEX Client ↔ BlueZ’s obexd or direct OBEX channel
• Logic Layer updates UI via signals (GLib main loop)
• Config Service ⇄ dconf/GSettings backend
• File I/O: Logic stores incoming files under configured directory
• Localization: po/ files → gettext
• Build Flow: Meson calls Cargo, processes data/, compiles glib-schemas, packs Flatpak
Architectural patterns & principles
• Event-driven (GLib main loop dispatch)
• Modular separation: UI vs. business logic vs. protocol layers
• MVC-style: widgets/views (View), bluetooth/obex modules (Model/Controller)
• Single-process, asynchronous calls to D-Bus