https://bugs.kde.org/show_bug.cgi?id=377918
--- Comment #3 from RJVB <rjvber...@gmail.com> --- Does Gnome provide a QPA platform plugin akin to the plasma-integration plugin? The env. variable may not be meant as a choice for the user, but it sure can become one for the typical KDevelop user. Who probably couldn't care less if the dialog looks different: if it provides features that are more in line with his/her use of KDevelop different looks aren't out of place. It's not up to individual applications to protect users from doing something different, or to do what I call dictating the emperor's clothes. Anyone who wants can use different widget styles with any application, and that shouldn't be thwarted. Indeed, the choice of filedialog can be made at the QPA plugin level, but not all platforms have such plugins, or make it easy to use one (and not because it's forbidden by Qt). Mac and (probably) MS Windows are examples. I cannot speak for MSWin, but I don't feel the KDE dialog looks out of place on Mac. It looks a bit different the way all KDE software looks with a pure native style without support for KDE's font roles, but the Mac OS has seen file dialog customisation (hacked or via system APIs) probably for longer than KDE has been around. I think I mentioned the following when the topic came up earlier: I maintain a KDE platform plugin for Mac, so that KDE applications can look the way they're designed to look, whether that's using the Macintosh style, Breeze, QtCurve or anything else. That QPA plugin does in fact instruct Qt to use native file dialogs by default, because I happen to prefer them for simple applications. For KDevelop the native dialog is no match though, esp. not when opening files or even more so, importing a project. And again: they only look like native dialogs. PS: KDE's QPA plugin doesn't use KDE_FULL_SESSION, AFAIK. -- You are receiving this mail because: You are watching all bug changes.
