Re: KDE file dialog

I realize I'm slightly orthagonal to the original topic, but On Sat, Mar 5, 2016 at 11:14 PM, Kai Uwe Broulik wrote: > Hi, > >> Distributions set up distribution-wide "Sans", "Serif" and "Monospace" >> aliases for a reason. The fonts are carefully selected by the

Re: KDE file dialog

Hi, > Distributions set up distribution-wide "Sans", "Serif" and "Monospace" > aliases for a reason. The fonts are carefully selected by the distribution > based on a variety of criteria, including glyph coverage We tried to keep font decisions to distributions before Plasma 5 and it always

Re: KDE file dialog

On Sonntag, 6. März 2016 11:34:32 CEST, Martin Graesslin wrote: I don't know how often we have heard over the last decade that Plasma's look and feel is terribly because of fonts. I'd have assumed that'd be because of the freetype rasterizers being, errr ummm... shit (almost as shit as

Re: KDE file dialog

On Sunday, March 6, 2016 1:48:13 AM CET Kevin Kofler wrote: > Martin Graesslin wrote: > > No, because everything in the current plugin is Plasma specific. If we > > want to change the font, we will do so! > > Forcing a default font as you have done is a bad idea even on Plasma. It is > not the

Re: KDE file dialog

Martin Graesslin wrote: > No, because everything in the current plugin is Plasma specific. If we > want to change the font, we will do so! Forcing a default font as you have done is a bad idea even on Plasma. It is not the desktop environment's business to pick a default font. (And yes, I know

Re: KDE file dialog

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

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

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

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

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

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

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

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

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

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

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),

Re: KDE file dialog

On Tuesday, March 1, 2016 7:37:55 PM CET Mark Gaiser wrote: > Op 29 feb. 2016 11:10 p.m. schreef "Thiago Macieira" : > > On segunda-feira, 29 de fevereiro de 2016 21:42:11 PST Sven Brauch wrote: > > > Hey, > > > > > > On 02/28/2016 03:58 PM, Luigi Toscano wrote: > > > > This is

Re: KDE file dialog

On terça-feira, 1 de março de 2016 21:20:03 PST Mark Gaiser wrote: > Isn't it possible to have the platform theme as it was before (with no > plasma deps) for others to use and then some "more fancy" plugin on top of > that which would implement just the plasma specific things? That way > everyone

Re: KDE file dialog

On Dienstag, 1. März 2016 19:42:58 CEST, Sven Brauch wrote: Otherwise I agree with your reasoning. I'm just not sure what we can effectively do about it. Build option to build the kde/plasma QPA into a strict "KF5" (tier 1) QPA? Forking sucks terribly and a tier 1 QPA might be interesting for

Re: KDE file dialog

Hey, On 03/01/2016 07:37 PM, Mark Gaiser wrote: > but there is > undoubtedly going to be a point in time where the plugin only works when > some very specific plasma part is required for it to function That is already the case; try running an application with a systray icon, it will not work (or

Re: KDE file dialog

On Tuesday, March 01, 2016 06:45:14 PM Martin Koller wrote: > On Monday 29 February 2016 21:34:13 Luigi Toscano wrote: > > > Should a KF5 app (with frameworksintegration) not also use the settings > > > from a still used KDE4 desktop ?> > > > > > > frameworksintegration is going to be part of

Re: KDE file dialog

On Tue, Mar 1, 2016 at 7:42 PM, Sven Brauch wrote: > Hey, > > On 03/01/2016 07:37 PM, Mark Gaiser wrote: > > but there is > > undoubtedly going to be a point in time where the plugin only works when > > some very specific plasma part is required for it to function > That is

Re: KDE file dialog

Op 29 feb. 2016 11:10 p.m. schreef "Thiago Macieira" : > > On segunda-feira, 29 de fevereiro de 2016 21:42:11 PST 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

Re: KDE file dialog

On Monday 29 February 2016 21:34:13 Luigi Toscano wrote: > > Should a KF5 app (with frameworksintegration) not also use the settings > > from a still used KDE4 desktop ? > > frameworksintegration is going to be part of plasma, in fact. There would need > to be an "old plasma" integration. Or

Re: KDE file dialog

On 02/29/2016 11:09 PM, Thiago Macieira wrote: >> So using QT_QPA_PLATFORMTHEME=kde is basically not a viable solution for >> > any non-plasma desktop out there. Instead you are stuck with a 3rd party >> > solution like qt5ct to at least set the Qt / icon theme (color scheme is >> > quite hard

Re: KDE file dialog

On terça-feira, 1 de março de 2016 00:44:05 PST Sven Brauch wrote: > > If you're not in the Plasma desktop, you should get the dialogs from the > > desktop you're in. For example, if you're in GNOME, the GTK style plugin > > should get the GTK dialogs. > > But that assumes the desktop you're in

Re: KDE file dialog

On segunda-feira, 29 de fevereiro de 2016 21:42:11 PST 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

Re: KDE file dialog

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), it will be part of Plasma (but hopefully > still usable without). It isn't,

Re: KDE file dialog

Martin Koller ha scritto: > On Sunday 28 February 2016 15:58:20 Luigi Toscano wrote: >> Martin Koller ha scritto: >>> In KDE4 times there was a common file dialog for the applications, I think >>> this is what KFileDialog was made for. >>> Now where some applications are already ported to KF5,

Re: KDE file dialog

On Sunday 28 February 2016 15:58:20 Luigi Toscano wrote: > Martin Koller ha scritto: > > In KDE4 times there was a common file dialog for the applications, I think > > this is what KFileDialog was made for. > > Now where some applications are already ported to KF5, there seems to be no > > such

Re: KDE file dialog

On 28 February 2016 at 20:06, Aleix Pol wrote: > The string is in Qt, AFAIR. It probably can't be changed until Qt 6 if > we don't want to mess with existing installations. We should still probably alias it and deprecate 'kde', so that people can start using the right name

Re: KDE file dialog

On Sun, Feb 28, 2016 at 8:01 PM, Riccardo Iaconelli wrote: > On 28 February 2016 at 15:58, Luigi Toscano wrote: >> >> This is what I use: >> export QT_QPA_PLATFORMTHEME=kde > > (btw, shouldn't this be "plasma"?) The string is in Qt, AFAIR. It probably

Re: KDE file dialog

On 28 February 2016 at 15:58, Luigi Toscano wrote: > > This is what I use: > export QT_QPA_PLATFORMTHEME=kde (btw, shouldn't this be "plasma"?) -Riccardo -- Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平 Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini

Re: KDE file dialog

Martin Koller ha scritto: > In KDE4 times there was a common file dialog for the applications, I think > this is what KFileDialog was made for. > Now where some applications are already ported to KF5, there seems to be no > such thing anymore > (or it does not work here). > KFileDialog is

KDE file dialog

In KDE4 times there was a common file dialog for the applications, I think this is what KFileDialog was made for. Now where some applications are already ported to KF5, there seems to be no such thing anymore (or it does not work here). KFileDialog is deprecated, QFileDialog does not have the