On Monday 30 April 2012 14:39:10 Mag. Dr. Nikolaus Klepp wrote:
> > 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
> Ok, now I got that point. For those without fear - and running wheezy in a
> test environment:
> # apt-get install kde-window-manager
> $ export KDEWM=/usr/bin/kwin
> $ export WINDOWMANAGER=/opt/trinity/bin/startkde
> $ startx
> The window decorations are not the same, I got a light 1px border on my dark
> theme, although most of my setting is quoted.
probably a setting in the color scheme or compositing related.
> Side effects like semitransparent windows when moving
A configurable feature to use translucency when moving windows
> some strange behavour when moving a window to the screens top,
Quick Maximization and Quick Tiling on screen edges. That has everyone
nowadays :-) (Read e.g. the release announcment of today's XFCE release). And
of course it can be turned off
> but basicly it works. It's not as slugish as KDE4
> but clearly slower than twin.
no it isn't :-) I'm very sure about that. Please note that you used KWin with
enabled OpenGL Compositing while it is disabled with TWin. Depending on
hardware and driver that might result in a performance impact, though in
general nowadays driver issues are resolved.
> I am couriouse, if that works on other distos, too.
> Besides from the proof of principle, I still do not see why anybody would
> like to jettison twin.
> > 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?)
> Yes, but where's the point? twin works and is fast. Why change?
I outlined the reasons, please read them up. I'm not going to repeat them :-)