Add guided tour

Very special thanks to Bill Nance for updating the information.
2025-12-17 19:20:17 +01:00 · 2013-02-07 00:30:13 +00:00
parent be2237cf3c
commit 9890479222
62 changed files with 2086 additions and 11 deletions
--- a/docs.php
+++ b/docs.php
@@ -32,9 +32,20 @@
          overlook this information, leading them to frustration and a bad first impression. Please take a moment to peruse the
          sections below, which should make the experience of learning Window Maker a more pleasant one.</p>
 	<ul>
            <li><a href="installation.php">Installation Basics</a></li>
            <li><a href="guidedtour/index.html">Guided Tour</a></li>
            <li><a href="guide_toc.php">User Guide</a></li>
 <!--            <li><a href="desktop.php">Desktop/X Integration</a></li> -->
            <li><a href="FAQ.php">FAQ</a></li>
            <li><a href="wings.php">WINGs</a></li>
          </ul>
 	<h3>Very frequently asked question </h3>
 	<div align="center"><img src="essential_dockapps.png" alt="Essential dockapps" width="66" height="135" /><div>wmvolman and wmsystemtray with nm-applet</div></div>
 	<h2> Can I easily mount my external drives or connect to the internet with Window Maker?</h2>
 	<p> Yes, you can. Mounting external media is not the problem of a window manager to solve, but
@@ -44,19 +55,11 @@
 	having your external media mounted on /media/VOLUME_LABEL.</p>
       	<p> And you can just as easily manage your network connections using the standard <code>nm-applet</code> running
-	in a system tray on your dock. See for example the excellent <a href="http://dockapps.windowmaker.org/file.php/id/355">wmsystemtray</a>.</p>
+	in a system tray like <a href="http://dockapps.windowmaker.org/file.php/id/355">wmsystemtray</a> on your dock.</p>
-          <ul>
+	<div align="center"><img src="essential_dockapps.png" alt="Essential dockapps" width="66" height="135" /><div>wmvolman and wmsystemtray with nm-applet</div></div>
            <li><a href="installation.php">Installation Basics</a></li>
            <li><a href="http://main.linuxfocus.org/~georges.t/">Guided Tour</a></li>
            <li><a href="guide_toc.php">User Guide</a></li>
 <!--            <li><a href="desktop.php">Desktop/X Integration</a></li> -->
            <li><a href="FAQ.php">FAQ</a></li>
            <li><a href="wings.php">WINGs</a></li>
          </ul>
        </td>
      </tr>
    </table>
--- a/guidedtour/back.html
+++ b/guidedtour/back.html
@@ -0,0 +1,164 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head>
  <title>Window Maker - Backgrounds</title>
  <link href="title.css" rel="stylesheet" type="text/css">
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 </head>
 <strong> </strong><strong> </strong>
 <h1><strong>
 <center>Backgrounds and Themes</center>
 </strong></h1>
 <strong></strong>
 <center><a href="index.html">Back to index</a></center>
 <ul>
  <li><a href="back.html#backg" name="backg">Backgrounds</a></li>
  <li><a href="back.html#style" name="style"></a><a href="#style">Styles</a></li>
  <li><a href="back.html#them" name="them">Themes</a></li>
 </ul>
 For the purposes of this guided tour, only those appearance options that
 are built-in to Window Maker will be considered. Crafting custom styles
 and themes is not terribly difficult, nor do you need any special
 knowledge of programming languages or other specialized skills, but
 this is outside the intended scope of the guided tour.<br>
 <br>
 The appearance of the Window Maker GUI can easily be customized from
 the applications menu item "Appearance."<br>
 Themes, styles, icon sets, and backgrounds can be selected as soon as
 they are installed in the right directory.
 <br>
 Themes should be installed in the directory
 ~/GNUstep/Library/WindowMaker/Themes/<br>
 Styles should be installed in the directory
 ~/GNUstep/Library/WindowMaker/Styles/<br>
 Backgrounds should be installed in the directory
 ~/GNUstep/Library/WindowMaker/Backgrounds/<br>
 <br>
 If you are working within a freshly-installed instance of Window Maker,
 your Linux distribution probably provided some default themes, styles
 and backgrounds. Rarely, a distribution
 provides no additional themes, styles or backgrounds - expecting users
 to provide these on their own.<br>
 <br>
 Here is the "Appearance" menu and some of its associated sub-menus,
 including themes, styles and backgrounds:<br>
 <br>
 <div style="text-align: center;"><img style="width: 714px; height: 636px;" alt="Appearance menu items" src="images/appearancemenu.png"><br>
 </div>
 <br>
 In the screenshot above, most of the styles are default to the Debian
 GNU/Linux distribution, while most of the themes were user-installed.
 Many themes are available for download on the internet.&nbsp; <br>
 <h2><a name="backg">Backgrounds</a></h2>
 <p>Backgrounds may be system-generated solid or gradient colors, or
 they may be images from user or distibution-supplied image files. The
 easiest way to change a system-generated background color or color
 gradient is to select one from the "Appearance -&gt; Background -&gt; <span style="color: rgb(255, 204, 102);">&lt; Solid <span style="color: white;">or</span> Gradient &gt;</span>" menu. In most default configurations there will be six to eight selections in each category.</p>
 <p>Likewise, the easiest way to change to a background image is to
 select one from the "Appearance -&gt; Background -&gt; Images" menu. If
 you wish to install your own images for use as backgrounds, place the
 image file in your ~/GNUstep/Library/WindowMaker/Backgrounds/ directory
 and they will be available from the menu immediately.</p>
 <p> </p>
 <h2><a name="Styles"></a>Styles</h2>
 A style defines the look of the key components of the Window Maker
 desktop. These components include the window titlebar and resizebar, the menu title and text field, and the icon background.<br>
 <br>
 The characteristics defined in a style (or theme) are&nbsp; the color
 and
 "texture" of key GUI elements. Texture in this context means using
 multiple colors in
 various color gradients - you are not limited to solid colors
 only.&nbsp; <br>
 <br>
 The easiest method for changing the style is to select a style from the
 "Appearance -&gt; Style" menu.<br>
 <br>
 A style may also be created using the <span style="font-style: italic;">Appearance
 Preferences</span> tool in <span style="font-style: italic;">WPrefs.app</span>.
 From this tool, you may configure the color and texture of window
 elements (titlebars, resizebars), menu elements (menu titlebar, menu
 item text colors, menu "style") and the color and texture of icon
 backgrounds. The location of titlebar text and the font and text color
 for window and menu text may also be configured here.<br>
 <br>
 <center><img style="width: 520px; height: 412px;" alt="Appearance preferences tool" src="images/prefs12.png"></center>
 <br>
 <br>
 More information on creating a style "from scratch" may be found <a href="http://windowmaker.org/chap4.php" target="_blank">in the Window Maker User's Guide.</a> (Scroll down to the section on "Appearance Options.") <br>
 <br>
 A step-by-step guide to crafting a custom style is available <a href="http://windowmakerandi.blogspot.com/search?updated-min=2011-01-01T00:00:00-06:00&amp;updated-max=2012-01-01T00:00:00-06:00&amp;max-results=4" target="_blank">HERE</a>.<br>
 <h2><a name="them">Themes</a></h2>
 <p>In its most basic form, a theme is simply a style that also
 includes a background. Some Linux distributions provide one or more
 default themes for use&nbsp; system-wide. You may
 install your own themes in the ~/GNUstep/Library/WindowMaker/Themes/
 directory. Themes installed in the correct directory will be
 available for selection in the "Appearance -&gt; Themes" menu.
 Selecting Themes from the Appearance menu runs the <span style="font-style: italic;">setstyle</span> program to install the
 theme and record it in the <span style="font-style: italic;">~/GNUstep/Defaults/WindowMaker</span>
 file.</p>
 Two sites
 providing preconfigured themes are <a href="http://lonelymachines.org/windowmaker-themes/" target="_blank">HERE</a>
 and <a href="http://www.jessanderson.org/wmthemes/" target="_blank">HERE</a>.
 An internet search for "Window Maker themes" will generate additional
 results, and you should also check your Linux distribution's
 repositories - some provide themes for installation using your
 distribution's package management system.
 <p>Themes may include images in png, jpg, xpm, and other supported image file
 formats for key elements of the GUI such as titlebars, icon
 backgrounds, and the workspace background. Themes that include images
 cannot be stored as a single text file, and therefore must be stored in a
 directory. A theme directory must contain all of the image files needed
 for the theme along with a file named "style." The style file in a
 theme directory will specify all of the GUI elements including any
 image files used for those elements in lieu of rgb color
 specifications. A theme directory must use the suffix ".themed" after
 the theme name. <br>
 </p>
 <p> </p>
 <center><a href="index.html">Back to index</a></center>
 </body></html>
--- a/guidedtour/clip.html
+++ b/guidedtour/clip.html
@@ -0,0 +1,157 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head><title>Window Maker - Clip</title>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <link href="title.css" rel="stylesheet" type="text/css"></head>
  <strong><big> </big></strong>
 <h1><strong>
 <center>CLIP</center>
 </strong></h1>
 <p>
 </p>
 <center><a href="index.html">Back to index</a><br>
 </center>
 <ul>
 </ul>
 <p>By default, The clip is represented by the icon on the top left of
 the screen containing a paperclip image.</p>
 <p style="text-align: center;"><img style="width: 64px; height: 64px;" alt="Clip icon" src="images/clip.png"><br>
 </p>
 <p>The clip's primary function is to serve as a workspace-specific
 dock. In
 other words, applications may be attached to the clip just as they are
 to the dock, but the clip and its associated applications are specific
 to each individual workspace - not available on all workspaces as they
 are on the dock.</p>
 <p>The clip's secondary function is to act as a "pager" - a utility for
 changing from one workspace to another (paging). The arrows at the top
 right and bottom left corners of the clip icon allow you to switch from
 one workspace to the next workspace (top right) or previous workspace
 (bottom left).
 </p>
 <p>The current workspace name (if any) and number are displayed on the
 clip. <br>
 </p>
 <p>The clip also has a number of menu-driven features.
 </p>
 <h2>Clip Menu</h2>
 <p>Right-clicking the clip displays a menu. </p>
 <center>
 <p><img src="images/clipm.jpg" alt="clip menu"> </p>
 </center>
 <h2>Clip Options<br>
 </h2>
 The first menu item allows you to select clip options. The following
 options are available:<br>
 <ul>
  <li><span style="font-style: italic;">Keep on top</span> - do not
 allow windows to cover the clip. <br>
  </li>
  <li><span style="font-style: italic;">Collapsed</span> - icons
 attached to the clip are hidden until you left-click the clip, which
 unhides them.</li>
  <li><span style="font-style: italic;">Autocollapse</span> - same as
 the previous option, except that mouseing over the clip unhides
 application icons.</li>
  <li><span style="font-style: italic;">Autoraise</span> - clicking an
 icon representing a
 window hidden under a larger window brings that window to the front.</li>
  <li><span style="font-style: italic;">Autoattract icons</span>
 - selecting this option attracts the icon of any application launched
 on the current workspace. Closing the application removes the icon from
 the clip.</li>
 </ul>
 <h2>Rename Workspace</h2>
 This item gives you to ability to name (or rename) the current
 workspace. <br>
 <br>
 Some users tend to group certain applications by workspace
 and like to name the workspace to indicate the nature of the
 applications on the clip. For example, a user might have a browser, an
 IRC client, and a file transfer application clipped on a workspace, and
 might name that workspace "internet" to indicate the workspace's
 primary function. The user might have a seperate workspace with a
 vector graphics application, an image manipulation application, and an
 image viewer on the clip, and might name that workspace "graphics."<br>
 <br>
 <h2>Other Options</h2>
 Right-clicking a clipped application's icon gives options specific to
 that application. <br>
 <ul>
  <li>You may make the application's icon <span style="font-style: italic;">omnipresent</span>
 (clipped on all workspaces). <br>
  </li>
  <li>You may <span style="font-style: italic;">select</span> one or all clipped icons. <br>
  </li>
  <li>You may <span style="font-style: italic;">move</span>
 one or all icons to a
 different workspace. <br>
  </li>
  <li>You may <span style="font-style: italic;">remove</span> the icon.</li>
  <li>You may instruct Window Maker to have all icons "<span style="font-style: italic;">attracted</span>" to
 the clip as soon as each application is launched, rather than placing them intially in the defined location on the display. </li>
 </ul>
 The remaining clip menu items are similar to those of the <a href="dock.html#conf" target="_blank">dock
 application icon menu</a>.
 As with the dock, clipped applications may be launched, hidden, or
 killed and their settings (icon used, application launch
 path/arguments, middle-click launch) may be
 modified. <br>
 <br>
 From version 0.80.0 on, the clip can "steal" appicons. This feature has
 nothing to
 do with autoattracting icons. When you start an application from somewhere
 other than either the clip or the dock (i.e., from the menu or a
 terminal), and the application is already either docked or clipped, a
 new application icon does not appear at the bottom
 of your
 screen. The icon that is already docked or clipped "steals" the icon
 function. As a
 result, the icon for the newly-launched application is the icon already on
 the
 clip or
 the dock. <br>
 <br>
 <center><a href="index.html">Back to index</a></center>
 </body></html>
--- a/guidedtour/dock.html
+++ b/guidedtour/dock.html
@@ -0,0 +1,189 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head><title>Window Maker - Dock</title>
  <link href="title.css" rel="stylesheet" type="text/css">
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
 <strong> </strong>
 <h1><strong>
 <center>DOCK</center>
 </strong></h1>
 <h2><strong></strong></h2>
 <strong></strong>
 <center><a href="index.html">Back to index</a></center>
 <ul>
  <li><a href="dock.html#what" name="what">Application dock</a></li>
  <li><a href="dock.html#start" name="start">Starting an application</a></li>
  <li><a href="dock.html#cust" name="cust">Customizing</a></li>
  <li><a href="dock.html#conf" name="conf">Configuring</a></li>
 </ul>
 <h2><a name="what">Application dock</a></h2>
 <p>The dock is the column of icons located by default on the right
 side of the screen.</p>
 <p>Any application can be attached to the dock. To do this, open an
 application then simply left-click-and-drag the application's icon to
 the last position on the dock. The dock will "attract" the icon and it
 will remain on the dock until removed by the user (left-click-and-drag
 the icon off the dock - it will disappear.) If you have saved your
 Window Maker session prior to logout (or set Window Maker to autosave
 your session upon logout) any icons you docked will automatically
 reappear at your next - and each subsequent - session.<br>
 </p>
 <p>The dock has it's own menu for user configuration.<br>
 </p>
 <p>The dock can be configured to remain on top of maximized windows. To
 do this, right-click on any docked icon then select "Keep on top" from
 the application icon menu. This will keep the entire dock visible
 (maximized windows will not be allowed to cover the dock). To allow the
 dock to be covered, uncheck the "Keep on top" item in the application
 icon menu.<br>
 </p>
 <p>The WMDock icon (by default, with the GNUstep logo) can be dragged
 sideways
 to switch the
 the entire dock from one side of the display to the other.<br>
 </p>
 <p>Dragging the WMDock icon downward will move the dock off the display
 with the
 exception of the WMDock icon itself, which will remain visible. To
 restore dock visibility, left-click-and-drag the dock back on screen.<br>
 </p>
 <h2><a name="start">Starting an application</a></h2>
 <p>Double-clicking the icon of a docked application starts the
 application. <br>
 </p>
 <p>An application that has not been launched normally has an elipsis
 (three dots) in the bottom-left-corner of the icon and appears in full
 color as shown below.&nbsp; <br>
 </p>
 <p style="text-align: center;"><img style="width: 62px; height: 62px;" alt="Unlaunched application icon" src="images/iconwithelipsis.png"><br>
 </p>
 <p>When the application is running, the elipsis disappears from the
 bottom-left-corner of the icon and the icon becomes "greyed out,"
 giving a visual cue that the application is already open. <br>
 </p>
 <p style="text-align: center;"><img style="width: 62px; height: 62px;" alt="Launched application icon" src="images/greyedouticon.png"><br>
 </p>
 <p>A docked icon that continues to show an elipsis and remains "full
 color" even after an instance of the
 application is running indicates that the application's settings have
 been modified to allow multiple launches from one docked icon. To do
 this you must open the application and modify the
 "application specific" settings in the <a href="win.html#menu">"commands
 menu"</a> of the application to allow
 "shared application icons."</p>
 <p>Using the "launch" command in the "application icon menu" for the
 icon is another way to start an application from the dock.<br>
 <br>
 From version 0.80.0 on, the dock can "steal" appicons. This feature has
 nothing to
 do with Autoattract Icons. When you start an application from somewhere
 else
 than either the clip or the dock (menu or terminal), and the appicon
 exists in
 one of them (clip or dock), this appicon doesn't appear at the bottom
 of your
 screen. The appicon existing in the clip or the dock "stole" it. As a
 result, the
 appicon is the same as the one used to start the application from the
 clip or
 the dock. </p>
 <p> </p>
 <h2><a name="cust">Customizing</a></h2>
 <p>Left-clicking and dragging an application icon to the dock adds this
 application to the dock. Obviously, this means the application is
 running! <br>
 </p>
 <p><span style="font-style: italic;">Miniwindows</span> (windows of
 minimized applications) cannot be docked. The small titlebar on the
 miniwindow differentiates it from an application's icon. <br>
 </p>
 <p>Dragging an icon off the dock removes the docked application.&nbsp; <br>
 </p>
 <p> </p>
 <h2><a name="conf">Configuring</a></h2>
 <p>There is a dock menu for each icon. Right-clicking the icon displays
 the "application icon menu." Select the "Settings..." option to
 configure the application.&nbsp;</p>
 <center>
 <p><a href="images/docks.jpg"><img src="images/docks.jpg" alt="dock"></a></p>
 </center>
 <p>The application's <span style="font-style: italic;">path</span> and
 its arguments, the command for middle-click launch, and the icon
 employed can
 be changed in this panel.<br>
 </p>
 <p>Shell commands such as redirection cannot be used in the command
 field. <br>
 </p>
 <p>The desired icon must be in one of the directories displayed
 in the panel while browsing. New directories can be added from the <a href="prefs.html#search">Search path preferences</a><br>
 </p>
 <p> A checkbox allows you to start the application when Window Maker is
 first started. (Note: <span style="font-style: italic;">You want to be
 careful with this</span>. If you have, for example, your terminal
 emulator, your file manager, and your browser set to start when Window
 Maker is started you'll get an open terminal, an open file manager and
 an open browser <span style="font-style: italic;">every time</span>
 you start a session! Normally you will only want to start certain
 dockapps - "regular" applications like a terminal emulator or browser
 can be started <span style="font-style: italic;">after</span> your
 session is up and going.)<br>
 </p>
 <p>From version 0.62.0 on, a checkbox can be used to prevent accidental
 removal from the dock. <br>
 <br>
 From version 0.70.0 on, a new field has been added for middle-click
 launch. Entering, for example, "firefox" into a docked
 application
 settings panel will launch the Firefox browser.<br>
 <br>
 </p>
 <p> </p>
 <center><a href="index.html">Back to index</a></center>
 </body></html>
--- a/guidedtour/images/GNUstep.jpg
+++ b/guidedtour/images/GNUstep.jpg
--- a/guidedtour/images/LogoGNUstep.png
+++ b/guidedtour/images/LogoGNUstep.png
--- a/guidedtour/images/apm.jpg
+++ b/guidedtour/images/apm.jpg
--- a/guidedtour/images/apm.png
+++ b/guidedtour/images/apm.png
--- a/guidedtour/images/appearancemenu.png
+++ b/guidedtour/images/appearancemenu.png
--- a/guidedtour/images/clip.png
+++ b/guidedtour/images/clip.png
--- a/guidedtour/images/clipm.jpg
+++ b/guidedtour/images/clipm.jpg
--- a/guidedtour/images/dde.png
+++ b/guidedtour/images/dde.png
--- a/guidedtour/images/den.png
+++ b/guidedtour/images/den.png
--- a/guidedtour/images/des.png
+++ b/guidedtour/images/des.png
--- a/guidedtour/images/dfr.png
+++ b/guidedtour/images/dfr.png
--- a/guidedtour/images/dockm.jpg
+++ b/guidedtour/images/dockm.jpg
--- a/guidedtour/images/dockm.png
+++ b/guidedtour/images/dockm.png
--- a/guidedtour/images/docks.jpg
+++ b/guidedtour/images/docks.jpg
--- a/guidedtour/images/gnustep_64.png
+++ b/guidedtour/images/gnustep_64.png
--- a/guidedtour/images/gnusteplogo.png
+++ b/guidedtour/images/gnusteplogo.png
--- a/guidedtour/images/gnusteplogo2.png
+++ b/guidedtour/images/gnusteplogo2.png
--- a/guidedtour/images/greyedouticon.png
+++ b/guidedtour/images/greyedouticon.png
--- a/guidedtour/images/header.png
+++ b/guidedtour/images/header.png
--- a/guidedtour/images/iconwithelipsis.png
+++ b/guidedtour/images/iconwithelipsis.png
--- a/guidedtour/images/panda.png
+++ b/guidedtour/images/panda.png
--- a/guidedtour/images/panda2.png
+++ b/guidedtour/images/panda2.png
--- a/guidedtour/images/panda3.png
+++ b/guidedtour/images/panda3.png
--- a/guidedtour/images/prefs1.png
+++ b/guidedtour/images/prefs1.png
--- a/guidedtour/images/prefs10.png
+++ b/guidedtour/images/prefs10.png
--- a/guidedtour/images/prefs11.png
+++ b/guidedtour/images/prefs11.png
--- a/guidedtour/images/prefs12.png
+++ b/guidedtour/images/prefs12.png
--- a/guidedtour/images/prefs13.png
+++ b/guidedtour/images/prefs13.png
--- a/guidedtour/images/prefs14.png
+++ b/guidedtour/images/prefs14.png
--- a/guidedtour/images/prefs2.png
+++ b/guidedtour/images/prefs2.png
--- a/guidedtour/images/prefs3.png
+++ b/guidedtour/images/prefs3.png
--- a/guidedtour/images/prefs4.png
+++ b/guidedtour/images/prefs4.png
--- a/guidedtour/images/prefs5.png
+++ b/guidedtour/images/prefs5.png
--- a/guidedtour/images/prefs6.png
+++ b/guidedtour/images/prefs6.png
--- a/guidedtour/images/prefs7.png
+++ b/guidedtour/images/prefs7.png
--- a/guidedtour/images/prefs8.png
+++ b/guidedtour/images/prefs8.png
--- a/guidedtour/images/prefs9.png
+++ b/guidedtour/images/prefs9.png
--- a/guidedtour/images/shadew.jpg
+++ b/guidedtour/images/shadew.jpg
--- a/guidedtour/images/wadvopt.jpg
+++ b/guidedtour/images/wadvopt.jpg
--- a/guidedtour/images/wapspec.jpg
+++ b/guidedtour/images/wapspec.jpg
--- a/guidedtour/images/watt.jpg
+++ b/guidedtour/images/watt.jpg
--- a/guidedtour/images/wicon.jpg
+++ b/guidedtour/images/wicon.jpg
--- a/guidedtour/images/wksm.jpg
+++ b/guidedtour/images/wksm.jpg
--- a/guidedtour/images/wksm.png
+++ b/guidedtour/images/wksm.png
--- a/guidedtour/images/wl.jpg
+++ b/guidedtour/images/wl.jpg
--- a/guidedtour/images/wlm.jpg
+++ b/guidedtour/images/wlm.jpg
--- a/guidedtour/images/wlm.png
+++ b/guidedtour/images/wlm.png
--- a/guidedtour/images/wmakercomponents.png
+++ b/guidedtour/images/wmakercomponents.png
--- a/guidedtour/images/wmakerconf.png
+++ b/guidedtour/images/wmakerconf.png
--- a/guidedtour/images/wprefs.jpg
+++ b/guidedtour/images/wprefs.jpg
--- a/guidedtour/images/wspec.jpg
+++ b/guidedtour/images/wspec.jpg
--- a/guidedtour/index.html
+++ b/guidedtour/index.html
@@ -0,0 +1,129 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
 <html><head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <meta name="keywords" content="WindowMaker,windowmaker,window manager,Window Maker"><title>WindowMaker Guided tour - Index</title>
  <link href="title.css" rel="stylesheet" type="text/css"></head>
 <h1 align="center"><strong><big>Window Maker</big></strong></h1>
 <h2 align="center">Guided Tour</h2>
 <p>
 </p>
 <center><img src="images/gnusteplogo.png" alt="Amanda by Agnieszka Czajkowska" height="100" width="100"></center>
 <p>
 </p>
 <center>
 <h3><a href="http://www.windowmaker.org/">Window Maker</a></h3>
 </center>
 <h2><strong>Foreword</strong></h2>
 This tutorial is intended to help Window Maker users gain knowledge
 about the many excellent features
 of this window manager.&nbsp; The official Users Guide is worth reading. It can
 be reached from the <a href="http://windowmaker.org/guide_toc.php">Window
 Maker site</a>.&nbsp;
 Other guides, tutorials and tips can be found at various sites on the
 internet.&nbsp; An
 internet search for "Window Maker guide how-to" might provide
 additional worthwhile information. <br>
 <br>
 This guided tour is NOT supposed to be a README, INSTALL or FAQ . These
 are worth reading, or more accurately, they should be considered COMPULSORY reading.
 <br>
 <br>
 The information in the guided tour is based upon Window Maker version 0.95.3.
 Check your version by opening WPrefs.app (the Window Maker Preferences
 tool). The version number is shown in the initial WPrefs window just
 below the "Window Maker Preferences" title. You may also run the
 command "<span style="font-style: italic;">wmaker --version</span>" in
 a terminal (without the quotation marks). This command returns the installed version number of Window Maker.
 <br>
 <h2><strong>A special word of thanks</strong></h2>
 The original Window Maker Guided Tour site was created and maintained
 for many years by Georges Tarbouriech. Where possible, I have retained
 his original work - including the layout and structure of the pages,
 the descriptions of Window Maker features,
 and even some of his original graphics. I want these pages to be up-to-date,
 but I also want them to be (as much as possible) a continuation
 of Georges' work. <span style="font-style: italic;">Thank you, Georges</span>.
 (Having said that, anything you
 find in error is without question my fault - so don't blame Georges
 for any mistakes!)
 If you find an error, have a suggestion, or wish to make a comment, you may contact me by email at <span style="font-style: italic;">bnance&lt;atsigngoeshere&gt;uu.edu</span>.<br>
 <br>
 This tour will attempt to follow Window Maker development, but not
 every update can be taken into account.&nbsp; In other words, this
 tour can help you learn the basics, but does not pretend to provide all
 of the detail or all of the latest information available in the
 official README, INSTALL and FAQ documents provided by Window Maker
 developers and maintainers.<br>
 <h2><strong>Table of contents</strong></h2>
 <ul>
  <li><a href="prefs.html">Preferences</a><a href="prefs.html"><br>
    </a></li>
  <li><a href="win.html">Windows</a></li>
  <li><a href="menu.html">Menus</a></li>
  <li><a href="dock.html">Dock</a></li>
  <li><a href="clip.html">Clip</a></li>
  <li><a href="back.html">Backgrounds and themes</a></li>
  <li><a href="misc.html">Miscellaneous</a></li>
  <li><a href="news.html">News</a></li>
 </ul>
 <p>
 </p>
 <h2><strong>Archives</strong></h2>
 <p>
 </p>
 <p>
 Two archives are available: HTML and pictures.
 <br>
 <a href="tut.tar.gz">tut.tar.gz (12K) HTML files</a> <br>
 <a href="img.tar.gz">img.tar.gz (613K) Picture files</a> </p>
 <p>
 </p>
 <h2><strong>Links of interest</strong></h2><a href="https://www.youtube.com/watch?v=dIkbxMbhBpc" target="_blank">Window Maker on Debian 6 (YouTube)</a> by fourandnine<br>
 <a href="https://wiki.archlinux.org/index.php/Window_Maker" target="_blank">Arch Linux Window Maker Wiki Entry</a><br>
 <a href="http://packages.debian.org/squeeze/wmaker">Debian Stable (Squeeze) Package Listing</a><br>
 <a href="http://www.youtube.com/watch?v=T7VFjW8p9NU" target="_blank">Window Maker on Mageia Linux (YouTube)</a> by St. Louis Mageia Users' Group<br>
 <br>
 <p>
 </p>
 <center><a href="http://www.windowmaker.org"><strong><span class="">Window
 Maker</span></strong></a></center>
 <p>
 </p>
 </body></html>
--- a/guidedtour/menu.html
+++ b/guidedtour/menu.html
@@ -0,0 +1,196 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <meta name="keywords" content="WindowMaker,windowmaker,window manager,Window Maker">
  <title>WindowMaker Guided tour - Index</title>
  <link href="title.css" rel="stylesheet" type="text/css">
 </head>
 <h1>
 <center>Menus</center>
 </h1>
 <center><a href="index.html">Back
 to Index</a></center>
 <ul>
  <li><a href="#menu">Menu list</a></li>
  <li><a href="#root">Root window menu</a></li>
  <li><a href="#list">Window list menu</a></li>
  <li><a href="#wspace">Workspaces menu</a></li>
  <li><a href="#apps">Application icon menu</a></li>
 </ul>
 <h2><a id="menu">Menu list</a></h2>
 <p>Different menus are available within Window Maker:</p>
 <ul>
  <li>The root window menu or applications menu</li>
  <li>The window list menu</li>
  <li>The workspace menu</li>
  <li>The application icon menu<br>
  </li>
 </ul>
 <p>Menus provide a list of applications or commands for execution. They
 can be used to launch applications, to get information, to configure
 the workspace...<br>
 </p>
 <p>Menus are opened by right-clicking either in the "blank" area of the
 workspace or in a window's titlebar or in docked icons. The <em>window
 list menu</em> is the only one opened with the middle mouse button.
 With a two-button mouse, pressing both buttons at once usually does the
 trick. A number of keyboard shortcuts are provided. These shortcuts are
 indicated by the modifier key + letter shown to the right of a menu
 item.</p>
 <p>The keyboard can be used to open and move through some of the menus.
 For instance, the root menu can be opened using F12 (default setting).
 The Up and Down arrow keys can then be used to navigate through the
 menu or the Left and Right arrow keys to jump between parent menus and
 submenus. Hitting the <em>Enter</em> key executes the selected item.
 the <em>Escape</em> key closes the menu or stops menu traversal.</p>
 <p>Menus can be forced to remain open on the workspace by left-clicking
 the titlebar. This creates a <em>close</em> button on the titlebar.</p>
 <h2><a id="root">Root window menu</a></h2>
 <center><img style="width: 107px; height: 261px;" alt="Root window menu (applications menu)" src="images/apm.png"></center>
 <br>
 The root window menu or applications menu is opened by right-clicking
 on an empty area of the workspace or by hitting the pre-defined
 keyboard shortcut (default is F12). This menu launches applications,
 allows for the customization of the workspace (backgrounds, themes...),
 and the management of other workspace characteristics using standard X
 utilities (xprop, xfontsel, xcmap...).
 <p>The menu content is totally configurable, either using WPrefs.app or
 by editing the plain text menu file. Instructions on how to configure
 one or the other can be found in the WindowMaker directory of the
 distribution. To use WPrefs.app, menus must be in property list format
 (plmenu). A script is available to convert plain text menus to property
 list menus and it's called wm-oldmenu2new. </p>
 <h2><a id="list">Window list menu</a></h2>
 <center><img style="width: 265px; height: 141px;" alt="Window list menu" src="images/wlm.png"></center>
 <br>
 Middle-clicking an empty area of the workspace opens the window list
 menu. With a two-button mouse, clicking both buttons at once usually
 gives the same result. F11 is the default keyboard shorcut to open the
 window list menu.
 <p>This menu lists all windows - whether active or inactive - in every
 workspace. The workspace containing each window is indicated at the
 right of the window name. The current focused window is marked by a
 diamond sign to the left of the window's name. Clicking any window in
 the list focuses and raises the corresponding window and moves you to
 the workspace where it's located.</p>
 <h2><a id="wspace">Workspaces menu</a></h2>
 <center><img style="width: 101px; height: 121px;" alt="Workspaces menu" src="images/wksm.png"></center>
 <br>
 <br>
 The workspaces menu is part of the root menu (applications menu).
 This item has two options: <em>new</em> and <em>destroy last</em>.
 <p>The first option creates a new workspace and automatically switches
 you to it. </p>
 <p>The second option destroys the last workspace as soon as there are
 no windows opened in it.</p>
 <p>Each workspace has a corresponding item in this menu. The active
 workspace is indicated by a diamond to the left of the workspace name
 or number.</p>
 <p>Clicking a workspace entry switches from the current workspace to
 the selected workspace.</p>
 <p>To change the name of a workspace, first "stick" the menu by
 left-clicking the menu titlebar. Then <em>Ctrl + click</em> the menu
 item to make it editable and type in the new name. Hitting <em>Return</em>
 saves the new name, hitting <em>Escape</em> cancels the operation.</p>
 <p>Key bindings allow movement from one workspace to another. Usually <em>Meta
 + (number)</em>. The <span style="font-style: italic;">Meta</span> key
 is normally the "<span style="font-style: italic;">Alt</span>" key,
 while <em>(number)</em> represents a number
 key that corresponds to the workspace number. For instance 1 can be
 the default workspace (workspace 1), 2 the second workspace and so on.
 Thus,
 <span style="font-style: italic;">Meta + 2</span> switches to workspace
 2.</p>
 <p>These key bindings can be set (or changed) from the keyboard
 shortcut dialog in
 WPrefs.app. </p>
 <h2><a id="apps">Application icon menu</a></h2>
 <center><img style="width: 98px; height: 119px;" alt="Icon application menu" src="images/dockm.png"></center>
 <br>
 <br>
 Clicking an icon in the dock with the right mouse button brings a
 menu for modifying that icon's application. There are six options
 available in the application icon menu for docked applications. (Some
 applications will not have all six&nbsp; options available.&nbsp; If an
 option is not available, it will appear "greyed out" in the menu.) <br>
 <ol>
  <li>
    <p>Clicking "Keep on top" places a check-mark beside that option,
 which means that the icon will always be on "top" of
 opened windows. If "Keep on top" is unchecked, windows will be allowed
 to cover the icons in the dock. Selecting "Keep on top" for one icon
 automatically affects all of the items in the dock. You cannot keep
 just one docked icon on top of windows - it's all or nothing, one way
 or the other.<br>
    </p>
  </li>
  <li>
    <p>"Launch" opens the application without double-clicking the icon.</p>
  </li>
  <li>
    <p>"Bring here" unhides the application in the current workspace.</p>
  </li>
  <li>
    <p>"Hide" hides the application or unhides it if already hidden.
 Unhiding opens the application in the workspace where it is located.
 (This option may not work if the application has it's own hiding menu
 option.)</p>
  </li>
  <li>
    <p>"Settings" allows the modification of application path and
 arguments, the command line, and the icon used.</p>
  </li>
  <li>
    <p>"Kill" closes the application immediately and should only be
 used if absolutely necessary.</p>
  </li>
 </ol>
 <center><a href="index.html">Back
 to Index</a></center>
 </body></html>
--- a/guidedtour/misc.html
+++ b/guidedtour/misc.html
@@ -0,0 +1,91 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head>
  <strong><title>Window Maker - Miscellaneous</title>  
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <link href="title.css" rel="stylesheet" type="text/css">
  </strong></head>
 <h1><strong>
 <center>Miscellaneous</center>
 </strong></h1>
 <strong></strong>
 <center><a href="index.html">Back to index</a></center>
 <ul>
  <li><a href="misc.html#loc" name="loc">Localization</a></li>
  <li><a href="misc.html#font" name="font">Fonts</a></li>
  <li><a href="misc.html#util" name="util">Utilities</a></li>
 </ul>
 <h2><a name="loc">Localization</a></h2>
 As soon as Window Maker is compiled with some options and gettext
 installed, it
 is fully localizable. Check the INSTALL file. <br>
 However, localization of menus can be used without the LANG environment
 variable
 set. Using pl menu allows to get menus in any available language
 without setting
 this variable. <br>
 Why do such a "thing" instead of setting the localization the "right"
 way? <br>
 For some reasons users may want to keep the system default language
 instead of
 defining a new localization. One of the main reason is that most
 software doesn't
 exist in all languages. <br>
 <h2><a name="font">Fonts</a></h2>
 It's possible to change the fonts in Window Maker, editing the
 WindowMaker file
 or the WMGLOBAL file in ~/GNUstep/Defaults. <br>
 Once again the INSTALL file gives instructions on how to do it. <br>
 The specific file to edit varies according to the fonts to be changed. <br>
 The script <span style="font-style: italic;">wsetfont</span> is
 provided to do the job.
 <h2><a name="util">Utilities</a></h2>
 Window Maker provides the user with some useful utilities. <br>
 There is a README file concerning these scripts in the util directory. <br>
 Almost each script has it's own man page recommended reading. <br>
 These utilities mainly concern the GUI: icons, styles, fonts, menus,
 backgrounds. <br>
 A few of them deserve special interest as many users don't seem to know
 about them. <br>
 The <span style="font-style: italic;">wdwrite</span> script, for
 instance, writes data into the
 configuration
 files. <br>
 The <span style="font-style: italic;">setstyle</span> (or <span style="font-style: italic;">getstyle</span>) scripts are used to
 manage themes. <br>
 <span style="font-style: italic;">Wxcopy</span> and <span style="font-style: italic;">wxpaste</span> allows copying and pasting
 using the X cutbuffer. <br>
 The first one makes part of the default applications menu, in the
 selection
 item. <br>
 For KDE users, wkdemenu.pl is worth using. <br>
 From version 0.63.0 on, a new utility is available : <span style="font-style: italic;">wmagnify</span>. It allows magnification
 of the area under the mouse pointer.<br>
 <br>
 <center><a href="index.html">Back to index</a></center>
 </body></html>
--- a/guidedtour/news.html
+++ b/guidedtour/news.html
@@ -0,0 +1,178 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head><title>Window Maker - News</title>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <link href="title.css" rel="stylesheet" type="text/css"></head>
 <h1><strong>
 <center>News</center></strong></h1>
 <strong>
 </strong>
 <p>
 </p>
 <center><a href="index.html">Back to index</a></center>
 <p>
 <strong>This page has been added to allow easy discovery of the main
 changes from one
 version to another. The original text is drawn directly from the <a href="http://windowmaker.org/news.php" target="_blank">windowmaker.org site</a>.
 Moving forward, it is anticipated that additional comments and
 observations on Window Maker development news will be provided as well.</strong>
 </p>
 <h3>Version 0.95.4 released</h3>
 <p> Window Maker 0.95.4 was released on January 3rd 2013. There was a major code cleanup related to icons, some changes
 	      in WPrefs, the addition of a new "Center" placement strategy, support for _NET_FRAME_EXTENTS, the removal of CPP
 	      dependency to process menu files and small fixes and improvements all around.</p>
 <h3>Version 0.95.3 released</h3>
 <p> Window Maker 0.95.3 was released on May 16th 2012. This release fixes a regression
 	  which would cause more than one instance of an application to start (under some circunstances) when using menu
 	  shortcuts. The window maximization procedures now have a more intuitive behavior with respect to remembering
          the old geometry and going back to it. Furthermore, there are some other small fixes and cleanups.</p>
 <h3>Version 0.95.2 released</h3>
 <p> Window Maker 0.95.2 was released on February 14th 2012, and it contains just a few
 	  commits on top of 0.95.1. They were necessary to fix a few issues like 'make dist' not compiling.
 	  Furthermore a few more code cleanups slipped in.</p>
 <h3>Version 0.95.1 released</h3>
 <p>Window Maker 0.95.1 was released on January 29th 2012.</p>
 <p>The last official Window Maker release was version 0.92.0 from 2005, and version 0.95.1 contains many bug fixes and
          also a few new features.</p>
 <h3>New features and highlights</h3>
 <p>The following list is incomplete, but should give a first-order approximation to the new features in this release.
          For the truly curious among you, reading through <code>git log</code> is the only complete source of information.</p>
 <ul>
 <li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/6924454836b3a9432def2749f093ea060ac82e97">Left Half / Right
              Half Maximize</a>.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/cf62d1591f5aef1e6760a8c0881a6de97ae26e92">Maximus: tiled
              maximization</a>. Maximizes a window such that it occupies the largest area without overlapping others.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/a063338175511c4e6af211cef9f2c8a555d7cb44">New mouse-resizing
              functionality</a>. Windows can now be resized vertically (horizontally) using MOD+Wheel (CTRL+Wheel).</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/05720d97076ffc1569e50d904b998ec99c3d3d4e">History and TAB
              completion in dialogs</a>. To use this new functionality in your old WMRootMenu, replace %a by %A in the relevant
              entry. It will look like this <code>(Run..., SHEXEC, "%A(Run, Type command:)")</code>. Or use
              <code>wmgenmenu</code> to generate a new menu.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/a257e16593bb471662ce46f65d489c2ba6d87813">Bouncing appicon
              effect</a>.</p>
            </li><li>
              <p>New applications (<a href="http://repo.or.cz/w/wmaker-crm.git/commit/1861880239634774bf898175a3155b7c7cd9b59c">wmgenmenu</a> and wmmenugen)
              to generate the root menu automatically by looking which applications you have on your $PATH. Translations to
              German, <a href="http://repo.or.cz/w/wmaker-crm.git/commit/077a2eaa71623421eaffc234c30e6d40a52f0220">Spanish and
              French</a> of menus generated by wmgenmenu.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/56d856878743ec2d3b8d98ab6a0b61a6b2c99129">Automatic detection
              of configuration changes</a>. Linux users whose kernel supports the <a href="http://en.wikipedia.org/wiki/Inotify">inotify</a> mechanism have their configuration changes detected
              automatically without polling, reducing the number of CPU wakeups.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/9318a7f42870753bd6b8c306573936369aa819f4">Improved dockapp
              recognition.</a></p>
            </li><li>
              <p>And many trivial things which reduce little annoyances one might have. For example, an option was added to
              control whether or not Window Maker should do <a href="http://repo.or.cz/w/wmaker-crm.git/commit/d6c134f420bfa1cd6b6a9474d01548933b559901">automatic workspace
              switching</a> to satisfy a focus request from a window located in another workspace.</p>
            </li><li>
              <p>(For developers). The <a href="http://repo.or.cz/w/wmaker-crm.git/commit/442e3876c6e5a78c6ed385ec204647553f45c168">addition</a> of a debian/
              folder which allows the creation of a debian package for wmaker using the git sources.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/b6689a0108fd06ba4d7bf22b789b3de531c2ad70">Added keyboard
              shortcut to uncover/cover the dock</a>.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/18408fff93468c533bf4aef3ce6c9808b415adde">Mac OS X-style
              window cycling</a>.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/c201e1612c1798106ccc2f806669a90b0bbb7a19">Preliminary XRandR
              support</a> (needs a bit more work to be bug-free; not compiled in by default. Use --enable-xrandr if you want to
              test it).</p>
            </li>
 </ul>
 <h3>Bug fixes</h3>
 <p>Window Maker 0.92.0 was already very stable, but many bugs were fixed in this release. A <strong>very</strong>
          incomplete list is given below, and as time permits it will be updated (including links to the commits) in the future.
          But the message now is that if you don't like bugs, use version 0.95.1.</p>
 <ul>
 <li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/37829a7c60ca09eb47d4d82b00070f6f6c0fb277">Fix loading saved
              states on 64-bit systems</a></p>
            </li><li>
              <p>Fix to avoid a segfault when creating more than 81 workspaces, as reported on youtube <a href="http://www.youtube.com/watch?v=fkNJZvKwmhE">here</a>.</p>
            </li><li>
              <p><a href="http://repo.or.cz/w/wmaker-crm.git/commit/c91bb1ba1360006c568db37438779e525868cf17">Periodic focus
              bug</a>.</p>
            </li>
 </ul>
 <h3>Summary of changes</h3>
 <p>A lot of effort was put into cleaning up the code, with lots of code removal and tidying things up. The following
          output should give you an idea of the development in the last cycle:</p>
 <pre>git diff --shortstat wmaker-0.92.0+..wmaker-0.95.1<br> 592 files changed, 118361 insertions(+), 133342 deletions(-)<br>git diff --shortstat 688a56e8ab67b..wmaker-0.95.1<br> 566 files changed, 37676 insertions(+), 41817 deletions(-)<br></pre>
 The first shortstat is really everything, including the (huge) patch generated in this <a href="http://repo.or.cz/w/wmaker-crm.git/commit/688a56e8ab67b56550e2874d9d7423f0d435bfd9">commit</a> from 2009, which changed the old
 sources to the linux kernel coding style. The second shortstat contains the summary of development afterwards -- but included is
 the addition of a debian folder with files summing around ~20k lines. The full diffstat for the second command can be seen
 <a href="http://windowmaker.org/fulldiffstat.php">here</a>.
          <p>
 </p>
 <center><a href="index.html">Back to index</a></center>
 </body></html>
--- a/guidedtour/prefs.html
+++ b/guidedtour/prefs.html
@@ -0,0 +1,485 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head><title>Window Maker - Prefs</title>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <link href="title.css" rel="stylesheet" type="text/css"></head>
 <h1>
 <center>Preferences</center>
 </h1>
 <p>
 </p>
 <center><img style="width: 64px; height: 64px;" src="images/wprefs.jpg" alt="Amanda by Agnieszka Czajkowska"></center>
 <p>
 </p>
 <center><a href="index.html">Back
 to Index</a>
 <h2 style="text-align: left;">WPrefs.app</h2>
 </center>
 <p>WPrefs.app is the heart of the configuration process in Window Maker.</p>
 <p>Upon installing Window Maker and running it for the first time, the
 WPrefs icon is already docked. By default, it's the one with the
 GNUstep logo in the background and a few tools in the foreground
 (although your distibution may use the plain GNUstep icon or something
 enitrely different). Normally Linux distributions position WPrefs as
 the second or third icon in the
 Dock column by default, just above or below the terminal icon. <br>
 </p>
 <center>
 <p><img style="width: 64px; height: 64px;" alt="GNUstep Logo with Tools" src="images/wmakerconf.png" align="middle" hspace="20"><img style="width: 64px; height: 64px;" alt="GNUstep Logo" src="images/gnustep_64.png" align="middle" hspace="20"><br>
 </p>
 </center>
 <p>Double-clicking on this icon opens the WPrefs.app window.
 Across the top of the window there is a row of icons, each one
 corresponding to a group of settings options. There is a checkbox for
 balloon help on the bottom left of the WPrefs.app window. Most of the
 following is taken directly from the content of the ballon help dialogs.</p>
 <h2>Available preference settings</h2>
 <ul>
  <li><a href="#wplace">Window handling</a></li>
  <li><a href="#switch">Window Focus</a></li>
  <li><a href="#menu">Menu</a></li>
  <li><a href="#icon">Icon</a></li>
  <li><a href="#ergo">Ergonomy</a></li>
  <li><a href="#search">Search path</a></li>
  <li><a href="#worksp">Workspace</a></li>
  <li><a href="#other">Other</a></li>
  <li><a href="#appmenu">Applications menu</a></li>
  <li><a href="#keyb">Keyboard shortcut</a></li>
  <li><a href="#mouse">Mouse</a></li>
  <li><a href="#appear">Appearance</a></li>
  <li><a href="#exp">Expert user</a></li>
  <li><a href="#font">Font configuration</a></li>
  <li><a href="#edit">Editing the configuration file</a></li>
 </ul>
 <h2><a id="whand">Window handling</a></h2>
 <center><img style="width: 519px; height: 414px;" alt="WPrefs.app window handling preferences" src="images/prefs1.png"></center>
 <br>
 Clicking the second icon allows you to select the window handling
 options. Clicking on this icon opens a panel allowing you to define the
 default placement and properties of windows in the workspace.
 <ul>
  <li>
    <p><em>Window placement</em><br>
 You can use the sliders around the screen representation to modify the
 original placement.
 The gadget tells Window Maker how to order windows on the screen: <span style="font-style: italic;">Random</span>, <span style="font-style: italic;">Manual</span>, <span style="font-style: italic;">Cascade</span> or <span style="font-style: italic;">Smart</span>. <span style="font-style: italic;">Automatic</span> is the default.</p>
  </li>
  <li>
    <p><em>Edge resistance</em><br>
 To set the edge resistance and whether it resists or attracts windows.
 According to the selection, windows resist or attract when moved
 against other windows or the edges of the screen. The slider defines
 the threshold. Some applications' title bars may disappear
 at the top of the screen, with the window being too high for the screen
 area. Setting the edge
 resistance to "0" may solve this problem.</p>
  </li>
  <li>
    <p><em>Open dialogs in the same workspace as their owners</em><br>
 Obviously, whether to force dialog boxes "spawned" by an application to
 open in same workspace as their owners.</p>
  </li>
  <li>
    <p><em>Opaque move/resize</em><br>
 Clicking on <span style="font-style: italic;">opaque move</span>
 causes windows to be moved with their contents visible. If not checked,
 only the frame is displayed during the move. <span style="font-style: italic;">Opaque resize</span> makes window contents
 visible during resizing, otherwise only the frame is displayed.<br>
    </p>
  </li>
  <li>
    <p><em>When maximizing</em><br>
 This option allows the window to cover (or not) icons or the dock when
 maximizing. </p>
  </li>
 </ul>
 <h2><a id="switch">Window focus</a></h2>
 <center><img style="width: 519px; height: 411px;" alt="WPrefs.app window focus controls" src="images/prefs2.png"></center>
 <br>
 The first icon from the left-hand side controls the way windows get
 their focus (how they are activated).
 <ul>
  <li>
    <p><em>Input focus mode</em> (two choices are available): <br>
    <strong>Manual</strong> - click on the window to set keyboard input
 focus.<br>
    <strong>Auto</strong> - set keyboard input focus to the window
 under the mouse pointer.</p>
  </li>
  <li>
    <p><em>Install colormap in the window</em><br>
 Select either (a) install the colormap in the window that has the input
 focus or (b) that is under the mouse pointer.</p>
  </li>
  <li>
    <p><em>Automatic window raise delay</em><br>
 Setting the delay (in msec) for automatic window raising</p>
  </li>
  <li>
    <p><em>Checkboxes</em><br>
 The topmost check box prevents applications from receiving the focusing
 mouse-click (I don't know why you would use this, but some people
 obviously find it useful).&nbsp;
 The bottom checkbox allows you to choose whether newly-opened
 application windows automatically receive the focus, or must be clicked
 to gain focus. </p>
  </li>
 </ul>
 <h2><a id="menu">Menu</a></h2>
 <center><img style="width: 519px; height: 412px;" alt="WPrefs.app menu preferences" src="images/prefs3.png"></center>
 <br>
 This panel allows you to set menu scrolling speed and submenu
 alignment with the parent menu. In addition, two checkboxes are
 provided:
 <ul>
  <li>The topmost box forces submenus to open inside the screen instead
 of scrolling&nbsp; when they would otherwise be off-screen.<br>
  </li>
  <li>The middle box allows submenus to open off-screen, but causes
 off-screen menus to scroll when the mouse pointer is
 moved over them. This setting is also of value if you "tear off" a menu
 and leave it positioned on the desktop. In that case, you might wish to
 "park" the menu off-screen (with only the titlebar showing, for
 example) and have it reappear when you mouse over it. This is
 convenient in some workflows, as when you have multiple applications
 open and you are using the window list menu to switch between
 applications.</li>
  <li>The bottom box allows you to assign EMACS-like keybindings for
 the selection of menu items.<br>
  </li>
 </ul>
 <h2><a id="icon">Icon</a></h2>
 <center><img style="width: 516px; height: 410px;" alt="WPrefs.app icon preferences" src="images/prefs4.png"></center>
 <br>
 <br>
 <p>Set icon or miniwindow handling options.<br>
 </p>
 <ul>
  <li><em>Icon positioning</em><br>
 This area defines the initial placement of miniwindows or icons will be
 displayed: <span style="font-style: italic;">bottom, top, right, left</span>...<br>
  </li>
  <li>
    <p><em>Checkboxes</em><br>
 The topmost box enables/disables auto-arrangement of icons.&nbsp; The
 bottom box places miniwindows for opened applications on all existing
 workspaces (<span style="font-style: italic;">omnipresent</span>).</p>
  </li>
  <li>
    <p><em>Iconification animation</em><br>
 When an application's window is miniaturized, <span style="font-style: italic;">miniaturization animation style</span>
 offers four animation choices.</p>
  </li>
  <ul>
    <li>Shrinking/Zooming,<br>
    </li>
    <li>Spinning/Twisting,<br>
    </li>
    <li>3D Flipping, or<br>
    </li>
    <li>None </li>
  </ul>
  <li>
    <p><em>Icon size</em><br>
 Selects the size of the icons shown when a window is miniaturized and
 for application icons. Dockapp developers usually assume that tiles
 will be 64x64 pixels, so it's
 probably a good idea to leave it at that size, unless you know you
 won't be using dockapps.</p>
  </li>
 </ul>
 <h2><a id="ergo">Ergonomy</a></h2>
 <center><img style="width: 518px; height: 413px;" alt="WPrefs.app ergonomic settings" src="images/prefs5.png"></center>
 <br>
 Various types of information are defined in this panel.
 <ul>
  <li>
    <p><em>Size display</em> <br>
 Window Maker provides a box that informs you about the size of a window
 during resizing. You may choose to have this display (a) in the center
 of the screen, (b) the center of the screen, (c) the center of the
 resized window, (d) the side and bottom of the window as a technical
 drawing-like size display or (e) not at all.</p>
  </li>
  <li>
    <p><em>Position display</em><br>
 Same information as above but regarding the screen placement of a
 window while moving (no technical drawing-like option).<br>
    </p>
  </li>
  <li>
    <p><em>Workspace border</em><br>
 You can set a small border for the workspace. This allows you to easily
 access the clip (for instance) when windows are maximized.</p>
  </li>
  <li>
    <p><em>Show balloon text for</em><br>
 Selecting
 checkboxes displays balloon text for: incomplete window
 titles, miniwindow titles, application and dock icons, or internal
 help. This may be useful for new users but many people find having help
 balloons pop out all over the desktop gets annoying quickly. I use the <span style="font-style: italic;">incomplete window title</span> and the <span style="font-style: italic;">miniwindow title</span> options and none
 of the others.<br>
    </p>
  </li>
  <li>
    <p><em>Checkbox</em><br>
 The top check bos, if selected, raises a window when switching focus
 with the keyboard. The bottom box enables a keyboard language selection
 button on window titlebars (must have multiple keyboard maps/locales
 defined - this is handy if you are working in multiple languages in
 applications such as word processors, for example).<br>
    </p>
  </li>
 </ul>
 <h2><a id="search">Search Path</a></h2>
 <center><img style="width: 521px; height: 408px;" alt="WPrefs.app icon and pixmap search path settings" src="images/prefs6.png"></center>
 <br>
 This panel is used to add or delete directory paths to search for
 icons and pixmaps. These paths are used in the <span style="font-style: italic;">settings</span>
 dialogs for dockapps and docked application icons, so having a good,
 complete set of defined paths is important.&nbsp; This may require some
 manual intervention, especially upon initial setup, since some default
 paths will not be present on your system, while others not predefined
 will be present.&nbsp; Use the <span style="font-style: italic;">add</span>
 and <span style="font-style: italic;">remove</span> dialogs to
 configure according to what is actually available.<br>
 <h2><a id="worksp">Workspace</a></h2>
 <center><img style="width: 520px; height: 410px;" alt="WPrefs.app workspace preference settings" src="images/prefs7.png"></center>
 <br>
 This panel defines navigation features within the workspace.
 <ul>
  <li>
    <p><em>Workspace navigation</em><br>
 Selecting the first
 checkbox allows switching to the first workspace when
 switching past the last workspace and vice-versa. Selecting the second
 checkbox allows windows to be dragged from one workspace to another.
 Selecting the third checkbox
 cause a new workspace to be created when windows are dragged off the
 last existing workspace. A selection menu allows you to define where
 the workspace name&nbsp; is displayed each time you move from one
 workspace to another (or not to display the workspace name at all).</p>
  </li>
  <li>
    <p><em>Dock and clip</em><br>
 Enables / disables the dock and/or the clip. I have seen some
 interesting configurations using no dock but having the clip present.
 For users who prefer a bottom or top "panel" of application launchers,
 system monitors and other tools, this is a very valuable bit of
 flexibility.<br>
    </p>
  </li>
 </ul>
 <h2><a id="other">Other</a></h2>
 <center><img style="width: 516px; height: 413px;" alt="WPrefs.app other workspace configuration settings" src="images/prefs8.png"></center>
 <br>
 <br>
 <p>This panel sets icon slide speed, shade animation speed, smooth
 scaling and titlebar control (button) style. Animations and sound are
 also defined here.</p>
 <ul>
  <li>
    <p><em>Icon slide speed</em><br>
 Selecting the left icon gives the slowest result, selecting the right
 one gives the fastest.</p>
  </li>
  <li>
    <p><em>Shade animation speed</em><br>
 Same as icon slide</p>
  </li>
  <li>
    <p><em>Smooth scaling</em><br>
 If selected, neutralizes pixelization effect on background images. The
 side-effect is to slow down background image loading.</p>
  </li>
  <li>
    <p><em>Titlebar style</em><br>
 To choose a more or less "NeXTish" titlebar. (The top version is
 "newer," while the bottom left is ca. 1990 and the bottom right is ca.
 1988.)<br>
    </p>
  </li>
  <li>
    <p><em>Animations</em><br>
 Selecting the animations icon enables animations for window
 miniaturization, shading and so on.<br>
 Selecting
 the superfluous icon enables "ghosting" of dock (when moved -
 especially when moved from one side of the screen to the other) and
 explosion
 animation for icons you remove from the dock.<br>
    </p>
  </li>
  <li>
    <p><em>Dithering colormap for 8bpp</em><br>
 For 8-bit displays (anyone still have one of these?) this enables
 dithering and changes the number of colors to reserve either for
 applications or for Window Maker. The Default setting almost always
 gives the best result.</p>
  </li>
 </ul>
 <h2><a id="appmenu">Applications menu</a></h2>
 <center><img style="width: 517px; height: 413px;" alt="WPrefs.app application menu configuration" src="images/prefs9.png"></center>
 <br>
 <br>
 <p>In this panel the applications menu and the commands to launch each
 application can be defined. This panel has been changed in version
 0.63.and later. It now displays the actual menu thus allowing direct
 editing. This can be done only if the menu is in property list format.
 Menus in plain text format can't be edited in WPrefs. Check the README
 file in the Window Maker directory on how to use one or the other.</p>
 <h2><a id="keyb">Keyboard shortcut</a></h2>
 <center><img style="width: 518px; height: 412px;" alt="WPrefs.app keyboard shortcut settings" src="images/prefs10.png"></center>
 <br>
 Many actions in Window Maker have predefined keyboard shortcuts.
 These actions mainly concern windows and workspaces.
 Modifying, adding or removing shortcuts can be done in this panel.
 Defining a shortcut can be done interactively, capturing the key
 combination.
 <h2><a id="mouse">Mouse</a></h2>
 <center><img style="width: 520px; height: 413px;" alt="WPrefs.app mouse configuration" src="images/prefs11.png"></center>
 <br>
 This panel sets the mouse speed and double-click delay.
 Mouse button bindings can be defined and can be disabled or enabled.
 <p>The default setting binds the right mouse button to the applications
 menu, middle button to the window list menu and left button to window
 selection (focus). Of course, with a two button mouse, the middle
 button binding will not work. However, on some OSes pressing both
 buttons at once gives the same result as the one obtained with middle
 button.</p>
 <p>Starting from version 0.65 on, the mouse wheel can be used to switch
 workspaces. This is not default behavior and must be enabled here.</p>
 <p>The mouse grab modifier represents the keyboard shortcut to use for
 actions like dragging windows with the mouse or clicking inside the
 window. Mod1 (Alt) is the default.</p>
 <h2><a id="appear">Appearance</a></h2>
 <center><img style="width: 520px; height: 412px;" alt="WPrefs.app appearance settings" src="images/prefs12.png"></center>
 <br>
 In this panel, everything related to the appearance of the GUI (except
 the background color or image) can
 be configured. Windows, menus and icons can have their own background
 "texture," meaning color gradients of various types can be configured
 here. Texture, color, menu style, and title alignment can be fully
 customized.
 <h2><a id="exp">Expert user</a></h2>
 <center><img style="width: 519px; height: 411px;" alt="WPrefs.app expert user settings" src="images/prefs13.png"></center>
 <br>
 Using this panel implies some knowledge. Many options are available.
 Among these are:
 <ul>
  <li>Disabling miniwindows (useful when using with KDE and GNOME)</li>
  <li>Using (or not) xset</li>
  <li>Saving session on exit (highly recommended!)</li>
  <li>Using SaveUnder in different objects</li>
  <li>Using Win style cycling (added from version 0.63.0)</li>
  <li>Disabling confirmation panel for the kill command</li>
  <li>Disabling cycling colors highlighting of icons</li>
 </ul>
 <h2><a id="font">Font configuration</a></h2>
 <center><img style="width: 517px; height: 411px;" alt="Wprefs.app font configuration options" src="images/prefs14.png"></center>
 <br>
 This panel allows you to configure fonts for the window and menu
 titlebars, for the menu body text, and for the icon and clip
 text.&nbsp; In addition, a font may be defined for desktop messages.<br>
 <h2><a id="edit">Editing the configuration file</a></h2>
 <p>If needed, the defaults configuration file found in
 $(HOME)/GNUstep/Defaults/WindowMaker can be edited by hand. This file
 is a database with a property list syntax. When selecting an option in
 WPrefs.app, it's written down into this file. When modifying this
 defaults file, it's very important to follow the syntax.<br>
 </p>
 <center><a href="index.html">Back
 to Index</a>
 </center>
 </body></html>
--- a/guidedtour/title.css
+++ b/guidedtour/title.css
@@ -0,0 +1,106 @@
 body  {
 	color: #FFF;
 	font-size: 14pt;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 	background-color: #505075;
 	border-size: 2px;
 	margin-top: 0px;
 	margin-right: 12px;
 	margin-bottom: 0px;
 	margin-left: 12px;
 }
 .hpadding   {
 	color: #483d8b;
 	font-weight: normal;
 	font-size: 14px;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 	padding: 0px 10px
 }
 .textpadding    {
 	color: white;
 	font-size: 14px;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 	line-height: normal;
 	margin: 0;
 	padding: 0 10px
 }
 a        {
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 }
 table .inner {
 	margin-left: 1em;
 	width: 90%;
 }
 h1       {
 	color: #ebdeff;
 	font-size: 20pt;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 	font-style: italic;
 	font-weight: bold;
 	line-height: 22pt
 }
 h2       {
 	color: #ebdeff;
 	font-size: 18pt;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 	font-style: italic;
 	line-height: 20pt
 }
 h3        {
 	color: #e8fd00;
 	font-size: 14pt;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 	font-style: normal;
 	line-height: 16pt
 }
 h4       {
 	color: #FFF;
 	font-size: 12pt;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
 	font-style: normal;
 	font-weight: bolder;
 	line-height: 12pt
 }
 .caption {
 	font-size: 11pt;
 	font-family: "Trebuchet MS", Arial, Helvetica, sans-serif
 }
 a:hover, a:focus   {
 	text-decoration: underline;
 	font-style: italic;
 	color: #CCC;
 }
 a:link, a:visited, a:active {
 	text-decoration: underline;
 	color: #FFF;
 }
 img {
 	border: none;
 }
 #dock {
 	position: absolute; top: 100px; left: 5px;
 }
 #inhalt {
        position: absolute; top: 40px; left: 100px;
        min-width: 800px;
 }
 div.screenshot {
      height: 250px;
      border: none;
      float: left;
      margin: 5px;
   }
--- a/guidedtour/win.html
+++ b/guidedtour/win.html
@@ -0,0 +1,377 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <meta name="keywords" content="WindowMaker,windowmaker,window manager,Window Maker"><title>WindowMaker Guided tour - Index</title>
  <link href="title.css" rel="stylesheet" type="text/css"></head>
 <h1>
 <center>Windows</center>
 </h1>
 <center><a href="index.html">Back
 to Index</a>
 </center>
 <ul>
  <li><a href="#desc">Description</a></li>
  <li><a href="#focus">Focusing</a></li>
  <li><a href="#order">Reordering</a></li>
  <li><a href="#move">Moving</a></li>
  <li><a href="#max">Maximizing</a></li>
  <li><a href="#mini">Miniturizing</a></li>
  <li><a href="#size">Resizing</a></li>
  <li><a href="#shade">Shading</a></li>
  <li><a href="#hide">Hiding</a></li>
  <li><a href="#close">Closing</a></li>
  <li><a href="#menu">Commands menu</a></li>
 </ul>
 <h2><a id="desc">Description</a></h2>
 <p>General layout of a window:</p>
 <ul>
  <li>
    <p><em>Titlebar</em>: Gives the name of the application, document
 or window. It's color (usually) indicates the focus state (active or
 inactive window). I say (usually) because some styles and themes do not
 provide different colors for focused or unfocused windows - although
 this is rare (and, I might add, cruel!).</p>
  </li>
  <li>
    <p><em>Miniaturize button</em>:
 Clicking on the left button of the titlebar iconifies the window.</p>
  </li>
  <li>
    <p><em>Close button</em>:
 Clicking on the right button of the titlebar closes the window or kills
 the application.</p>
  </li>
  <li>
    <p><em>Resizebar</em>:
 The bottom part of the window. Dragging the resizebar with the mouse
 resizes the window.</p>
  </li>
  <li><em>Client area</em>:
 The window content. It can be an application, some text, a picture... </li>
 </ul>
 <h2><a id="focus">Focusing</a></h2>
 <p>A window can be in two states: focused or unfocused. The focused
 window is the active window, the one receiving keystrokes. It's
 titlebar has a differentiated color (usually!). Dialog windows or
 panels opened
 from a main window, automatically get the focus. As soon as they are
 closed, the main window gets the focus back.</p>
 <p>Two modes are available to focus a window:</p>
 <ul>
  <li>
    <p><em>Click to focus mode</em>: clicking on any part of the window
 activates it.</p>
  </li>
  <li>
    <p><em>Focus follows mouse mode</em>: moving the mouse pointer over
 the window activates it. </p>
  </li>
 </ul>
 <h2><a id="order">Reordering</a></h2>
 <p>Windows can overlap other windows, in which case some will hide all
 or part of others. Clicking on the titlebar or resizebar with the left
 mouse button brings a window to the "front" (gives that window focus).
 Selecting a window from the window list menu does the same.</p>
 <p>Some key bindings are provided and are very useful when a window is
 hidden behind others.</p>
 <ul>
  <li>
    <p><em>Meta key + click on the titlebar with left mouse button</em>-<br>
 sends the window to the back and gives focus to the topmost window.</p>
  </li>
  <li>
    <p><em>Meta key + click on the client area with left mouse button</em>-<br>
 brings the window to the front and focuses it.</p>
  </li>
  <li>
    <p><em>Meta key + Up Arrow key</em>-<br>
 brings the current focused window to the front.</p>
  </li>
  <li>
    <p><em>Meta key + Down Arrow key</em>-<br>
 sends the current focused window to the back.</p>
  </li>
 </ul>
 <p>Many window attributes can be modified from the attributes panel in
 the window commands menu (clicking the right mouse button on the
 titlebar). From version 0.62.0, window cycling was changed to Windows
 style (Alt-Tab).</p>
 <h2><a id="move">Moving</a></h2>
 <p>Clicking on the titlebar of a window and dragging it with the left
 mouse button pressed moves the window.
 The little box in the middle indicates the current position in pixels
 relative to the top left corner of the screen (+0 +0).
 Extra key bindings give more flexibility.
 - Dragging the titlebar with middle mouse button: moves the window
 without changing it's stacking order.
 - Dragging the titlebar + Ctrl key: moves the window without focusing
 it.
 - Dragging the client area or the resizebar + Meta key: moves the
 window.</p>
 <h2><a id="max">Maximizing</a></h2>
 <p>Double-clicking the titlebar while holding the Ctrl key resizes the
 window's height to full screen.</p>
 <p>Double-clicking the titlebar while holding the Shift key resizes the
 window's width to full screen.</p>
 <p>Double-clicking the titlebar while holding both Ctrl and Shift keys
 resizes the window's height and width to full screen.
 Double-clicking the titlebar while holding Ctrl or Shift key restores
 the initial size of the window.</p>
 <p>To prevent a maximized window from covering the dock, the "Keep on
 top" option must be selected from the dock menu.</p>
 <h2><a id="mini">Miniaturizing</a></h2>
 <p>Clicking the miniaturize button (the left one on the titlebar)
 shrinks the window into a miniwindow with an icon and a title and
 places it at the bottom of the screen. Hitting the assigned shortcut
 does the same. (Default is Meta + m.)</p>
 <p>The miniwindow is different from the application icon in that the
 miniwindow cannot be docked.</p>
 <p>Double-clicking in the miniwindow restores a miniaturized window.
 Double-clicking in an application icon with the middle mouse button
 restores all miniaturized and hidden windows of this application.</p>
 <h2><a id="size">Resizing</a></h2>
 <p>The resizebar, at the bottom of the window, is divided into three
 regions: left end region, middle region and right end region.</p>
 <p>Depending upon the region you click, the resize operation is
 constrained to one direction. </p>
 <p>Clicking in the middle region of the resizebar and dragging it
 vertically changes the window's height.</p>
 <p>Clicking in either the left or right region of the resizebar and
 dragging it horizontally changes the window's width. </p>
 <p>Dragging with Shift key pressed gives the same result. Clicking in
 either end region of the resizebar and dragging it diagonally changes
 both height and width.</p>
 <p>Key bindings give more options.</p>
 <ul>
  <li>
    <p>Dragging the window in the client area with the right mouse
 button + Meta key resizes the window.</p>
  </li>
  <li>
    <p>Dragging the resizebar with the middle mouse button resizes the
 window without bringing it to the front.</p>
  </li>
  <li>
    <p>Dragging the resizebar + Ctrl key resizes the window without
 focusing it.</p>
  </li>
 </ul>
 <h2><a id="shade">Shading</a></h2>
 <p>Double-clicking on the titlebar of a window shades it.
 This means the window rolls up to it's titlebar. A shaded window has
 almost the same properties as a normal window. It can be miniaturized
 or closed.</p>
 <p>From version 0.80.0, you can shade/unshade a window using a mouse
 wheel on its titlebar. This of course, assumes your system is able to
 manage a mouse wheel. The WMGLOBAL file in you $HOME/GNUstep/Defaults
 should contain two new directives : MouseWheelUp and MouseWheelDown.</p>
 <h2><a id="hide">Hiding</a></h2>
 <p>Clicking the the miniaturize button (the left one on the titlebar)
 with the right mouse button hides the application.
 Using the middle mouse button unhides the application, simultaneously
 opening the windows list menu and selecting the hidden application.
 (Pressing both buttons at once with a two buttons mouse does the same
 on some OSes.) If this doesn't work, use the F11 key binding (the
 default) to open the windows list menu.</p>
 <h2><a id="close">Closing</a></h2>
 <p>Clicking the close button (the right one on the titlebar) closes the
 window. When the close button has a different form (not an X), it means
 an application is running in that window.
 Double-clicking in this close button kills the application. This can be
 done too with <em>Ctrl key + clicking the close button</em>.</p>
 <p>Usually, it's much better to exit an application from inside
 (through it's menu, for instance).</p>
 <h2><a id="menu">Commands menu</a></h2>
 <p>Clicking on the titlebar of a window with the right mouse button
 opens a menu containing commands applying to this window. The keyboard
 shortcut Ctrl + Esc can replace the click on the titlebar. Esc closes
 this menu.</p>
 <p><strong>List of Commands Menu commands:</strong></p>
 <p><em>Maximize/Unmaximize</em>:<br>
 Either maximizes or returns the window to it's initial state.</p>
 <p><em>Miniaturize</em>:<br>
 Miniaturizes the window (miniwindow). The keyboard shortcut is Meta + m.</p>
 <p><em>Shade/Unshade</em>: Shades (or unshades) the window.</p>
 <p><em>Hide</em>:<br>
 Hides all windows of the application. Clicking on the application icon
 unhides the windows.</p>
 <p><em>Hide Others</em>:<br>
 From version 0.80.1 it is possible to hide all others windows. The
 window list menu allows to unhide selecting the window to redisplay.</p>
 <p><em>Resize/Move</em>:<br>
 When this menu option is selected, the window is ready to be moved or
 resized (the little box with coordinates is displayed inside the
 window). Clicking on the titlebar deselects the option.</p>
 <p><em>Select</em>:<br>
 Obviously selects the window which then can be moved or resized...
 Reselecting this option deselects the window.</p>
 <p><em>Move to</em>:<br>
 Allows to move the window to another workspace (if existing!).</p>
 <p><em>Attributes</em>:<br>
 Opens the attributes panel to edit attributes and options for the
 window.</p>
 <p>Five options are available in this panel: Window specification,
 Window attributes, Advanced options, Icon and initial workspace and
 application specific.</p>
 <ul>
  <li>Window specification: Defines that the configuration will apply
 to windows having their WM_CLASS property set to the selected name.
 This is because windows can have different names.
 From version 0.65.0, you can select the window to get the right
 specification.</li>
  <li>
    <p>Window attributes: selecting the corresponding checkbox allows
 to: </p>
    <ul>
      <li>disable titlebar</li>
      <li>disable resizebar</li>
      <li>disable close button</li>
      <li>disable miniaturize button</li>
      <li>disable border</li>
      <li>keep on top</li>
      <li>keep at bottom</li>
      <li>omnipresent</li>
      <li>start miniaturized</li>
      <li>start maximized</li>
      <li>full screen maximization</li>
    </ul>
  </li>
  <li>
    <p>Advanced options: selecting the corresponding checkbox allows
 to: </p>
    <ul>
      <li>don't bind keyboard shortcuts</li>
      <li>don't bind mouse clicks</li>
      <li>don't show in the window list</li>
      <li>don't let the window take focus</li>
      <li>keep inside screen</li>
      <li>ignore "Hide others"</li>
      <li>ignore "Save session"</li>
      <li>emulate application icon</li>
    </ul>
  </li>
  <li>
    <p>Icon and initial workspace: allow to </p>
    <ul>
      <li>choose an icon browsing directories</li>
      <li>ignore client supplied icon when selecting the checkbox</li>
      <li>define initial workspace</li>
    </ul>
  </li>
  <li>
    <p>Application specific: selecting checkboxes allows to:</p>
    <ul>
      <li>start hidden or with no application icon</li>
      <li>collapse application icons (from version 0.65.0)</li>
    </ul>
  </li>
  <li>
    <p>From version 0.80.0 a new checkbox is available : "Shared
 application icon". It replaces the "Collapse application icon"
 checkbox. That is, you can have many open windows from the same
 application with only one appicon. This feature is on by default except
 for some incompatible applications. This behavior can be defined for
 all windows in the Window Specification inspector selecting the
 Defaults for all windows checkbox.</p>
  </li>
 </ul>
 <p>You can revert to the old behavior changing SharedAppIcon to "No" in
 the WMWindowAttributes file, either in the global domain or in the
 local domain : $HOME/GNUstep/Defaults.</p>
 <p><em>Options</em>:</p>
 <p>Submenu options allow to:</p>
 <ul>
  <li>to keep the window on top</li>
  <li>to keep the window at bottom</li>
  <li>to keep the window omnipresent</li>
  <li>to set shortcuts for the window</li>
 </ul>
 <p>Ten shortcuts are available as soon as they have been set in the
 keyboard shortcut dialog. The shortcuts to define are those named
 "Shortcut for window + figure". Then, using the defined shortcut gives
 the focus to the window.</p>
 <p><em>Close</em>:<br>
 Closes the window</p>
 <p><em>Kill</em>:<br>
 Kills the application.
 Usually, an application must be closed from inside (menu or other
 means). This option is especially reserved for "emergency" cases.</p>
 </body></html>