> no it doesn't. KWin provides the same level of integration to Trinity as it > has ever done, whether you call it KWin or TWin or FooBar doesn't change > the fact that it is afterall KWin. Just for the fun of it, I just searched > for the term "kicker" in KWin's source code and it still finds 11 > reference. > > So no, the question whether TWin or KWin is a completely different one to > whether TWin or openbox. 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? Nik