Re: KDE backward compatibility issue

2015-02-05 Thread Aleix Pol
On Fri, Jan 30, 2015 at 11:41 AM, Vasily Khoruzhick wrote: > Hi, > > I'd like to rise KDE backward compatibility issue once again. > > I've read [1] and [2] and as far as I understand, dropping xembed > support was more political decision than technical difficulty. Ple

Re: Re: KDE backward compatibility issue

2015-02-04 Thread Martin Gräßlin
On Wednesday 04 February 2015 22:15:54 Vasily Khoruzhick wrote: > On Wed, Feb 4, 2015 at 9:57 PM, Milian Wolff wrote: > > "Every application"? You mention two. > > Well, at least these two are affected. I can also mention tuxguitar > which uses Java and SWT, however I don't care about its tray ic

Re: KDE backward compatibility issue

2015-02-04 Thread Vasily Khoruzhick
On Wed, Feb 4, 2015 at 9:57 PM, Milian Wolff wrote: > "Every application"? You mention two. Well, at least these two are affected. I can also mention tuxguitar which uses Java and SWT, however I don't care about its tray icon. > And if they, or others, don't care about > us, why should we go o

Re: KDE backward compatibility issue

2015-02-04 Thread Milian Wolff
On Wednesday 04 February 2015 21:49:15 Vasily Khoruzhick wrote: > Hi Milian, > > On Wed, Feb 4, 2015 at 9:04 PM, Milian Wolff wrote: > > If these apps link against Qt5 statically (which they can, assuming they > > pay the license fees to Digia), then they will need to recompile and > > release an

Re: KDE backward compatibility issue

2015-02-04 Thread Vasily Khoruzhick
Hi Milian, On Wed, Feb 4, 2015 at 9:04 PM, Milian Wolff wrote: > > If these apps link against Qt5 statically (which they can, assuming they pay > the license fees to Digia), then they will need to recompile and release an > updated version. If otoh they just ship they own set of libs and adapt >

Re: KDE backward compatibility issue

2015-02-04 Thread Milian Wolff
On Wednesday 04 February 2015 20:42:53 Vasily Khoruzhick wrote: > Hi Sebastian, > > On Wed, Feb 4, 2015 at 8:15 PM, Sebastian Kügler wrote: > > There are patches for Qt < 5.4 around which are have been shipped by > > various distributions for quite some time. Martin's blog, which you > > linked f

Re: KDE backward compatibility issue

2015-02-04 Thread Vasily Khoruzhick
Hi Sebastian, On Wed, Feb 4, 2015 at 8:15 PM, Sebastian Kügler wrote: > > There are patches for Qt < 5.4 around which are have been shipped by various > distributions for quite some time. Martin's blog, which you linked from your > initial email, links them: > > http://blog.martin-graesslin.com/b

Re: KDE backward compatibility issue

2015-02-04 Thread Sebastian Kügler
On Friday, January 30, 2015 13:41:42 Vasily Khoruzhick wrote: > There're some proprietary applications using xembed tray and Qt5 < > 5.4, for example - dropbox and viber. There's no way to fix them. There are patches for Qt < 5.4 around which are have been shipped by various distributions for qui

Re: KDE backward compatibility issue

2015-01-30 Thread Todd Rme
On Fri, Jan 30, 2015 at 6:40 PM, Thomas Lübking wrote: > On Freitag, 30. Januar 2015 18:22:03 CEST, Vasily Khoruzhick wrote: > >> It's a way to keep all tray icons on the panel. In case of horizontal >> panel >> it's even seemless > > > I'd not rather not expect a "seamless" result from this appro

Re: KDE backward compatibility issue

2015-01-30 Thread Thomas Lübking
On Freitag, 30. Januar 2015 18:22:03 CEST, Vasily Khoruzhick wrote: It's a way to keep all tray icons on the panel. In case of horizontal panel it's even seemless I'd not rather not expect a "seamless" result from this approach. You'll have an autopositioned/hiding wmsystemtray though, that's

Re: KDE backward compatibility issue

2015-01-30 Thread Vasily Khoruzhick
On Fri, Jan 30, 2015 at 8:14 PM, Thomas Lübking wrote: > On Freitag, 30. Januar 2015 18:04:03 CEST, Martin Graesslin wrote: Hi Thomas, > What he suggests is to add a spacer into a panel and move a root parented > XEmbed override_redirect container there. > That's trivial enough (the spacer only

Re: KDE backward compatibility issue

2015-01-30 Thread Thomas Lübking
On Freitag, 30. Januar 2015 18:04:03 CEST, Martin Graesslin wrote: Patches welcome. If you think it's important and that trivial you should be able to do it, right? What he suggests is to add a spacer into a panel and move a root parented XEmbed override_redirect container there. That's trivi

Re: KDE backward compatibility issue

2015-01-30 Thread Vasily Khoruzhick
On Fri, Jan 30, 2015 at 8:04 PM, Martin Graesslin wrote: Hi Martin, > Patches welcome. If you think it's important and that trivial you should be > able to do it, right? Well, my area of expertise is embedded, kernel drivers and bootloaders. But OK, I'll try to implement a xembed tray widget. I

Re: KDE backward compatibility issue

2015-01-30 Thread Martin Graesslin
On Friday 30 January 2015 19:58:04 Vasily Khoruzhick wrote: > On Fri, Jan 30, 2015 at 6:02 PM, Christoph Feck wrote: > > On Friday 30 January 2015 11:41:42 Vasily Khoruzhick wrote: > >> I've read [1] and [2] and as far as I understand, dropping xembed > >> support was more political decision than

Re: KDE backward compatibility issue

2015-01-30 Thread Vasily Khoruzhick
On Fri, Jan 30, 2015 at 6:02 PM, Christoph Feck wrote: > On Friday 30 January 2015 11:41:42 Vasily Khoruzhick wrote: >> I've read [1] and [2] and as far as I understand, dropping xembed >> support was more political decision than technical difficulty. Hi Christoph, > I am sorry to say that you d

Re: KDE backward compatibility issue

2015-01-30 Thread Christoph Feck
On Friday 30 January 2015 11:41:42 Vasily Khoruzhick wrote: > I've read [1] and [2] and as far as I understand, dropping xembed > support was more political decision than technical difficulty. I am sorry to say that you did understand wrong. It was mostly a technical decision. You are free to por

KDE backward compatibility issue

2015-01-30 Thread Vasily Khoruzhick
Hi, I'd like to rise KDE backward compatibility issue once again. I've read [1] and [2] and as far as I understand, dropping xembed support was more political decision than technical difficulty. Please kindly understand that breaking applications for users is a no-go. I'd l