Re: [Interest] Qt5 and global configuration

2014-11-14 Thread Stanislav Baiduzhyi
On Thursday 13 November 2014 14:59:19 Thiago Macieira wrote: Which means that we should not use Qt5 apps on less supported desktop environments and we should not use Qt5 apps launched under another user with empty home folder? No, it means Qt 5 needs to support those desktops too, as much

Re: [Interest] Qt5 and global configuration

2014-11-14 Thread Stanislav Baiduzhyi
On Thursday 13 November 2014 20:12:46 René J.V. Bertin wrote: solve the majority of issues: ... fontconfig ... XDG That's all that needed to make Qt5 look bearable on unconfigured/unsupported desktop. There you go ... Linux is the new MS Windows? :) Fontconfig is present on OS X but I

Re: [Interest] Qt5 and global configuration

2014-11-14 Thread Constantin Makshin
On 11/14/2014 02:41 PM, Stanislav Baiduzhyi wrote: - when you're using some brand new laptop your physical screen dimension may not be present in X db yet, which means that X just takes your screen resolution, assumes 96dpi and calculates physical dimensions based on that, which usually

Re: [Interest] Qt5 and global configuration

2014-11-14 Thread Stanislav Baiduzhyi
On Friday 14 November 2014 15:10:05 Constantin Makshin wrote: On 11/14/2014 02:41 PM, Stanislav Baiduzhyi wrote: - when you're using some brand new laptop your physical screen dimension may not be present in X db yet, which means that X just takes your screen resolution, assumes 96dpi and

Re: [Interest] Qt5 and global configuration

2014-11-14 Thread Constantin Makshin
Probably lack of similar problems with my screens (both notebook and desktop) made me over-optimistic. :) On 11/14/2014 03:20 PM, Stanislav Baiduzhyi wrote: On Friday 14 November 2014 15:10:05 Constantin Makshin wrote: On 11/14/2014 02:41 PM, Stanislav Baiduzhyi wrote: - when you're using some

Re: [Interest] Qt5 and global configuration

2014-11-14 Thread Thiago Macieira
On Friday 14 November 2014 12:41:08 Stanislav Baiduzhyi wrote: 2. Read 'dpi' config value from fontconfig. Disagreed. The DPI value comes from the windowing system, not from fontconfig. There are multiple issues with that. I'm talking about X right now: [cut] All of those you listed

Re: [Interest] Qt5 and global configuration

2014-11-14 Thread Stanislav Baiduzhyi
On Friday 14 November 2014 09:08:11 Thiago Macieira wrote: All of those you listed are true, but you're asking for us to work around a structural problem in X (which we usually do). And in fact, we're already doing the necessary changes to support high DPI. I don't think the DPI is an issue

Re: [Interest] Qt5 and global configuration

2014-11-13 Thread Stanislav Baiduzhyi
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

Re: [Interest] Qt5 and global configuration

2014-11-13 Thread Thiago Macieira
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

Re: [Interest] Qt5 and global configuration

2014-11-13 Thread Stanislav Baiduzhyi
On Thursday 13 November 2014 09:25:43 Thiago Macieira wrote: 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

Re: [Interest] Qt5 and global configuration

2014-11-13 Thread René J . V . Bertin
On Thursday November 13 2014 18:52:45 Stanislav Baiduzhyi wrote: 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. That's fine on an OS that gives a choice of desktops, but much less so on a system that doesn't. Especially

Re: [Interest] Qt5 and global configuration

2014-11-12 Thread Thiago Macieira
On Wednesday 12 November 2014 12:18:02 René J.V. Bertin wrote: One of the really nice things in Qt4 was that one could take the appearance parameters available for individual applications (style, default font but also the font replacement table) and set them on a system/user-wide basis via

Re: [Interest] Qt5 and global configuration

2014-11-12 Thread Jérôme Godbout
In the same line about the style, I was wondering the same thing to set a global style for a particular widgets a little while ago: http://qt-project.org/forums/viewthread/45862/ Would have been nice to avoid setting style to each controls individualy. The only things I see is making a singleton

Re: [Interest] Qt5 and global configuration

2014-11-12 Thread René J . V . Bertin
On Wednesday November 12 2014 12:46:02 Thiago Macieira wrote: 1) application self-containing: we don't want to open files we shouldn't, especially on more locked-down platforms like OS X ?? Why would Qt (apps) not be able to open Qt configuration files? Thank goodness OS X hasn't yet become

Re: [Interest] Qt5 and global configuration

2014-11-12 Thread Thiago Macieira
On Wednesday 12 November 2014 23:10:49 René J.V. Bertin wrote: On Wednesday November 12 2014 12:46:02 Thiago Macieira wrote: 1) application self-containing: we don't want to open files we shouldn't, especially on more locked-down platforms like OS X ?? Why would Qt (apps) not be able to

Re: [Interest] Qt5 and global configuration

2014-11-12 Thread René J . V . Bertin
On Wednesday November 12 2014 16:12:42 Thiago Macieira wrote: Setting a default style is almost feasible on OS X by making the bundle executable a shell script that calls the binary with a style choice. Same cannot be said about the default font, though. Agreed, the -style option should

Re: [Interest] Qt5 and global configuration

2014-11-12 Thread Thiago Macieira
On Thursday 13 November 2014 01:46:56 René J.V. Bertin wrote: developer to use when writing the application, not meant to be used in production or, worse, be used by the user. Oh, horror, yes, the user using an option! I mean, we all know that only we developers know what's good for Joe