Re: Look and Feel in 5.8

2017-02-16 Thread Sebastian Kügler
On donderdag 16 februari 2017 14:45:25 CET Marco Martin wrote: > On Thursday 16 February 2017 11:38:57 Sebastian Kügler wrote: > > > > > > I would actually remove the button from next 5.8 release at this > > > point, if people are ok > > > > > OK, we're not really breaking functionality, and

Re: Look and Feel in 5.8

2017-02-16 Thread Marco Martin
On Thursday 16 February 2017 11:38:57 Sebastian Kügler wrote: > > I would actually remove the button from next 5.8 release at this > > point, if people are ok > > OK, we're not really breaking functionality, and the sooner we do it, the > better. done. button removed from 5.8, all merged and

Re: Look and Feel in 5.8

2017-02-16 Thread Sebastian Kügler
On dinsdag 14 februari 2017 13:11:04 CET Marco Martin wrote: > On Wed, Feb 8, 2017 at 11:39 PM, Łukasz Sawicki wrote: > > > > However what saddens me the most is the fact that I warned you guys > > about potential issues before Plasma 5.8 release in September. [2]. > > Either

Re: Look and Feel in 5.8

2017-02-14 Thread Marco Martin
On Wed, Feb 8, 2017 at 11:39 PM, Łukasz Sawicki wrote: > However what saddens me the most is the fact that I warned you guys > about potential issues before Plasma 5.8 release in September. [2]. > Either way it is up to you how are going to solve this "problem". In > any case, I

Look and Feel in 5.8

2017-02-08 Thread Łukasz Sawicki
Hi, Long story short. We have 3 basics problems with Look and Feel in Plasma 5.8 1. While support for dependencies was implemented in KDE Frameworks 5.29, one needs Frameworks 5.31 (yet to be released) for more or less bug free experience. And I assume that most of the l themes will use this

Look and Feel in 5.8

2017-02-07 Thread Sebastian Kügler
Hey, One of the topics that were put in the Etherpad for the Plasma sprint is the following: - get new look: remove it from 5.8? users complain that breaks their system as it doesn't support dependencies in 5.8 (deps can't be backported either,as would bump frameworks requirement); now we