From: Carlos R. Mafra Date: Thu, 7 Feb 2013 00:30:13 +0000 (+0000) Subject: Add guided tour X-Git-Url: https://repo.or.cz/w/whome.git/commitdiff_plain/9890479222106ebe8fd0cb072560a59537295ddb Add guided tour Very special thanks to Bill Nance for updating the information. --- diff --git a/docs.php b/docs.php index 29949c4..5f9fd3b 100644 --- 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.

+ +

Very frequently asked question

-
Essential dockapps
wmvolman and wmsystemtray with nm-applet

Can I easily mount my external drives or connect to the internet with Window Maker?

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.

And you can just as easily manage your network connections using the standard nm-applet running - in a system tray on your dock. See for example the excellent wmsystemtray.

- - diff --git a/guidedtour/back.html b/guidedtour/back.html new file mode 100644 index 0000000..8cb0a75 --- /dev/null +++ b/guidedtour/back.html @@ -0,0 +1,164 @@ + + + Window Maker - Backgrounds + + + + + + + + + + +

+
Backgrounds and Themes
+

+ + +
Back to index
+ + + +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.
+ +
+ +The appearance of the Window Maker GUI can easily be customized from +the applications menu item "Appearance."
+ +Themes, styles, icon sets, and backgrounds can be selected as soon as +they are installed in the right directory. +
+ +Themes should be installed in the directory +~/GNUstep/Library/WindowMaker/Themes/
+ +Styles should be installed in the directory +~/GNUstep/Library/WindowMaker/Styles/
+ +Backgrounds should be installed in the directory +~/GNUstep/Library/WindowMaker/Backgrounds/
+ +
+ +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.
+ +
+ +Here is the "Appearance" menu and some of its associated sub-menus, +including themes, styles and backgrounds:
+ +
+ +
Appearance menu items
+
+ +
+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. 
+ +

Backgrounds

+ + +

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 -> Background -> < Solid or Gradient >" menu. In most default configurations there will be six to eight selections in each category.

+

Likewise, the easiest way to change to a background image is to +select one from the "Appearance -> Background -> 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.

+ +

+ +

Styles

+ +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.
+ +
+ +The characteristics defined in a style (or theme) are  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. 
+ +
+ +The easiest method for changing the style is to select a style from the +"Appearance -> Style" menu.
+ +
+ +A style may also be created using the Appearance +Preferences tool in WPrefs.app. +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.
+ +
+ +
Appearance preferences tool
+
+ +
+ +More information on creating a style "from scratch" may be found in the Window Maker User's Guide. (Scroll down to the section on "Appearance Options.")
+
+A step-by-step guide to crafting a custom style is available HERE.
+ +

Themes

+ +

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  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 -> Themes" menu. +Selecting Themes from the Appearance menu runs the setstyle program to install the +theme and record it in the ~/GNUstep/Defaults/WindowMaker +file.

+Two sites +providing preconfigured themes are HERE +and HERE. +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. +

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.
+

+ +

+ +
Back to index
+ + diff --git a/guidedtour/clip.html b/guidedtour/clip.html new file mode 100644 index 0000000..7bf5fc4 --- /dev/null +++ b/guidedtour/clip.html @@ -0,0 +1,157 @@ + +Window Maker - Clip + + + + + + + + + + +

+
CLIP
+

+ +

+

+ +
Back to index
+
+ + + +

By default, The clip is represented by the icon on the top left of +the screen containing a paperclip image.

+ +

Clip icon
+

+ +

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.

+ +

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). +

+ +

The current workspace name (if any) and number are displayed on the +clip.
+

+ +

The clip also has a number of menu-driven features. +

+ +

Clip Menu

+ +

Right-clicking the clip displays a menu.

+ +
+

clip menu

+
+ +

Clip Options
+ +

+ + +The first menu item allows you to select clip options. The following +options are available:
+ + + +

Rename Workspace

+ + +This item gives you to ability to name (or rename) the current +workspace.
+ +
+ +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."
+ +
+ +

Other Options

+ + +Right-clicking a clipped application's icon gives options specific to +that application.
+ + + +The remaining clip menu items are similar to those of the dock +application icon menu. +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.
+ +
+ +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.
+
+ +
Back to index
+ + diff --git a/guidedtour/dock.html b/guidedtour/dock.html new file mode 100644 index 0000000..f3e9051 --- /dev/null +++ b/guidedtour/dock.html @@ -0,0 +1,189 @@ + +Window Maker - Dock + + + + + + + + + + +

+
DOCK
+

+ +

+ + +
Back to index
+ + + +

Application dock

+ + +

The dock is the column of icons located by default on the right +side of the screen.

+ +

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.
+

+ +

The dock has it's own menu for user configuration.
+

+ +

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.
+

+ +

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.
+

+ +

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.
+

+ +

Starting an application

+ + +

Double-clicking the icon of a docked application starts the +application.
+

+ +

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. 
+

+ +

Unlaunched application icon
+

+ +

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.
+

+ +

Launched application icon
+

+ +

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 "commands +menu" of the application to allow +"shared application icons."

+ +

Using the "launch" command in the "application icon menu" for the +icon is another way to start an application from the dock.
+
+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.

+ +

+ +

Customizing

+ + +

Left-clicking and dragging an application icon to the dock adds this +application to the dock. Obviously, this means the application is +running!
+

+ +

Miniwindows (windows of +minimized applications) cannot be docked. The small titlebar on the +miniwindow differentiates it from an application's icon.
+

+ +

Dragging an icon off the dock removes the docked application. 
+

+ +

+ +

Configuring

+ + +

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. 

+ +
+

dock

+
+ +

The application's path and +its arguments, the command for middle-click launch, and the icon +employed can +be changed in this panel.
+

+ +

Shell commands such as redirection cannot be used in the command +field.
+

+ +

The desired icon must be in one of the directories displayed +in the panel while browsing. New directories can be added from the Search path preferences
+

+ +

A checkbox allows you to start the application when Window Maker is +first started. (Note: You want to be +careful with this. 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 every time +you start a session! Normally you will only want to start certain +dockapps - "regular" applications like a terminal emulator or browser +can be started after your +session is up and going.)
+

+ +

From version 0.62.0 on, a checkbox can be used to prevent accidental +removal from the dock.
+
+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.
+
+

+ +

+ +
Back to index
+ + diff --git a/guidedtour/images/GNUstep.jpg b/guidedtour/images/GNUstep.jpg new file mode 100644 index 0000000..e4d453e Binary files /dev/null and b/guidedtour/images/GNUstep.jpg differ diff --git a/guidedtour/images/LogoGNUstep.png b/guidedtour/images/LogoGNUstep.png new file mode 100644 index 0000000..3e4ec30 Binary files /dev/null and b/guidedtour/images/LogoGNUstep.png differ diff --git a/guidedtour/images/apm.jpg b/guidedtour/images/apm.jpg new file mode 100644 index 0000000..102b409 Binary files /dev/null and b/guidedtour/images/apm.jpg differ diff --git a/guidedtour/images/apm.png b/guidedtour/images/apm.png new file mode 100644 index 0000000..ca18f96 Binary files /dev/null and b/guidedtour/images/apm.png differ diff --git a/guidedtour/images/appearancemenu.png b/guidedtour/images/appearancemenu.png new file mode 100644 index 0000000..a2a25ed Binary files /dev/null and b/guidedtour/images/appearancemenu.png differ diff --git a/guidedtour/images/clip.png b/guidedtour/images/clip.png new file mode 100644 index 0000000..68707e4 Binary files /dev/null and b/guidedtour/images/clip.png differ diff --git a/guidedtour/images/clipm.jpg b/guidedtour/images/clipm.jpg new file mode 100644 index 0000000..bc4350e Binary files /dev/null and b/guidedtour/images/clipm.jpg differ diff --git a/guidedtour/images/dde.png b/guidedtour/images/dde.png new file mode 100644 index 0000000..3b5f401 Binary files /dev/null and b/guidedtour/images/dde.png differ diff --git a/guidedtour/images/den.png b/guidedtour/images/den.png new file mode 100644 index 0000000..6180633 Binary files /dev/null and b/guidedtour/images/den.png differ diff --git a/guidedtour/images/des.png b/guidedtour/images/des.png new file mode 100644 index 0000000..23e5011 Binary files /dev/null and b/guidedtour/images/des.png differ diff --git a/guidedtour/images/dfr.png b/guidedtour/images/dfr.png new file mode 100644 index 0000000..17cfb34 Binary files /dev/null and b/guidedtour/images/dfr.png differ diff --git a/guidedtour/images/dockm.jpg b/guidedtour/images/dockm.jpg new file mode 100644 index 0000000..4a9da61 Binary files /dev/null and b/guidedtour/images/dockm.jpg differ diff --git a/guidedtour/images/dockm.png b/guidedtour/images/dockm.png new file mode 100644 index 0000000..dec0491 Binary files /dev/null and b/guidedtour/images/dockm.png differ diff --git a/guidedtour/images/docks.jpg b/guidedtour/images/docks.jpg new file mode 100644 index 0000000..079b522 Binary files /dev/null and b/guidedtour/images/docks.jpg differ diff --git a/guidedtour/images/gnustep_64.png b/guidedtour/images/gnustep_64.png new file mode 100644 index 0000000..3831057 Binary files /dev/null and b/guidedtour/images/gnustep_64.png differ diff --git a/guidedtour/images/gnusteplogo.png b/guidedtour/images/gnusteplogo.png new file mode 100644 index 0000000..7b9c86c Binary files /dev/null and b/guidedtour/images/gnusteplogo.png differ diff --git a/guidedtour/images/gnusteplogo2.png b/guidedtour/images/gnusteplogo2.png new file mode 100644 index 0000000..c309fd8 Binary files /dev/null and b/guidedtour/images/gnusteplogo2.png differ diff --git a/guidedtour/images/greyedouticon.png b/guidedtour/images/greyedouticon.png new file mode 100644 index 0000000..1389205 Binary files /dev/null and b/guidedtour/images/greyedouticon.png differ diff --git a/guidedtour/images/header.png b/guidedtour/images/header.png new file mode 100644 index 0000000..01553d8 Binary files /dev/null and b/guidedtour/images/header.png differ diff --git a/guidedtour/images/iconwithelipsis.png b/guidedtour/images/iconwithelipsis.png new file mode 100644 index 0000000..05c6a85 Binary files /dev/null and b/guidedtour/images/iconwithelipsis.png differ diff --git a/guidedtour/images/panda.png b/guidedtour/images/panda.png new file mode 100644 index 0000000..295bcbd Binary files /dev/null and b/guidedtour/images/panda.png differ diff --git a/guidedtour/images/panda2.png b/guidedtour/images/panda2.png new file mode 100644 index 0000000..295bcbd Binary files /dev/null and b/guidedtour/images/panda2.png differ diff --git a/guidedtour/images/panda3.png b/guidedtour/images/panda3.png new file mode 100644 index 0000000..3d13cb1 Binary files /dev/null and b/guidedtour/images/panda3.png differ diff --git a/guidedtour/images/prefs1.png b/guidedtour/images/prefs1.png new file mode 100644 index 0000000..81a2eed Binary files /dev/null and b/guidedtour/images/prefs1.png differ diff --git a/guidedtour/images/prefs10.png b/guidedtour/images/prefs10.png new file mode 100644 index 0000000..c381af6 Binary files /dev/null and b/guidedtour/images/prefs10.png differ diff --git a/guidedtour/images/prefs11.png b/guidedtour/images/prefs11.png new file mode 100644 index 0000000..b61bf62 Binary files /dev/null and b/guidedtour/images/prefs11.png differ diff --git a/guidedtour/images/prefs12.png b/guidedtour/images/prefs12.png new file mode 100644 index 0000000..0fef79b Binary files /dev/null and b/guidedtour/images/prefs12.png differ diff --git a/guidedtour/images/prefs13.png b/guidedtour/images/prefs13.png new file mode 100644 index 0000000..67678d8 Binary files /dev/null and b/guidedtour/images/prefs13.png differ diff --git a/guidedtour/images/prefs14.png b/guidedtour/images/prefs14.png new file mode 100644 index 0000000..db06bdd Binary files /dev/null and b/guidedtour/images/prefs14.png differ diff --git a/guidedtour/images/prefs2.png b/guidedtour/images/prefs2.png new file mode 100644 index 0000000..4be47eb Binary files /dev/null and b/guidedtour/images/prefs2.png differ diff --git a/guidedtour/images/prefs3.png b/guidedtour/images/prefs3.png new file mode 100644 index 0000000..7b3fe36 Binary files /dev/null and b/guidedtour/images/prefs3.png differ diff --git a/guidedtour/images/prefs4.png b/guidedtour/images/prefs4.png new file mode 100644 index 0000000..648378f Binary files /dev/null and b/guidedtour/images/prefs4.png differ diff --git a/guidedtour/images/prefs5.png b/guidedtour/images/prefs5.png new file mode 100644 index 0000000..79ae89d Binary files /dev/null and b/guidedtour/images/prefs5.png differ diff --git a/guidedtour/images/prefs6.png b/guidedtour/images/prefs6.png new file mode 100644 index 0000000..368ad5d Binary files /dev/null and b/guidedtour/images/prefs6.png differ diff --git a/guidedtour/images/prefs7.png b/guidedtour/images/prefs7.png new file mode 100644 index 0000000..287c4a5 Binary files /dev/null and b/guidedtour/images/prefs7.png differ diff --git a/guidedtour/images/prefs8.png b/guidedtour/images/prefs8.png new file mode 100644 index 0000000..2180adc Binary files /dev/null and b/guidedtour/images/prefs8.png differ diff --git a/guidedtour/images/prefs9.png b/guidedtour/images/prefs9.png new file mode 100644 index 0000000..bbae97c Binary files /dev/null and b/guidedtour/images/prefs9.png differ diff --git a/guidedtour/images/shadew.jpg b/guidedtour/images/shadew.jpg new file mode 100644 index 0000000..c027ce9 Binary files /dev/null and b/guidedtour/images/shadew.jpg differ diff --git a/guidedtour/images/wadvopt.jpg b/guidedtour/images/wadvopt.jpg new file mode 100644 index 0000000..0456d58 Binary files /dev/null and b/guidedtour/images/wadvopt.jpg differ diff --git a/guidedtour/images/wapspec.jpg b/guidedtour/images/wapspec.jpg new file mode 100644 index 0000000..9d1d197 Binary files /dev/null and b/guidedtour/images/wapspec.jpg differ diff --git a/guidedtour/images/watt.jpg b/guidedtour/images/watt.jpg new file mode 100644 index 0000000..c1c2751 Binary files /dev/null and b/guidedtour/images/watt.jpg differ diff --git a/guidedtour/images/wicon.jpg b/guidedtour/images/wicon.jpg new file mode 100644 index 0000000..9a7a6fc Binary files /dev/null and b/guidedtour/images/wicon.jpg differ diff --git a/guidedtour/images/wksm.jpg b/guidedtour/images/wksm.jpg new file mode 100644 index 0000000..072e431 Binary files /dev/null and b/guidedtour/images/wksm.jpg differ diff --git a/guidedtour/images/wksm.png b/guidedtour/images/wksm.png new file mode 100644 index 0000000..1da526b Binary files /dev/null and b/guidedtour/images/wksm.png differ diff --git a/guidedtour/images/wl.jpg b/guidedtour/images/wl.jpg new file mode 100644 index 0000000..99e329e Binary files /dev/null and b/guidedtour/images/wl.jpg differ diff --git a/guidedtour/images/wlm.jpg b/guidedtour/images/wlm.jpg new file mode 100644 index 0000000..3c754c7 Binary files /dev/null and b/guidedtour/images/wlm.jpg differ diff --git a/guidedtour/images/wlm.png b/guidedtour/images/wlm.png new file mode 100644 index 0000000..b7d44da Binary files /dev/null and b/guidedtour/images/wlm.png differ diff --git a/guidedtour/images/wmakercomponents.png b/guidedtour/images/wmakercomponents.png new file mode 100644 index 0000000..aa219c5 Binary files /dev/null and b/guidedtour/images/wmakercomponents.png differ diff --git a/guidedtour/images/wmakerconf.png b/guidedtour/images/wmakerconf.png new file mode 100644 index 0000000..37dc5c3 Binary files /dev/null and b/guidedtour/images/wmakerconf.png differ diff --git a/guidedtour/images/wprefs.jpg b/guidedtour/images/wprefs.jpg new file mode 100644 index 0000000..b7472e2 Binary files /dev/null and b/guidedtour/images/wprefs.jpg differ diff --git a/guidedtour/images/wspec.jpg b/guidedtour/images/wspec.jpg new file mode 100644 index 0000000..bfc6707 Binary files /dev/null and b/guidedtour/images/wspec.jpg differ diff --git a/guidedtour/index.html b/guidedtour/index.html new file mode 100644 index 0000000..1eac4bf --- /dev/null +++ b/guidedtour/index.html @@ -0,0 +1,129 @@ + + + + + + + + WindowMaker Guided tour - Index + + + + + +

Window Maker

+ +

Guided Tour

+ +

+

+ +
Amanda by Agnieszka Czajkowska
+ +

+

+ +
+

Window Maker

+
+ +

Foreword

+ +This tutorial is intended to help Window Maker users gain knowledge +about the many excellent features +of this window manager.  The official Users Guide is worth reading. It can +be reached from the Window +Maker site.  +Other guides, tutorials and tips can be found at various sites on the +internet.  An +internet search for "Window Maker guide how-to" might provide +additional worthwhile information.
+ +
+ +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. +
+ +
+ +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 "wmaker --version" in +a terminal (without the quotation marks). This command returns the installed version number of Window Maker. +
+ +

A special word of thanks

+ +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. Thank you, Georges. +(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 bnance<atsigngoeshere>uu.edu.
+ +
+ +This tour will attempt to follow Window Maker development, but not +every update can be taken into account.  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.
+ +

Table of contents

+ + + +

+

+ +

Archives

+ +

+

+ +

+Two archives are available: HTML and pictures. +
+tut.tar.gz (12K) HTML files
+img.tar.gz (613K) Picture files

+ +

+

+ +

Links of interest

Window Maker on Debian 6 (YouTube) by fourandnine
+Arch Linux Window Maker Wiki Entry
+Debian Stable (Squeeze) Package Listing
+Window Maker on Mageia Linux (YouTube) by St. Louis Mageia Users' Group
+
+ + +

+

+ +
Window +Maker
+ +

+

+ + diff --git a/guidedtour/menu.html b/guidedtour/menu.html new file mode 100644 index 0000000..a76378f --- /dev/null +++ b/guidedtour/menu.html @@ -0,0 +1,196 @@ + + + + + + + + WindowMaker Guided tour - Index + + + + + + +

+
Menus
+

+ +
Back +to Index
+ + + +

Menu list

+ +

Different menus are available within Window Maker:

+ + + +

Menus provide a list of applications or commands for execution. They +can be used to launch applications, to get information, to configure +the workspace...
+

+ +

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 window +list menu 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.

+ +

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 Enter key executes the selected item. +the Escape key closes the menu or stops menu traversal.

+ +

Menus can be forced to remain open on the workspace by left-clicking +the titlebar. This creates a close button on the titlebar.

+ +

Root window menu

+ +
Root window menu (applications menu)
+ +
+ +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...). +

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.

+ +

Window list menu

+ +
Window list menu
+ +
+ +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. +

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.

+ +

Workspaces menu

+ +
Workspaces menu
+ +
+ +
+ +The workspaces menu is part of the root menu (applications menu). +This item has two options: new and destroy last. +

The first option creates a new workspace and automatically switches +you to it.

+ +

The second option destroys the last workspace as soon as there are +no windows opened in it.

+ +

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.

+ +

Clicking a workspace entry switches from the current workspace to +the selected workspace.

+ +

To change the name of a workspace, first "stick" the menu by +left-clicking the menu titlebar. Then Ctrl + click the menu +item to make it editable and type in the new name. Hitting Return +saves the new name, hitting Escape cancels the operation.

+ +

Key bindings allow movement from one workspace to another. Usually Meta ++ (number). The Meta key +is normally the "Alt" key, +while (number) 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, +Meta + 2 switches to workspace +2.

+ +

These key bindings can be set (or changed) from the keyboard +shortcut dialog in +WPrefs.app.

+ +

Application icon menu

+ +
Icon application menu
+ +
+ +
+ +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  options available.  If an +option is not available, it will appear "greyed out" in the menu.)
+ +
    + +
  1. +

    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.
    +

    +
    2. +
  2. +

    "Launch" opens the application without double-clicking the icon.

    +
    3. +
  3. +

    "Bring here" unhides the application in the current workspace.

    +
    4. +
  4. +

    "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.)

    +
    5. +
  5. +

    "Settings" allows the modification of application path and +arguments, the command line, and the icon used.

    +
    6. +
  6. +

    "Kill" closes the application immediately and should only be +used if absolutely necessary.

    +
    7. +
+ +
Back +to Index
+ + diff --git a/guidedtour/misc.html b/guidedtour/misc.html new file mode 100644 index 0000000..1b88d25 --- /dev/null +++ b/guidedtour/misc.html @@ -0,0 +1,91 @@ + + + Window Maker - Miscellaneous + + + +

+
Miscellaneous
+

+ + +
Back to index
+ + + +

Localization

+ +As soon as Window Maker is compiled with some options and gettext +installed, it +is fully localizable. Check the INSTALL file.
+ +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.
+ +Why do such a "thing" instead of setting the localization the "right" +way?
+ +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.
+ +

Fonts

+ +It's possible to change the fonts in Window Maker, editing the +WindowMaker file +or the WMGLOBAL file in ~/GNUstep/Defaults.
+ +Once again the INSTALL file gives instructions on how to do it.
+ +The specific file to edit varies according to the fonts to be changed.
+ +The script wsetfont is +provided to do the job. +

Utilities

+ +Window Maker provides the user with some useful utilities.
+ +There is a README file concerning these scripts in the util directory.
+ +Almost each script has it's own man page recommended reading.
+ +These utilities mainly concern the GUI: icons, styles, fonts, menus, +backgrounds.
+ +A few of them deserve special interest as many users don't seem to know +about them.
+ +The wdwrite script, for +instance, writes data into the +configuration +files.
+ +The setstyle (or getstyle) scripts are used to +manage themes.
+ +Wxcopy and wxpaste allows copying and pasting +using the X cutbuffer.
+ +The first one makes part of the default applications menu, in the +selection +item.
+ +For KDE users, wkdemenu.pl is worth using.
+ +From version 0.63.0 on, a new utility is available : wmagnify. It allows magnification +of the area under the mouse pointer.
+
+ +
Back to index
+ + diff --git a/guidedtour/news.html b/guidedtour/news.html new file mode 100644 index 0000000..fc2ea35 --- /dev/null +++ b/guidedtour/news.html @@ -0,0 +1,178 @@ + +Window Maker - News + + + + + + + + + +

+
News

+ + + +

+

+ +
Back to index
+ + +

+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 windowmaker.org site. +Moving forward, it is anticipated that additional comments and +observations on Window Maker development news will be provided as well. +

+

Version 0.95.4 released

+ + +

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.

+ + + +

Version 0.95.3 released

+ + +

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.

+ + + +

Version 0.95.2 released

+ + +

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.

+ + + + +

Version 0.95.1 released

+ + + +

Window Maker 0.95.1 was released on January 29th 2012.

+ + + +

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.

+ + + +

New features and highlights

+ + + +

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 git log is the only complete source of information.

+ + + + + + + +

Bug fixes

+ + + +

Window Maker 0.92.0 was already very stable, but many bugs were fixed in this release. A very + 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.

+ + + + + + + +

Summary of changes

+ + + +

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:

+ + +
git diff --shortstat wmaker-0.92.0+..wmaker-0.95.1
 592 files changed, 118361 insertions(+), 133342 deletions(-)
git diff --shortstat 688a56e8ab67b..wmaker-0.95.1
 566 files changed, 37676 insertions(+), 41817 deletions(-)
+The first shortstat is really everything, including the (huge) patch generated in this commit 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 +here. + +

+

+ +
Back to index
+ + + + diff --git a/guidedtour/prefs.html b/guidedtour/prefs.html new file mode 100644 index 0000000..67fc181 --- /dev/null +++ b/guidedtour/prefs.html @@ -0,0 +1,485 @@ + +Window Maker - Prefs + + + + + + + + + +

+
Preferences
+

+ +

+

+ +
Amanda by Agnieszka Czajkowska
+ +

+

+ +
Back +to Index +

WPrefs.app

+
+ +

WPrefs.app is the heart of the configuration process in Window Maker.

+ +

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.
+

+ +
+

GNUstep Logo with ToolsGNUstep Logo
+

+
+ +

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.

+ +

Available preference settings

+ + + +

Window handling

+ +
WPrefs.app window handling preferences
+ +
+ +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. + + +

Window focus

+ +
WPrefs.app window focus controls
+ +
+ +The first icon from the left-hand side controls the way windows get +their focus (how they are activated). + + +

Menu

+ +
WPrefs.app menu preferences
+ +
+ +This panel allows you to set menu scrolling speed and submenu +alignment with the parent menu. In addition, two checkboxes are +provided: + + +

Icon

+ +
WPrefs.app icon preferences
+ +
+ +
+ +

Set icon or miniwindow handling options.
+

+ + + +

Ergonomy

+ +
WPrefs.app ergonomic settings
+ +
+ +Various types of information are defined in this panel. + + +

Search Path

+ +
WPrefs.app icon and pixmap search path settings
+ +
+ +This panel is used to add or delete directory paths to search for +icons and pixmaps. These paths are used in the settings +dialogs for dockapps and docked application icons, so having a good, +complete set of defined paths is important.  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.  Use the add +and remove dialogs to +configure according to what is actually available.
+ +

Workspace

+ +
WPrefs.app workspace preference settings
+ +
+ +This panel defines navigation features within the workspace. + + +

Other

+ +
WPrefs.app other workspace configuration settings
+ +
+ +
+ +

This panel sets icon slide speed, shade animation speed, smooth +scaling and titlebar control (button) style. Animations and sound are +also defined here.

+ + + +

Applications menu

+ +
WPrefs.app application menu configuration
+ +
+ +
+ +

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.

+ +

Keyboard shortcut

+ +
WPrefs.app keyboard shortcut settings
+ +
+ +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. +

Mouse

+ +
WPrefs.app mouse configuration
+ +
+ +This panel sets the mouse speed and double-click delay. +Mouse button bindings can be defined and can be disabled or enabled. +

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.

+ +

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.

+ +

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.

+ +

Appearance

+ +
WPrefs.app appearance settings
+ +
+ +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. +

Expert user

+ +
WPrefs.app expert user settings
+ +
+ +Using this panel implies some knowledge. Many options are available. +Among these are: + + +

Font configuration

+ +
Wprefs.app font configuration options
+ +
+ +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.  In addition, a font may be defined for desktop messages.
+ +

Editing the configuration file

+ +

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.
+

+ +
Back +to Index +
+ + diff --git a/guidedtour/title.css b/guidedtour/title.css new file mode 100644 index 0000000..928d320 --- /dev/null +++ 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; + } diff --git a/guidedtour/win.html b/guidedtour/win.html new file mode 100644 index 0000000..b445100 --- /dev/null +++ b/guidedtour/win.html @@ -0,0 +1,377 @@ + + + + + + + + WindowMaker Guided tour - Index + + + + + +

+
Windows
+

+ +
Back +to Index +
+ + + +

Description

+ +

General layout of a window:

+ + + +

Focusing

+ +

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.

+ +

Two modes are available to focus a window:

+ + + +

Reordering

+ +

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.

+ +

Some key bindings are provided and are very useful when a window is +hidden behind others.

+ + + +

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).

+ +

Moving

+ +

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.

+ +

Maximizing

+ +

Double-clicking the titlebar while holding the Ctrl key resizes the +window's height to full screen.

+ +

Double-clicking the titlebar while holding the Shift key resizes the +window's width to full screen.

+ +

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.

+ +

To prevent a maximized window from covering the dock, the "Keep on +top" option must be selected from the dock menu.

+ +

Miniaturizing

+ +

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.)

+ +

The miniwindow is different from the application icon in that the +miniwindow cannot be docked.

+ +

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.

+ +

Resizing

+ +

The resizebar, at the bottom of the window, is divided into three +regions: left end region, middle region and right end region.

+ +

Depending upon the region you click, the resize operation is +constrained to one direction.

+ +

Clicking in the middle region of the resizebar and dragging it +vertically changes the window's height.

+ +

Clicking in either the left or right region of the resizebar and +dragging it horizontally changes the window's width.

+ +

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.

+ +

Key bindings give more options.

+ + + +

Shading

+ +

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.

+ +

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.

+ +

Hiding

+ +

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.

+ +

Closing

+ +

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 Ctrl key + clicking the close button.

+ +

Usually, it's much better to exit an application from inside +(through it's menu, for instance).

+ +

Commands menu

+ +

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.

+ +

List of Commands Menu commands:

+ +

Maximize/Unmaximize:
+Either maximizes or returns the window to it's initial state.

+ +

Miniaturize:
+Miniaturizes the window (miniwindow). The keyboard shortcut is Meta + m.

+ +

Shade/Unshade: Shades (or unshades) the window.

+ +

Hide:
+Hides all windows of the application. Clicking on the application icon +unhides the windows.

+ +

Hide Others:
+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.

+ +

Resize/Move:
+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.

+ +

Select:
+Obviously selects the window which then can be moved or resized... +Reselecting this option deselects the window.

+ +

Move to:
+Allows to move the window to another workspace (if existing!).

+ +

Attributes:
+Opens the attributes panel to edit attributes and options for the +window.

+ +

Five options are available in this panel: Window specification, +Window attributes, Advanced options, Icon and initial workspace and +application specific.

+ + + +

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.

+ +

Options:

+ +

Submenu options allow to:

+ + + +

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.

+ +

Close:
+Closes the window

+ +

Kill:
+Kills the application. +Usually, an application must be closed from inside (menu or other +means). This option is especially reserved for "emergency" cases.

+ +