trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

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

From: Martin Gräßlin <mgraesslin@...>
Date: Mon, 30 Apr 2012 11:17:23 +0200
Am 30.04.2012 10:47, schrieb Slávek Banko:
> On Monday 30 of April 2012 10:26:21 Mag. Dr. Nikolaus Klepp wrote:
>> Sorry, I still don't get the point. What is the "integretion" you 
>> talk
>> about? Is there a testcase where you can show the advantage of kwin 
>> above
>> any other wm?
>> As I see it - from a users point of view - the only difference 
>> between twin
>> and any other wm is the configuration dialog. Is this valid for 
>> kwin, too?
>
> Exactly. The TWin advantages are obvious - the same toolkit (TQt3), 
> Twin
> settings are integrated with other TDE settings. The KWin not even 
> one of
> them. That is like any other window manager - it is a foreign 
> element.
guys, I have written this multiple times:
* KWin still includes exactly the same window decoration as the one 
used by TWin
* all your configuration dialogs are basically unchanged - you can 
continue to use them

I don't know how often I have to write it: TWin and KWin are the same 
window manager.

The only difference is that KWin uses Qt 4 which is not visible when 
configured correctly (we already discussed that in this thread, haven't 
we?)

Cheers
Martin