Re: KDE file dialog

2016-03-02 Thread Thomas Lübking
On Mittwoch, 2. März 2016 12:51:28 CEST, Martin Graesslin wrote: On Wednesday, March 2, 2016 12:09:17 PM CET Sven Brauch wrote: On 03/02/2016 11:56 AM, Thomas Lübking wrote: ... Just saying: I wrote that SNI integration and I have never heard of that problem before Sven mentioned it here.

Re: KDE file dialog

2016-03-02 Thread Martin Graesslin
On Wednesday, March 2, 2016 12:09:17 PM CET Sven Brauch wrote: > On 03/02/2016 11:56 AM, Thomas Lübking wrote: > > Imo that's a more issue: IPC is I/O, ie. unreliable. You cannot provide > > functionality that relies on working IPC, but hard-relying on it is bad > > design (nb. that the failing

Re: KDE file dialog

2016-03-02 Thread Martin Graesslin
On Wednesday, March 2, 2016 11:46:01 AM CET Sven Brauch wrote: > Hey, > > On 03/02/2016 11:19 AM, Martin Graesslin wrote: > > No, because everything in the current plugin is Plasma specific. > > Meh. In some kind of theoretical view you are right, I do see that. > Pragmatically, that's just not

Re: KDE file dialog

2016-03-02 Thread Marco Martin
On Wednesday 02 March 2016 11:19:42 Martin Graesslin wrote: > > What is that "kf5" plugin you talk of? Sorry this just does not make sense. > The plugin we have (and soon had) in frameworks is setting the defaults for > Plasma. There are no generic defaults for frameworks. It just does not make >

Re: KDE file dialog

2016-03-02 Thread Sven Brauch
On 03/02/2016 11:56 AM, Thomas Lübking wrote: > Imo that's a more issue: IPC is I/O, ie. unreliable. You cannot provide > functionality that relies on working IPC, but hard-relying on it is bad > design (nb. that the failing kded module make _every_ Qt client using > QSystemTray unusable and

Re: KDE file dialog

2016-03-02 Thread Thomas Lübking
On Mittwoch, 2. März 2016 11:19:42 CEST, Martin Graesslin wrote: On Wednesday, March 2, 2016 11:08:30 AM CET Mark Gaiser wrote: On Wed, Mar 2, 2016 at 9:42 AM, Martin Graesslin wrote: ... What is that "kf5" plugin you talk of? The origin of this thread was that the

Re: KDE file dialog

2016-03-02 Thread Sven Brauch
Hey, On 03/02/2016 11:19 AM, Martin Graesslin wrote: > No, because everything in the current plugin is Plasma specific. Meh. In some kind of theoretical view you are right, I do see that. Pragmatically, that's just not true, most of the things in the plugin are not plasma specific at all, for

Re: KDE file dialog

2016-03-02 Thread Martin Graesslin
On Wednesday, March 2, 2016 11:08:30 AM CET Mark Gaiser wrote: > On Wed, Mar 2, 2016 at 9:42 AM, Martin Graesslin wrote: > > On Monday, February 29, 2016 9:42:11 PM CET Sven Brauch wrote: > > > Hey, > > > > > > On 02/28/2016 03:58 PM, Luigi Toscano wrote: > > > > This is what

Re: KDE file dialog

2016-03-02 Thread Mark Gaiser
On Wed, Mar 2, 2016 at 9:42 AM, Martin Graesslin wrote: > On Monday, February 29, 2016 9:42:11 PM CET Sven Brauch wrote: > > Hey, > > > > On 02/28/2016 03:58 PM, Luigi Toscano wrote: > > > This is what I use: > > > export QT_QPA_PLATFORMTHEME=kde > > > > > > and you need the

Re: KDE file dialog

2016-03-02 Thread Marco Martin
On Wednesday 02 March 2016 09:42:06 Martin Graesslin wrote: > If you think Qt's default is too bad, improve Qt. If you think it needs a > more generic qpt-plugin which can be used outside of Plasma: do it. But > don't complain to people doing actual work. ^^This -- Marco Martin

Re: KDE file dialog

2016-03-02 Thread Martin Graesslin
On Monday, February 29, 2016 9:42:11 PM CET Sven Brauch wrote: > Hey, > > On 02/28/2016 03:58 PM, Luigi Toscano wrote: > > This is what I use: > > export QT_QPA_PLATFORMTHEME=kde > > > > and you need the integration plugin installed. It used to be part of > > Frameworks (frameworksintegration),