- Add a Preferences page (reachable from the hamburger menu) with a
KColorSchemeManager-backed color scheme switcher
- Add an About page reading from KAboutData
- Ship a full hicolor icon set (16-128px + scalable) via ecm_install_icons
instead of a single flat SVG
- Restyle the permissions list after KDE System Settings' Audio page:
Kirigami.ListSectionHeader per category, flat separated rows, no card
borders
- Explicitly declare Kirigami/KirigamiAddons/ColorScheme as CMake
dependencies instead of relying on the QML import scanner alone
- Add KDEClangFormat/KDEGitCommitHooks, a CMakePresets.json, and a
REUSE + clang-format lint CI workflow
- Reformat SPDX headers to include copyright, and tidy up a stray
namespace inconsistency
- Add .github/workflows/test.yml, using flatpak-builder's run-tests
option so PRs and pushes exercise ctest inside the same KDE SDK
sandbox as release builds.
- Add REUSE.toml covering files that can't carry an inline SPDX header
(.desktop, keys/*.asc, screenshots/*).
- Add CONTRIBUTING.md documenting build/test/release steps.
- Preserve override keys we do not model so Save never drops data
- Prompt before discarding unsaved changes when switching applications
- Native FormCard layout for the permission list (grouped cards)
- Filesystem entries gain an access-mode selector and a folder browser
- Add resolution autotests (toggle render/save, filesystem split, key preservation)
Inside a flatpak, XDG_DATA_HOME points at our own private data, so the
user-installation scan (and override writes) missed every user-installed
app, including FlatKontrol itself. Use HOST_XDG_DATA_HOME and the host
/etc path when running in a sandbox, matching Flatseal.
Adds a dedicated repo-signing public key and signs the exported repo,
static deltas, and single-file bundle. The public key is embedded in the
generated .flatpakrepo so installs no longer need --no-gpg-verify.
A KDE/Qt application to review and edit the permissions of installed
Flatpak applications, editing the same override files as Flatpak itself.
Covers shared subsystems, sockets, devices, features, filesystem access,
persistent paths, environment variables, D-Bus policies and portals.
Includes a Flatpak manifest and a CI workflow that publishes a bundle and
a hosted Flatpak repository on tagged releases.
austin