In the current state of things, this component has lots of missed optential, showing the burger menu instead of hierarchichal appmenu would be a better option if possible. Having the menubar integrated into a dropdown menu isn't the best option for programs which haven't been meant to have it in the first place, such as krita or gimp, at the end making using those programs way more tedious. This is why I suggest it'd be a great option for the appmenu button to be integrated only if the program has burger menus and using them instead, it would allow for more efficent use of space and better end user experience.
> it'd be a great option for the appmenu button to be integrated only if the program has burger menus and using them instead When that's the case, then the burger menu is already displayed on the toolbar. Exporting this to KWin so that KWin could show it in place of the normal menu structure unfortunately is not really technically feasible. It's doable but only with enough engineering effort as to be not worth it, given that the using appmenu button is a non-default option, sorry!
It's all good :). I'd love to contribute on all sorts of stuff but I know all sorts of nothing, if I ever get into programming I'll see how possible it would be for me to do
Maybe having a blacklist/whitelist system would be a good compromise solution? I love the idea of this widget and it works incredibly well in apps like transmission, kwrite or dolphin but I don't want to turn it off manually every time I open gimp, krita, kdenlive or libreoffiice. Having those blacklisted by default wouldn't be a bad idea either :p