Message: previous - next
Month: September 2013

Re: Re: [trinity-devel] My opinion on Trinity project quality

From: Martin Gräßlin <mgraesslin@...>
Date: Thu, 19 Sep 2013 13:02:55 +0200
On Thursday 19 September 2013 12:35:17 Aleksey Midenkov wrote:
> >  Qt4 decided that they wanted to be a compositor instead of
> > passing compositing off to the native display server, and most of the
> > performance problems and drawing limitations stem from this decision.
> Hmm, interesting news. Ok, that's a good reason to stay with Qt3. I
> don't like how Qt4 performs either.
It's not interesting news, it's just wrong. Qt's internal rendering doesn't 
depend on whether compositing is used or not. Even more a compositor would not 
even be able to make use of any optimizations done inside Qt for the 
composited case, because there is no way for the compositor to know that the 
app "supports" it. Compositing on X11 happens behind the scenes of the window. 
The window doesn't and doesn't need to know that it gets composited.


Maintainer of the X11 Compositor of the KDE Plasma Workspaces