David Redondo

Oh I made [patch](https://github.com/Sodivad/xdg-desktop-portal/commit/d7791150211ef28da7ddf87e1dc63960824d66a2) recently (but didn't open a MR yet, actually I was just about to do when I saw this issue) that's similar to your idea but goes...

Thanks for the examples, not coming from that corner of things I was not aware of all of that in detail and see that per-interface is indeed useful and brings...

I think the main point then that we want to specify a specific fallback on multiple environments while not overriding their own portal if they have one or create one...

>In @ebassi's proposal, it's only the maintainers of a backend who are responsible for knowing things about the implementation of that backend: the maintainers of x-d-p-gtk need to know that...

It doesn't have to distributions but shouldn't desktop projects decide themselves which portal implementation they want to use not the developer of a implementation? And not have to go to...

Support in Qt and KDE portal https://codereview.qt-project.org/c/qt/qtbase/+/478997 https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/199

> short of using https://github.com/swaywm/wlr-protocols/pull/25 which is not available outside of wlroots based compositors KWin implements it too

Hi we actually do not use qt-surface-extension for this (anymore? this was before I joined devleopment) but have our own protocol for [appmenu](https://invent.kde.org/libraries/plasma-wayland-protocols/-/blob/master/src/protocols/appmenu.xml?ref_type=heads) . Related is the standardising effort https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/52

> added explicit link interface to Qt5/Qt6 variants Is having Qt5/Qt6 be possible at the same time still relevant nowadays instead of just doing Qt6?

> Code is inspired by libtaskmanager/waylandtasksmodel.cpp Awesome that the code works for you but in this case the inspiration seems was rather strong and seems to include copied code from...