summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING15
1 files changed, 15 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 864b1880..013a386c 100644
--- a/HACKING
+++ b/HACKING
@@ -8,8 +8,19 @@ It runs metacity in an Xnest. e.g.:
CLIENTS=3 ./run-metacity.sh
or
DEBUG=memprof ./run-metacity.sh
+or
+ DEBUG_TEST=1 ./run-metacity-sh
or whatever.
+The tool metacity-message can be used as follows:
+ metacity-message reload-theme
+ metacity-message restart
+ metacity-message enable-keybindings
+ metacity-message disable-keybindings
+
+metacity-window-demo is good for trying behavior of various kinds of window
+without launching a full desktop.
+
src/window.c is where all the guts of the window manager live. This is
basically the only remotely scary file.
@@ -29,6 +40,10 @@ display.h or window.h or other core files.
Files in the core (display.[hc], window.[hc]) are not supposed to
include gdk.h or gtk.h.
+src/theme.c and src/theme-parser.c have the theme system; this is
+well-modularized from the rest of the code, since the theme viewer app
+links to these files in addition to the WM itself.
+
When hacking, remember that you can have multiple screens. The code is
also written to support multiple displays, but this is useless, since
you can just run two copies of the WM. Also, an XKillClient() or