Message: previous - next
Month: December 2011

Re: Re: [trinity-devel] Suggestion to drop [t|k]win from Trinity and replace it by KWin4

From: Martin Gräßlin <mgraesslin@...>
Date: Sat, 10 Dec 2011 20:16:39 +0100
On Saturday 10 December 2011 12:56:07 Nigel Stewart wrote:
> > I had been thinking about the Trinity/KWin relationship for quite some
> > time
> > and todays triaging showed me that this just does not make sense. I do
> > understand that you want to provide a KDE 3.5 desktop experience. This is
> > great and I am all for it. But KWin 4 is a clear continuation of KWin 3.
> > It is not a rewrite like other parts of the desktop. It is the same
> > application, with more features, less bugs and in general a better
> > performance.
> Hi Martin,
> What you're proposing makes sense, on the face of it.  And I ask these
> question not as a troll or flame - and not from the perspective of really
> knowing what the KWin component is responsible for:
> Is the binary size and performance (desktop latency) going to be
> comparable?
> Does it drag in other KDE 4 dependencies?
Obviously it depends on kdelibs and kde-runtime like any KDE application. The 
dependencies will of course be better once frameworks 5 are released.

Considering the impact on a running environment I would say that all depends 
whether your users are using any KDE 4 applications or none. I would be 
surprised if your users would use no KDE 4 applications. So I think it is 

> - Nigel