Add some docs about the titlebar to wmii.pdf.

This commit is contained in:
Kris Maglione 2009-10-13 03:25:17 -04:00
parent 05cbfe09cf
commit 4090134905
8 changed files with 46 additions and 0 deletions

BIN
doc/floating.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 599 B

BIN
doc/focused.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 726 B

BIN
doc/managed.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 579 B

BIN
doc/selected.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 698 B

BIN
doc/unfocused.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 754 B

BIN
doc/unselected.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 787 B

Binary file not shown.

View File

@ -19,6 +19,9 @@
\let\primary=\textbf \let\primary=\textbf
\def\titlebar#1{%
\begin{center}\includegraphics[width=5.5in]{#1.png}\end{center}}
% Key specs % Key specs
\def\key#1{{\small$\langle$\addfontfeature{Numbers=Lining}#1\/$\rangle$}} \def\key#1{{\small$\langle$\addfontfeature{Numbers=Lining}#1\/$\rangle$}}
\let\<=< \let\<=<
@ -141,6 +144,9 @@ As noted, \wmii\ provides two management styles:
switching from an active to a collapsed window, the active switching from an active to a collapsed window, the active
window collapses, and the collapsed one effectively takes window collapses, and the collapsed one effectively takes
its place. its place.
Managed windows have an unadorned titlebar:
\titlebar{managed}
\item[Floating] Since some programs aren't designed in ways \item[Floating] Since some programs aren't designed in ways
conducive to the managed work flow, \wmii\ also provides the conducive to the managed work flow, \wmii\ also provides the
classic “floating” window management model. In this model, classic “floating” window management model. In this model,
@ -148,6 +154,9 @@ As noted, \wmii\ provides two management styles:
freely about. Other than automatic placement of new windows freely about. Other than automatic placement of new windows
and snapping of edges, \wmii\ doesn't manage floating and snapping of edges, \wmii\ doesn't manage floating
windows at all. windows at all.
Floating windows are indicated by a decorated titlebar:
\titlebar{floating}
\item[Fullscreen] Fullscreen mode is actually a subset of the \item[Fullscreen] Fullscreen mode is actually a subset of the
floating style. Windows may be toggled to and from floating style. Windows may be toggled to and from
fullscreen mode at will. When fullscreen, windows reside in fullscreen mode at will. When fullscreen, windows reside in
@ -445,6 +454,43 @@ you can click and drag as well. If that's still too hard a
target, try using <M-Mouse3>, which works anywhere and provides target, try using <M-Mouse3>, which works anywhere and provides
much richer functionality. much richer functionality.
\subsection{Window Focus and Selection}
For the purposes of keyboard navigation, \wmii\ keeps track of
which window is currently selected, and confers its titlebar a
different color scheme from the other windows. This window is
the basis of relative motion commands, such as “select the
window to the left”, and the target of commands such as “close
this window”. Normally, the selected window is the same as the
focused window, i.e., the window that recieves keyboard events.
Some applications, however, present strange corner cases.
\begin{description}
\item[Focused, selected window] This is the normal case of a
window which is both selected and has the keyboard focus.
\titlebar{selected}
\item[Unfocused, unselected window] This is the normal case for an
unselected window which does not have the keyboard focus.
\titlebar{unselected}
\item[Unfocused, selected window] This is the first unusual
case. This is the selected window, for the purposes of
keyboard navigation, but it does not recieve keyboard events.
A good example is an onscreen keyboard, which will recieve
mouse clicks and translate them to keyboard events, but
won't absorb those keyboard events itself. Other examples
include any window whilst another (such as \wimenu) has
grabbed the keyboard.
\titlebar{unfocused}
\item[Focused, unselected window] This is the second unusual
focus case. The window has the keyboard focus, but for the
purposes of keyboard navigation, it is not considered
selected. In the case of an onscreen keyboard, this is the
window which will receive the generated events. In the case
of a keyboard grab, the will likely be the window holding
the grab.
\titlebar{focused}
\end{description}
\section{Running Programs} \section{Running Programs}
You've already seen the convenient key binding to launch a You've already seen the convenient key binding to launch a