On Thursday 10 December 2015 12:43:29 Martin Graesslin wrote:
> On Thursday, December 10, 2015 12:24:06 PM CET Kevin Ottens wrote:
> > > As I just said: I consider this as a useless exercise and a waste of my
> > > time (and of anybody else who would do that).
> >
> > Note that it's a waste of tim
On Thursday, December 10, 2015 12:24:06 PM CET Kevin Ottens wrote:
> > As I just said: I consider this as a useless exercise and a waste of my
> > time (and of anybody else who would do that).
>
> Note that it's a waste of time which could have been easily avoided. If the
> goal was to get somethi
On Thursday 10 December 2015 08:02:49 Martin Graesslin wrote:
> On Wednesday, December 9, 2015 6:14:47 PM CET Kevin Ottens wrote:
> > > I just started looking into doing the replacement and noticed that I'm
> > > also using:
> > > * Non-static data member initializers (N2756), gcc 4.7
> > > * Range
On Thursday, December 10, 2015 1:07:42 PM CET Boudhayan Gupta wrote:
> On 10 December 2015 at 12:32, Martin Graesslin wrote:
> > yes, that's the annoying one which is lots of work and lots of possible
> > regressions. I'm not sure whether I'm willing to do that work which I
> > consider a useless
On 10 December 2015 at 12:32, Martin Graesslin wrote:
> yes, that's the annoying one which is lots of work and lots of possible
> regressions. I'm not sure whether I'm willing to do that work which I consider
> a useless exercise.
In my opinion this discussion is an useless exercise, because:
>
On Wednesday, December 9, 2015 6:14:47 PM CET Kevin Ottens wrote:
> > I just started looking into doing the replacement and noticed that I'm
> > also
> > using:
> > * Non-static data member initializers (N2756), gcc 4.7
> > * Range-based for (N2930), gcc 4.6
>
> Note that if you do that with Qt co
Hello,
On Wednesday 09 December 2015 10:07:50 Martin Graesslin wrote:
> On Thursday, November 5, 2015 11:10:49 AM CET Kevin Ottens wrote:
> > Hello,
> >
> > On Thursday 05 November 2015 10:50:06 Martin Graesslin wrote:
> > > There are two things which make the move to frameworks difficult and I
>
On Thursday, November 5, 2015 11:10:49 AM CET Kevin Ottens wrote:
> Hello,
>
> On Thursday 05 November 2015 10:50:06 Martin Graesslin wrote:
> > There are two things which make the move to frameworks difficult and I
> > don't see a solution to it at the moment:
> >
> > 1. We require C++11 without
On Thursday, November 5, 2015 10:50:06 AM CET Martin Graesslin wrote:
> 2. We use Qt 5.4.
Given David's suggestion on having the last three released Qt releases
supported, this issue will resolve itself once Qt 5.6 is released. Given that
this is on the horizon I will delay the move of KWayland
On Thursday 05 November 2015 10:50:06 Martin Graesslin wrote:
> Hi,
>
> after the Plasma 5.5 release I would like to move KWayland to frameworks.
> The main reason is that it is oddly placed in plasma-workspace as it's also
> a library useful for applications (example kde-connect uses it already).
Hello,
On Thursday 05 November 2015 10:50:06 Martin Graesslin wrote:
> There are two things which make the move to frameworks difficult and I don't
> see a solution to it at the moment:
>
> 1. We require C++11 without exceptions: reason, it's designed for Linux and
> it didn't come to my mind to
11 matches
Mail list logo
