trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: Re: [trinity-devel] Re: Resolving the TWin/KWin Fork Issue

From: Martin Gräßlin <mgraesslin@...>
Date: Sun, 29 Apr 2012 21:11:27 +0200
On Sunday 29 April 2012 19:13:35 Slávek Banko wrote:
> On Sunday 29 of April 2012 18:42:34 Martin Gräßlin wrote:
> > The Trinity Desktop Environment is a fork of KDE 3.5. KDE 3.5 used as
> > desktop shell KDesktop and Kicker and as a window manager KWin. TWin is
> > the fork of this version of KWin. Obviously KWin is very well integrated
> > with the rest of the desktop environment (e.g. uses same toolkit) and
> > has been developed especially for the needs of this environment in
> > comparison to things like openbox which is actually a standalone window
> > manager and includes things you don't need. Using openbox will therefore
> > result in higher RAM consumption than using KWin.
> 
> So you said this very descriptive! KWin4 is tightly integrated with rest
> of desktop environment == KDE4 (uses the same toolkit, etc). And just as
> TWin is tightly integrated with rest of desktop environment == TDE (uses
> the same toolkit, etc). Each lives in a different environment. KWin is
> NOT integrated with TDE and includes things that we do not need. Using
> KWin4 means outside TQt3 still have QT4 tooklit == higher RAM consumption
> than using TWin.
ah yes I knew that this conclusion would be drawn but it is incorrect. You can 
easily see that when you closely follow what I have written about the 
relationship between KWin and TWin and the relationship between KWin and 
Plasma and the possibilities to trim down KWin.

Cheers
Martin

Attachments: