dwm-meillo

changeset 468:210a99f18657

some simplifications to intro in dwm.h
author arg@mmvi
date Tue, 19 Sep 2006 16:13:44 +0200
parents 8852d6a2270e
children a2cc7adf9d4d
files dwm.h
diffstat 1 files changed, 13 insertions(+), 13 deletions(-) [+]
line diff
     1.1 --- a/dwm.h	Sat Sep 16 11:21:01 2006 +0200
     1.2 +++ b/dwm.h	Tue Sep 19 16:13:44 2006 +0200
     1.3 @@ -4,32 +4,32 @@
     1.4   *
     1.5   * dynamic window manager is designed like any other X client as well. It is
     1.6   * driven through handling X events. In contrast to other X clients, a window
     1.7 - * manager like dwm selects for SubstructureRedirectMask on the root window, to
     1.8 - * receive events about window appearance and disappearance.  Only one X
     1.9 - * connection at a time is allowed to select for this event mask.
    1.10 + * manager selects for SubstructureRedirectMask on the root window, to receive
    1.11 + * events about window (dis-)appearance.  Only one X connection at a time is
    1.12 + * allowed to select for this event mask.
    1.13   *
    1.14 - * Calls to fetch an X event from the X event queue connection are blocking.
    1.15 - * Due reading status text from standard input, a select-driven main loop has
    1.16 - * been implemented which selects for reads on the X connection and
    1.17 - * STDIN_FILENO to handle all data smoothly and without busy-loop quirks. The
    1.18 - * event handlers of dwm are organized in an array which is accessed whenever a
    1.19 - * new event has been fetched. This allows event dispatching in O(1) time.
    1.20 + * Calls to fetch an X event from the event queue are blocking.  Due reading
    1.21 + * status text from standard input, a select-driven main loop has been
    1.22 + * implemented which selects for reads on the X connection and STDIN_FILENO to
    1.23 + * handle all data smoothly. The event handlers of dwm are organized in an
    1.24 + * array which is accessed whenever a new event has been fetched. This allows
    1.25 + * event dispatching in O(1) time.
    1.26   *
    1.27   * Each child of the root window is called a client, except windows which have
    1.28   * set the override_redirect flag.  Clients are organized in a global
    1.29   * doubly-linked client list, the focus history is remembered through a global
    1.30   * stack list. Each client contains an array of Bools of the same size as the
    1.31   * global tags array to indicate the tags of a client.  For each client dwm
    1.32 - * creates a small title window which is resized whenever the WM_NAME or
    1.33 - * _NET_WM_NAME properties are updated or the client is resized.
    1.34 + * creates a small title window, which is resized whenever the (_NET_)WM_NAME
    1.35 + * properties are updated or the client is moved/resized.
    1.36   *
    1.37   * Keys and tagging rules are organized as arrays and defined in the config.h
    1.38   * file. These arrays are kept static in event.o and tag.o respectively,
    1.39   * because no other part of dwm needs access to them.  The current mode is
    1.40 - * represented by the arrange function pointer which wether points to dofloat
    1.41 + * represented by the arrange function pointer, which wether points to dofloat
    1.42   * or dotile. 
    1.43   *
    1.44 - * To understand everything else, start with reading main.c:main().
    1.45 + * To understand everything else, start reading main.c:main().
    1.46   */
    1.47  
    1.48  #include "config.h"