From 512f3d57335f852a32ffeecb8f2f2e198f7ee244 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lubo=C5=A1=20Lu=C5=88=C3=A1k?= Date: Fri, 14 Jul 2006 10:03:37 +0000 Subject: [PATCH] Some updates. svn path=/branches/work/kwin_composite/; revision=562201 --- HACKING | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/HACKING b/HACKING index e14a12e5ac..62b8618f02 100644 --- a/HACKING +++ b/HACKING @@ -4,8 +4,9 @@ Mailing list and bugzilla: The KWin mailing list is kwin@kde.org . It's rather low traffic. The bugs.kde.org product for KWin is 'kwin'. Currently the components are 'general' (KWin core), -'decorations' (decoration plugins), 'compatibility' (problems with non-KDE WMs/apps) and -'eyecandy' (transparency and similar effects). +'decorations' (decoration plugins), 'compatibility' (problems with non-KDE WMs/apps), +'eyecandy' (transparency and similar effects), 'xinerama' (problems with Xinerama) and +'multihead' (non-Xinerama multihead, without maintainer). There are also two kcontrol components 'kcmkwindecoration' and 'kcmkwinoptions' related to KWin's KControl modules. @@ -63,6 +64,11 @@ and attach to the running KWin instance from there, or launch it as 'DISPLAY=:0 Since KWin is such an important component of KDE, it is usually better to start another X for development. Note that XNest is quite buggy and is therefore not recommended to use. +Starting separate X for testing KWin: I myself use a separate user, login to a text console and run +"( X vt10 :1 -terminate &); sleep 5; DISPLAY=:1 xterm". This launches another X with DISPLAY=:1 +on virtual console 10 (Ctrl+Alt+F10) with xterm. Then it's normally possible to run just KWin +or whole KDE with startkde (in which case it's a good idea to disable xterm from session management +in KControl->KDE components->Session manager). Window manager spec: ====================