Window geometry and position is supposed to be saved automatically by KXMLGui, at least for widgets apps. If that's not possible to do here, perhaps we should have Kirigami do this at the frameworks level so it doesn't need to be done by every single app.

my concern here using qsettings in this place, is that then it kinda clashes when an application uses its own config like it should, from a framework (kconfiggroup, kconfigskeleton etc)
i always refrained from using any form of config read/write here, and i think we should continue to do so.
Kirigami is a tier1 framework that should do the kleast possible, is more like KGuiAddons/§KWidgetAddons, *not* a full feature kxmlgui, which if we want to have something along the lines, we should have a proper framework to do so, and not tier1

In D28971#652708, @mart wrote:

i always refrained from using any form of config read/write here, and i think we should continue to do so.

Are you referring to the gallery (this patch) or to Kirigami?

In D28971#652708, @mart wrote:

my concern here using qsettings in this place, is that then it kinda clashes when an application uses its own config like it should, from a framework (kconfiggroup, kconfigskeleton etc)
i always refrained from using any form of config read/write here, and i think we should continue to do so.
Kirigami is a tier1 framework that should do the kleast possible, is more like KGuiAddons/§KWidgetAddons, *not* a full feature kxmlgui, which if we want to have something along the lines, we should have a proper framework to do so, and not tier1

If that's your vision for Kirigami, then we definitely need one, yeah. Otherwise our QML apps are going to need to endlessly reinvent this kind of wheel.