Extract bos-settings to its own repo; add breadhelp; JSON-driven Hyprland config
bos-settings moves to git.breadway.dev/Breadway/bos-settings (full history preserved via git-filter-repo) so its release cadence is decoupled from BOS's own. breadhelp takes its place as this repo's workspace member: a GTK4 onboarding/help center replacing the old bos-welcome/bos-keybinds bash scripts with searchable guides, an interactive keybind viewer (sourced from the new keybinds.toml, not parsed out of hyprland.lua or hardcoded), a troubleshooting wizard with one-click fixes, and a proper first-run tour. bos-netcheck extracts bos-welcome's network-check half, which still needs to run every login independent of breadhelp's own first-run gating. hyprland.lua's keybinds/settings/monitors/autostart are now JSON-driven (binds.json/settings.json/monitors.json/autostart.json) with every loader pcall-wrapped and falling back to hardcoded defaults per field on bad or missing config, so bread* apps (bos-settings' new editors, and breadhelp's keybind viewer) can read/write this config without ever being able to leave the compositor unable to start. CI's package.yml now builds breadhelp instead of bos-settings on tag push; bos-settings needs its own equivalent workflow in its new repo (not yet set up).
This commit is contained in:
commit
fea8f83204
50 changed files with 2403 additions and 0 deletions
34
src/main.rs
Normal file
34
src/main.rs
Normal file
|
|
@ -0,0 +1,34 @@
|
|||
mod cli;
|
||||
mod config;
|
||||
mod content;
|
||||
mod services;
|
||||
mod theme;
|
||||
mod ui;
|
||||
|
||||
use gtk4::gio::ApplicationFlags;
|
||||
use gtk4::prelude::*;
|
||||
|
||||
fn main() {
|
||||
// GApplication requires a dotted id (g_application_id_is_valid rejects a
|
||||
// bare "breadhelp" with a GLib-GIO-CRITICAL and silently skips setting
|
||||
// it, which would break D-Bus single-instance activation). The Wayland
|
||||
// app-id GTK reports is this exact string — the Hyprland window rule and
|
||||
// .desktop's StartupWMClass must match it verbatim.
|
||||
//
|
||||
// HANDLES_COMMAND_LINE: `breadhelp --onboard` while already running must
|
||||
// reach the running (primary) instance's argv, not just re-activate it
|
||||
// with no arguments — that's what lets a second launch re-trigger the
|
||||
// onboarding tour instead of only focusing the window.
|
||||
let app = gtk4::Application::builder()
|
||||
.application_id("com.breadway.breadhelp")
|
||||
.flags(ApplicationFlags::HANDLES_COMMAND_LINE)
|
||||
.build();
|
||||
|
||||
app.connect_command_line(|app, cmdline| {
|
||||
let action = cli::parse(&cmdline.arguments());
|
||||
ui::window::present(app, action);
|
||||
glib::ExitCode::SUCCESS
|
||||
});
|
||||
|
||||
app.run();
|
||||
}
|
||||
Loading…
Add table
Add a link
Reference in a new issue