kirigami-app-components in frameworks

[Aleix Pol]

+1 in general, but I'd say it should go hand-in-hand with figuring out
Kirigami Addons as I fear it's making the story even more complex. If
the plan is to use this then we should have a plan to bring all the
necessary features and phase out Kirigami Addons.

In the end, the only reason for either to exist is dependency
management as Kirigami itself already is app components too.

Aleix

On Fri, Aug 28, 2026 at 2:45 PM Marco Martin <notmart at gmail.com> wrote:
>
> Hi all,
> I would like the eventual inclusion of the repo
> kirigami-app-components in frameworks.
> It's stable and is already used by some applications, like koko and Keepsecret.
> Right now is a single qml module for user-configurable keyboard
> shortcuts in applications.
> It's planned to eventually expand it to other modules but strictly in
> the topic of "components needed for an application to look more like a
> desktop application well integrated with the rest of KDE
> technologies". basically... the kxmlgui of qml in a sense :p
>
> right now there was kirigami-addons with kinda this goal even if not
> 100% overlapping, but it grown a bit too much organically, so none of
> the parties was confident in "just make it a framework as is"
> So it was in the past decided to do a new project both with new
> modules, and eventually with modules coming from kirigami-addons (with
> all the needed refactors, as the new namespace would allow api break,
> if needed)
>
> comments? opinions?
>
> --
> Marco Martin