On Thursday 13 November 2014 10:19:40 Stanislav Baiduzhyi wrote: > On Wednesday 12 November 2014 12:46:02 Thiago Macieira wrote: > > 3) delegation: this is delegated to the platform theme plugins. Qt > > applications are meant to look like the system, therefore the the plugin > > will decide what the application should look like and which files it needs > > to read in order to come to the right decisions. > > > > We could provide a plugin that reads configuration files, but it would not > > be the default in any platform. > > That can be extremely problematic on desktops without any kind of UI or less > supported UI. Think of TWM, IceWM, some rare desktops like now perished > RazorQt and stuff like that. Or adding second user on your main system but > not logging in for the first time to allow KDE or gnome to create any > configuration, but just launching Qt apps with kdesu or sudo. In addition, > all of that can go though vnc to the display with ppi resolution very far > from one the app is launched on. In those cases having normal > configurations hierarchy (like read app settings, fallback to ~/.config, > fallback to /etc) would be extremely helpful. And that is one of the > reasons why using Qt4 apps in all of those cases I listed above is way more > convenient than using Qt5 apps.
Qt is not a desktop. I don't like the idea of qtconfig because it's not Qt's purpose to do that. It's the desktop's. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest