Menu
▾
▴
[Fvwm-crystal-commits] SF.net SVN: fvwm-crystal:[475]
|
From: <dom...@us...> - 2013-05-26 13:03:40
|
Revision: 475
http://sourceforge.net/p/fvwm-crystal/code/475
Author: dominique_libre
Date: 2013-05-26 13:03:36 +0000 (Sun, 26 May 2013)
Log Message:
-----------
+ asciidoc/fvwm-crystal: introduced fvwm-crystal man page. asciidoc/*; functions/About: updated version to 3.2.0. functions/Developer-Menu: added fvwm-crystal man page
Modified Paths:
--------------
ChangeLog
asciidoc/ApplicationDatabase
asciidoc/CrystalRoxHOWTO
asciidoc/FAQ
asciidoc/KeyboardBindings
asciidoc/MouseBindings
asciidoc/Tips
asciidoc/create.sh
doc/html/ApplicationDatabase.html
doc/html/CrystalRoxHOWTO.html
doc/html/FAQ.html
doc/html/KeyboardBindings.html
doc/html/MouseBindings.html
doc/html/Tips.html
fvwm/components/functions/About
fvwm/components/functions/Developer-Menu
man/ApplicationDatabase.1
man/CrystalRoxHOWTO.1
man/FVWMCrystalFAQ.1
man/KeyboardBindings.1
man/MouseBindings.1
man/Tips.1
Added Paths:
-----------
asciidoc/fvwm-crystal
doc/html/fvwm-crystal.html
man/fvwm-crystal.1
Modified: ChangeLog
===================================================================
--- ChangeLog 2013-05-26 10:03:25 UTC (rev 474)
+++ ChangeLog 2013-05-26 13:03:36 UTC (rev 475)
@@ -3,7 +3,10 @@
Dimanche 25 Mai 2013 Dominique Michel
preferences/MediaDirectories: replaced variables by full paths
INSTALL: changed some sentence to reflect the actual process.
-
++ asciidoc/fvwm-crystal: introduced fvwm-crystal man page
+ asciidoc/*; functions/About: updated version to 3.2.0
+ functions/Developer-Menu: added fvwm-crystal man page
+
Samedi 24 Mai 2013 Dominique Michel
- apps/Thunar;
+ apps/DesktopIcons; functions/Preferences-Menu: renamed Thunar to DesktopIcons
Modified: asciidoc/ApplicationDatabase
===================================================================
--- asciidoc/ApplicationDatabase 2013-05-26 10:03:25 UTC (rev 474)
+++ asciidoc/ApplicationDatabase 2013-05-26 13:03:36 UTC (rev 475)
@@ -2,7 +2,7 @@
======================
:doctype: manpage
:man source: ApplicationDatabase
-:man version: 3.1.12
+:man version: 3.2.0
:man manual: FVWM-Crystal
NAME
Modified: asciidoc/CrystalRoxHOWTO
===================================================================
--- asciidoc/CrystalRoxHOWTO 2013-05-26 10:03:25 UTC (rev 474)
+++ asciidoc/CrystalRoxHOWTO 2013-05-26 13:03:36 UTC (rev 475)
@@ -2,7 +2,7 @@
==================
:doctype: manpage
:man source: CrystalROXHOWTO
-:man version: 3.1.12
+:man version: 3.2.0
:man manual: FVWM-Crystal
NAME
Modified: asciidoc/FAQ
===================================================================
--- asciidoc/FAQ 2013-05-26 10:03:25 UTC (rev 474)
+++ asciidoc/FAQ 2013-05-26 13:03:36 UTC (rev 475)
@@ -2,7 +2,7 @@
===================
:doctype: manpage
:man source: FAQ
-:man version: 3.1.12
+:man version: 3.2.0
:man manual: FVWM-Crystal
NAME
Modified: asciidoc/KeyboardBindings
===================================================================
--- asciidoc/KeyboardBindings 2013-05-26 10:03:25 UTC (rev 474)
+++ asciidoc/KeyboardBindings 2013-05-26 13:03:36 UTC (rev 475)
@@ -2,7 +2,7 @@
===================
:doctype: manpage
:man source: KeyboardBindings
-:man version: 3.1.12
+:man version: 3.2.0
:man manual: FVWM-Crystal
NAME
@@ -214,8 +214,7 @@
*`Alt + Shift + KP_*`*::
Switch focus between the different full-screened windows of the current
- desktop page and the desktop. This is an innovative way to flow through
- desktop space.
+ desktop page and the desktop.
*Alt + KP_-* or *Alt + Backspace*::
Iconifies currently focused window (or makes a thumbnail).
@@ -238,16 +237,11 @@
----------------
*Print Screen*::
Makes a screenshot of the entire desktop in .jpg format and puts it in
- '~/.fvwm-crystal/screenshots/' directory (by default).
+ '~/.fvwm/screenshots/' directory (by default).
*Alt + Home*::
Move mouse cursor to "home position" - top left corner of the screen.
-*Alt + E*::
- Launch FVWMExpose, an expose clone function. It use xwd to take
- screenshoots of the applications of the current desktop page,
- show them and let you choose one.
-
Note:
-----
If you want to modify some bindings, the best place is to put them into
Modified: asciidoc/MouseBindings
===================================================================
--- asciidoc/MouseBindings 2013-05-26 10:03:25 UTC (rev 474)
+++ asciidoc/MouseBindings 2013-05-26 13:03:36 UTC (rev 475)
@@ -2,7 +2,7 @@
================
:doctype: manpage
:man source: MouseBindings
-:man version: 3.1.12
+:man version: 3.2.0
:man manual: FVWM-Crystal
NAME
Modified: asciidoc/Tips
===================================================================
--- asciidoc/Tips 2013-05-26 10:03:25 UTC (rev 474)
+++ asciidoc/Tips 2013-05-26 13:03:36 UTC (rev 475)
@@ -2,7 +2,7 @@
=======
:doctype: manpage
:man source: Tips
-:man version: 3.1.12
+:man version: 3.2.0
:man manual: FVWM-Crystal
NAME
Modified: asciidoc/create.sh
===================================================================
--- asciidoc/create.sh 2013-05-26 10:03:25 UTC (rev 474)
+++ asciidoc/create.sh 2013-05-26 13:03:36 UTC (rev 475)
@@ -1,6 +1,6 @@
#!/bin/bash
-asciidoc_files=(ApplicationDatabase CrystalRoxHOWTO FAQ KeyboardBindings MouseBindings Tips)
+asciidoc_files=(fvwm-crystal ApplicationDatabase CrystalRoxHOWTO FAQ KeyboardBindings MouseBindings Tips)
dodoc() {
a2x -vf manpage $1
@@ -12,17 +12,25 @@
}
-for name in ${asciidoc_files[*]}
-do
- dodoc ${name}
-done
+controldoc() {
+ for name in ${asciidoc_files[*]}
+ do
+ dodoc ${name}
+ done
+ for name in *.1
+ do
+ mv ${name} ../man/${name}
+ done
-for name in *.1
-do
- mv ${name} ../man/${name}
-done
+ for name in *.html
+ do
+ mv ${name} ../doc/html/${name}
+ done
+}
-for name in *.html
-do
- mv ${name} ../doc/html/${name}
-done
+if [ $# -eq 0 ]
+then
+ controldoc
+else
+ dodoc $1
+fi
Added: asciidoc/fvwm-crystal
===================================================================
--- asciidoc/fvwm-crystal (rev 0)
+++ asciidoc/fvwm-crystal 2013-05-26 13:03:36 UTC (rev 475)
@@ -0,0 +1,359 @@
+fvwm-crystal(1)
+===============
+:doctype: manpage
+:man source: fvwm-crystal
+:man version: 3.2.0
+:man manual: FVWM-Crystal
+
+NAME
+----
+
+fvwm-crystal - an easy to use, eye-candy but also powerful desktop environment for GNU/Linux or other Unix-like operating systems.
+
+
+SYNOPSIS
+--------
+
+None
+
+
+DESCRIPTION
+-----------
+
+*FVWM-Crystal* aims to be an easy to use, eye-candy but also powerful desktop environment based on the F? Virtual Window Manager (FVWM). It uses following programs: FVWM as a window manager and "main core", icons on the desktop with support for more than 10 different file managers and custom commands (with optional Nautilus or ROX-Filer support), different terminal emulators inclusive xterm, aterm, mrxvt or urxvt, different music and medias players inclusive MPD, XMMS2 or MPlayer (there's built-in support for controlling these programs, and several other tools for different functions, like setting a wallpaper or making screen shots. Fvwm-Crystal provide some unique features like the ability to bring in full screen virtually any application, and to flow through the full-screened applications and the desktop. In this document you will find a general description of *FVWM-Crystal*, how to begin with it and how to customize it.
+
+USAGE
+-----
+
+First Start
+~~~~~~~~~~~
+*FVWM-Crystal* checks while your first login if +~/.fvwm-crystal+ exist and if old preferences must be converted to the new Fvwm InfoStore variables. In all cases, it should just start.
+
+*FVWM-Crystal* will also check your locale and create the XDG localized user directories if they don't exist. Those directories are common to most modern OS and are used to store dedicated files. As example +$HOME/Music+, +$HOME/Documents+ and +$HOME/Pictures+.
+
+
+Initial Media Player Setup
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+MPlayer is the default media player. A help screen can pop-up and show you how to setup the Media directories preferences, which tell FVWM-Crystal where your music and movie files are. You can do it now or later, but it must be done before to use the play-lists features found in the Music menu (or button).
+
+For that, edit the file +~/.fvwm-crystal/preferences/MediaDirectories+:
+----
+audio $HOME/Music
+video $HOME/Video
+cdrom /dev/cdrom0
+dvd /dev/cdrom1
+----
+
+You can put as many lines you need. Each line have the following format:
+----
+type path
+----
+where *type* is one of [+audio+ +video+ +cdrom+ +dvd+]
+and *path* is the +full path+ to a directory or a device.
+Devices are used only for +cd+ and +dvd+.
+Note that all players doesn't support all the provided features. Their respective menus will be adjusted accordingly.
+
+As example, you can have:
+----
+audio /home/name/Music
+viedo /home/name/Video
+audio /mnt/work/Music
+video /mnt/usb/Video
+dvd /dev/cdrom
+----
+
+When you are done, save the file. You can load the control for your preferred player from the preferences menu
+----
+Crystal -> Music -> Player -> Music player
+----
+or from the menu on the first music button.
+
+In the same menu, you will find +Recreate the playlists+. This script will scan the paths pointed by the MediaDirectories preference file, and create the play-lists into +$HOME/.fvwm-crystal/Playlists+. They will be separated into an Audio and a Video part. We can cal them the Crystal play-lists. Don't edit those files, all your changes will be lost the next time you run +Recreate the playlists+. Instead, 2 other directories will be created: +$HOME/Playlists/Audio+ and +$HOME/Playlists/Video+. They are the User play-lists.
+
+In the same Music menu, the play-lists operation are grouped. You can of course load them into the selected player. +Copy playlist+ will copy the selected play-list from the Crystal play-lists to the User play-lists. +Remove playlist+ will remove the selected play-lists from the User play-lists. Some players provide they own play-lists management system, FVWM-Crystal try to support them as well.
+
+Some supported players must be setup before FVWM-Crystal can use them. For that, please refer to their respective documentation. If you have a DVB card, please refer also to the linuxtv.org V4L-DVB Wiki at <http://linuxtv.org/wiki/index.php/Main_Page>.
+
+
+Desktop Organisation
+~~~~~~~~~~~~~~~~~~~~
+17 different desktop layouts, named recipes, are available.
+
+Some are very simple and provide very few decorations. Others provide many buttons and decorations. A few of them mimic existing OS, like Nebulae which loosely mimic Windows or Amiga which mimic the Amiga OS.
+
+You can change them via Fvwm-Crystal system menu
+----
+Preferences -> Recipes -> System
+----
+
+The other preferences apply to all recipes and are independent from each others.
+By example, you can choose to have desktop icons showing the XDG user directories and the mounted partitions, and to not have applications icons.
+
+It is 2 menus, the system menu available with *Alt + Win_R* (Meta + Windows Left) and the application menu available with *Alt + Menu* (Meta + a "menu" key). A menu can also be available by holding a *Left click* on the root window (the desktop) if selected in System -> Preferences -> Desktop menu (On by default). The content of that menu depend on the recipe in use.
+
+
+Decorations common to all recipes
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Not all recipes use all followings decorations called buttons, but they can be used in any recipe, inclusive your own ones.
+
+_The "Crystal" Button_::
++
+or "FvwmButtons-MainMenu" is the little button with a diamond.
++
+There are some mouse bindings available:
++
+* left clicking open the system menu
+* middle clicking change the wallpaper randomly
+* right clicking on some recipes open the applications menu
+
++
+The Amiga recipe is different:
++
+* left clicking shift the top bar to a menu bar and back
+* middle clicking change the wallpaper randomly
+* right clicking open the system menu
+
++
+When the button is located at the top left corner:
++
+* mouse wheeling will change the screen resolution
+
+_The Media Buttons_::
++
+They are 4 grouped media buttons - FvwmButtons-Music - providing controls and menus for the supported media players and mixers. For a description of their bindings, consult *man MouseBindings* and *man KeyboardBindings*, or the html documentation.
++
+The same functionalities are provided by the Music menu, which is located in the System menu.
++
+The supported media players are +alsaplayer+, +audacious+, +cdcd+, +cmus+, +mocp+, +mpd+, +mplayer+, +mplayer2+, +quodlibet+ and +xmms2+.
++
+The supported audio mixers are +alsamixer+ and +aumix+, plus the mixers of the players. +QJackCTL+ is also supported.
++
+* left clicking on the first media button will open a menu.
+
++
+In it, +Music player+ is where you choose the player and can start it. +Recreate the playlists+ will scan your music and video files and create the play-lists for you. For that, it will use the preferences file you edited in the section "First Start". It is also a mixer preferences menu where you can choose the mixer and the sound card.
++
+Each player have its own features set, and the Music menu and functions will change accordingly.
++
+As example, with *cdcd* you have a cd player and you will be able to control it, when with *mplayer*, you have an universal media player, and FVWM-Crystal will even recognize if you have a DVB card and use it. Basic stream capture is enabled and use the standard 'C' MPlayer key binding. See *man mplayer*. This will create a stream dump in $HOME. That file will be usable only with MPEG sources, and it can be edited with applications like +Kino+.
+
+_The Application Panel_::
++
+It is an auto generated panel which provide one button for each *FreeDesktop* menu main category. The icon of each button is the icon of the preferred application of that category. The mouse bindings available are:
++
+* left clicking open the application menu of the category
+* middle clicking on some recipes launch the second preferred application
+* right clicking launch the preferred application
+
++
+These menus have full support for the additional FreeDesktop categories, which mean much less modifications will be needed in comparison with many other desktops. And last but not least, your modifications will never be lost. It is why at the first place I begun with Crystal and I will keep it that way. See *man ApplicationDatabase* for how to customize the application menu (the examples are at the end).
++
+More: the files in the applications database are scripts. You can put anything you want into them. You will find them into +$prefix/share/fvwm-crystal/fvwm/Applications+ and +$HOME/.fvwm-crystal/Applications+, and can copy them fro this first location to the second one. The files in the second path will take the precedence. The same apply for the icons directory.
++
+The same database is used to generate the application menu available with the system menu on some recipes, and with the Alt+Menu key binding.
++
+The application database provided by +FVWM_Crystal+ contain a large set of menu entries and application icons. You can generate extra database menu entries and icons from the preferences menu: +Diamond -> Preferences -> Generate application menu+. This will populate +$HOME/.fvwm-crystal/Applications+ and +$HOME/.fvwm-crystal/icons+.
++
+The 2 first time you run this script, it will copy 2 preferences files and show help messages.
++
+Those files are +$HOME/.fvwm-crystal/preferences/IconDirs+ and +$HOME/.fvwm-crystal/preferences/DesktopDirs+. They must contain the full path to where the icon and desktop files provided by the applications are stored, typically something like +/usr/share/icons+ and +/usr/share/pixmaps+ for the icons, and +/usr/share/applications+ and +/usr/share/applications/kde4+ for the desktop files. The 2 preference files are self explained.
+
+
+_The Clock_::
++
+As it name describe it, a clock.
+
+
+_The Pager_::
++
+It is a miniature illustration of the virtual desktop pages with mini windows. By clicking on each of the segments you can change the page.
++
+For a description of the bindings, see "man MouseBindings".
+*
+Some recipes provide only a small button. Clicking on it will show or hide the pager.
++
+The number of desktop pages can be changed on the fly from the preferences menu, option +Desktop geometry+. If necessary, windows will be moved on the last available desktop page.
+
+
+_Notification area_::
++
+Both stalonetray and trayer are supported. For best support will all recipes, use stalonetray.
+
+
+_Icon Manager_::
++
+A recipe can provide several icon managers. They can show the icons from the running applications on the whole desktop or on the current desktop page. They can be grouped by applications type like terminals or other application types. The application name can be shown in the icon manager or as a tool-tip when the mouse is over the icon. And different actions are bound to these icons.
++
+Some recipes provide an icon manager for the iconic applications. With these recipes, no application icons will be on the desktop, independently of what choice was made in the preferences.
+
+
+_Desktop Icons_::
++
+It is 2 types of icons: application icons and desktop icons.
++
+Desktop icons are typically used to launch a file browser at a given path. You can choose in +Preferences -> Desktop manager+ how FVWM-Crystal will manage them:
++
+* +None+ will remove the desktop icons
+* +FVWM-Crystal+ will let FVWM-Crystal manage these icons
+* +ROX_Filer+ will manage these icons
+* +Nautilus+ will manage these icons.
+
++
+You can change on the fly between +None+ and +FVWM-Crystal+. The other changes need to logout and restart Xorg and FVWM-Crystal. At that time of writing, the FVWM-Crystal-3.2.0 desktop icon managing is mature enough to considerer that ROX-Filer and Nautilus are provided only as a commodity or for backward compatibility or convenience. (See *man CrystalRoxHOWTO* for rox.)
++
+When +FVWM-Crystal+ is selected, it will show all its icons be default. Right clicking on the +Home+ icon will open the +Desktop icons preference menu+. the +Home+ icon is mandatory, both the +XDG user directories+ icons and the +partitions+ icons are optionals.
++
+In the same menu, you can select the actions for the left and middle clicks. Several file managers have built-in support: +Thunar+, +Worker+ (a very good Directory Opus clone), +Midnight Commander+ (mc in short), +ROX-Filer+, +Nautilus+, +Krusader+, +Xfm+, +4Pane+, +Ranger+ (a Vim like file manager), +PCMan FM+, +gentoo+ (another dopus clone), +Konqueror+, +emelFM2+ (which, like mc, support extfs), +Dolphin+ and +SpaceFM+.
++
+A custom command can also be set where both console commands and X commands can be used. A self documented form will be launched, which let you update and save the configuration.
+
+
+_Application Icons_::
++
+They are the icons of the iconic applications. This will work only with the recipe that doesn't provide an icon manager for them.
++
+In Preferences -> Type of icons, you can choose between:
++
+* +None+
+* +Thumbnails+
+* +Amiga+
+* +Mwm+
+
++
++Amiga+ and +Mwm+ will show the application icons. Simple clicking on the +Amiga+ style icons will restore the application window. Double clicking on the +Mwm+ style icons will do the same.
+
+
+Full Screen Navigation
+----------------------
+For what I know, FVWM-Crystal is the only GNU/Linux desktop that provide that feature.
+
+In short, *Full Screen Navigation* is the ability to bring in full screen virtually any application, and to navigate between these full-screened applications, as well than between them and the desktop.
+
+It can be many useful use cases for it. As example, if you have several browser windows open and want to zap quickly. Or with a file manager like mc which is limited to 2 panels. It is one limitation: the full screened windows must be on the same desktop page. This limitation is a force at the same time, because you can zap the desktop pages too, and you can have full-screened and "normal" windows in any desktop page at the same time.
+
+Try it. Launch a few applications on the current desktop pages ans put them in full screen with *Alt + KP_\**. When this is done, use *Alt + Shift + KP_** to zap between the full screened windows and the desktop. With *Alt + F<n>*, you can zap the desktop pages.
+
+In fact, this functionality is not new. It was already available with the first Amiga computer in 1985, when Windows was not born and the Mac was boring in black and white. It was called the window stack. With the +Amiga recipe+, simple clicking on the button at the top right corner provide that function too.
+
+
+PREFERENCES
+-----------
+Most preferences are applied on the fly. Some, like a recipe change, need a restart.
+
+*Select recipe*::
+ Select a recipe.
+
+*Desktop geometry*::
+ Select the number of desktop pages from 1 to 9.
+
+*Characters fonts*::
+ Launch FVWM-Crystal font selector dialog. *Panel font* is used by the buttons, *Tittle font* by the window title bars, and *Menu font* by menus. FVWM-Crystal support xft fonts and this dialog let you visualize the fonts, save and apply the fonts, as well than edit, save and restore the example string. Restore will restore the example string to its original value. To restore it to its saved value, you have to quit and launch again the font selector.
+
+*Handle width*::
+ Set the handle width between 1 to 7 pixels. Handles are used to resize the windows with the mouse. See also *man KeyboardBindings".
+
+*Translucency*::
+ Start and stop translucency. Off by default, this setting will not survive a restart. When On, you can use the mouse wheel on the window title bars to set their translucency.
+
+*Bling bling*::
+ Start and stop the bling bling. It is an effect that will shift the translucency with the focus. This setting is Off by default and will not survive a restart. Translucency can have a negative impact whit some softwares like MPlayer. In the worst case, shift to a primary console with *Ctrl + Alt + F<n>*, login, run *killall mplayer* or *killall -9 mplayer*, and get back to FVWM-Crystal with *Alt + F7*.
+
+*Default terminal*::
+ Set the terminal available with *Right click* on the root window. Possible choices: +GNOME-Terminal+, +Multi-GNOME-Terminal+, +XFCE4-Terminal+, +Terminator+, +MRxvt+, URxvt+, +ATerm+, +ETerm+ and +XTerm+.
+
+*Fvwm console terminal*::
+ Set FVWM console terminal, *Alt + ;* will show/hide it, and it will be present on all desktop pages. It will only send commands to FVWM. Very useful to try any FVWM command.
+
+*QuakeConsole termianl*::
+ Set terminal for the QuakeConsole. *Alt + ' (grave)* will show/hide it, and it will be present on all desktop pages. You can use it for whatever console you want, by example htop. Supported by these 2 last terminal are +MRxvt+, +URxvt+, +ATerm+ and +XTerm+.
+
+*Desktop manager*::
+ Select the manager for the desktop icons. See above.
+
+*Icon type*::
+ Select the icon type for iconic applications. See above.
+
+*Desktop menu*::
+ Set On or Off the menu available with left clicking.
+
+*Notification area manager*::
+ Select stalonetray or trayer, and let you choose the size of the area between 0 to 20 icons.
+
+*Focus policy*::
+ Select the focus policy between
+ - +Amiga+ - click to focus without raise
+ - +FVWM-Crystal+ -enter to focus without raise
+ - +FVWM-Crystal with raise+ - enter to focus with raise
+ - +MS Windows+ - click to focus with raise.
+
+With the without raise policies, a click on a title bar will raise the window.
+
+*Privileged terminals*::
+ With URxvt and ETerm, set the FPOverrideGrabFocus style. Such terminals will never loose the focus.
+
+*Generate application menu*::
+ Generate the databse entries and icons for the applications menu.
+
+*Silent operations*::
+ Add "2>/dev/null" at the end of most commands launched by FVWM-Crystal.
+
+
+CUSTOMIZATION
+-------------
+Structure of Fvwm-Crystal
+~~~~~~~~~~~~~~~~~~~~~~~~~
+*FVWM-Crystal* is split in a system, a system wide configuration, and an user configuration part.
+
+The system part is located in +/usr/local/share/fvwm-crystal/fvwm+ (default) or +/usr/share/fvwm-crystal/fvwm+ (distribution related). We can call it <system>
+
+The system configuration part is located in +/etc/X11/fvwm/fvwm-crystal+. Call it <config>
+
+The user part is located in +~/.fvwm-crystal+. <user>
+
+You can copy any file from the system part (without the /fvwm/) to the 2 other parts. Files in the user part will be used first, second will be the files in the system configuration part (empty be default), and third will be used the files in the system part. This is true for all files loaded with the +Include+ command, which is the case for most FVWM-Crystal files.
+
+
+Location of some Files and their Function
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+*<system>/config* will be the first file loaded by FVWM. It initialize some variables and load the whole FVWM-Crystal configuration, inclusive the recipe in use.
+
+*<system>/components/Standard* is the second file loaded by FVWM. It contain the functions used to load the other file with respect to their priorities part order. After, it load other files with functions used in many places.
+
+The other files in <system> are grouped in directories. Each directory correspond to a group of functions. For example, *<system>/preferences* are for the saved preferences, *<system>/apps* are functions to control some main features of FVWM-Crstal like the Desktop Icons, the Screen Saver, or the Fvwm Console.
+
+As a rule, make small modification at a time. And RTFM. FVWM is not so difficult, but it is very complex. This complexity make things harder. So, try to keep focused on one thing at a time.
+
+FVWM documentation is huge, The best place to read it is on the FVWM website where you will find an html version, which ease the navigation. Use the stable 2.6 branch, the unstable 2.7 is outdated and will not work well with FVWM-Crystal.
+
+
+Autostart of Applications
+~~~~~~~~~~~~~~~~~~~~~~~~~
+Copy *<system>/preferences/Startup* to *<user>/preferences/Startup* and put your commands here.
+
+
+Custom FVWM Commands
+~~~~~~~~~~~~~~~~~~~~
+Create the file *<user>/userconfig* and put your FVWM commands here. It will be the last loaded file.
+
+
+AUTHORS
+-------
+This man page was written by Dominique Michel <dom...@us...> (C) 2013
+
+
+COPYRIGHT
+---------
+*FVWM-Crystal* and all the scripts and other files coming with
+the distribution are subject to the GNU General Public License (GPL).
+Please refer to the COPYING file that came with *FVWM-Crystal* for details.
+
+
+BUGS
+----
+Bug reports can be sent to the fvwm-crystal-users mailing list at
+<https://mail.gna.org/listinfo/fvwm-crystal-users/>.
+
+
+SEE ALSO
+--------
+*KeyboardBindings*(1), *MouseBindings*(1), *FVWMCrystalFAQ*(1), *TIPS*(1), *CrystalRoxHOWTO*(1), *ApplicationDatabase*(1) <http://fvwm-crystal.sourceforge.net/>
Modified: doc/html/ApplicationDatabase.html
===================================================================
--- doc/html/ApplicationDatabase.html 2013-05-26 10:03:25 UTC (rev 474)
+++ doc/html/ApplicationDatabase.html 2013-05-26 13:03:36 UTC (rev 475)
@@ -957,7 +957,7 @@
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-25 14:27:45 CEST
+Last updated 2013-05-26 14:56:32 CEST
</div>
</div>
</body>
Modified: doc/html/CrystalRoxHOWTO.html
===================================================================
--- doc/html/CrystalRoxHOWTO.html 2013-05-26 10:03:25 UTC (rev 474)
+++ doc/html/CrystalRoxHOWTO.html 2013-05-26 13:03:36 UTC (rev 475)
@@ -840,7 +840,7 @@
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-25 13:54:44 CEST
+Last updated 2013-05-26 14:56:21 CEST
</div>
</div>
</body>
Modified: doc/html/FAQ.html
===================================================================
--- doc/html/FAQ.html 2013-05-26 10:03:25 UTC (rev 474)
+++ doc/html/FAQ.html 2013-05-26 13:03:36 UTC (rev 475)
@@ -1275,7 +1275,7 @@
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-25 14:25:00 CEST
+Last updated 2013-05-26 14:56:01 CEST
</div>
</div>
</body>
Modified: doc/html/KeyboardBindings.html
===================================================================
--- doc/html/KeyboardBindings.html 2013-05-26 10:03:25 UTC (rev 474)
+++ doc/html/KeyboardBindings.html 2013-05-26 13:03:36 UTC (rev 475)
@@ -1188,8 +1188,7 @@
<dd>
<p>
Switch focus between the different full-screened windows of the current
- desktop page and the desktop. This is an innovative way to flow through
- desktop space.
+ desktop page and the desktop.
</p>
</dd>
<dt class="hdlist1">
@@ -1246,7 +1245,7 @@
<dd>
<p>
Makes a screenshot of the entire desktop in .jpg format and puts it in
- <em>~/.fvwm-crystal/screenshots/</em> directory (by default).
+ <em>~/.fvwm/screenshots/</em> directory (by default).
</p>
</dd>
<dt class="hdlist1">
@@ -1257,16 +1256,6 @@
Move mouse cursor to "home position" - top left corner of the screen.
</p>
</dd>
-<dt class="hdlist1">
-<strong>Alt + E</strong>
-</dt>
-<dd>
-<p>
- Launch FVWMExpose, an expose clone function. It use xwd to take
- screenshoots of the applications of the current desktop page,
- show them and let you choose one.
-</p>
-</dd>
</dl></div>
</div>
</div>
@@ -1332,7 +1321,7 @@
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-25 15:33:29 CEST
+Last updated 2013-05-26 14:55:50 CEST
</div>
</div>
</body>
Modified: doc/html/MouseBindings.html
===================================================================
--- doc/html/MouseBindings.html 2013-05-26 10:03:25 UTC (rev 474)
+++ doc/html/MouseBindings.html 2013-05-26 13:03:36 UTC (rev 475)
@@ -1767,7 +1767,7 @@
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-25 14:27:21 CEST
+Last updated 2013-05-26 14:55:38 CEST
</div>
</div>
</body>
Modified: doc/html/Tips.html
===================================================================
--- doc/html/Tips.html 2013-05-26 10:03:25 UTC (rev 474)
+++ doc/html/Tips.html 2013-05-26 13:03:36 UTC (rev 475)
@@ -838,7 +838,7 @@
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-05-25 14:27:54 CEST
+Last updated 2013-05-25 18:43:41 CEST
</div>
</div>
</body>
Added: doc/html/fvwm-crystal.html
===================================================================
--- doc/html/fvwm-crystal.html (rev 0)
+++ doc/html/fvwm-crystal.html 2013-05-26 13:03:36 UTC (rev 475)
@@ -0,0 +1,1258 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
+<meta name="generator" content="AsciiDoc 8.6.8" />
+<title>fvwm-crystal(1)</title>
+<style type="text/css">
+/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
+
+/* Default font. */
+body {
+ font-family: Georgia,serif;
+}
+
+/* Title font. */
+h1, h2, h3, h4, h5, h6,
+div.title, caption.title,
+thead, p.table.header,
+#toctitle,
+#author, #revnumber, #revdate, #revremark,
+#footer {
+ font-family: Arial,Helvetica,sans-serif;
+}
+
+body {
+ margin: 1em 5% 1em 5%;
+}
+
+a {
+ color: blue;
+ text-decoration: underline;
+}
+a:visited {
+ color: fuchsia;
+}
+
+em {
+ font-style: italic;
+ color: navy;
+}
+
+strong {
+ font-weight: bold;
+ color: #083194;
+}
+
+h1, h2, h3, h4, h5, h6 {
+ color: #527bbd;
+ margin-top: 1.2em;
+ margin-bottom: 0.5em;
+ line-height: 1.3;
+}
+
+h1, h2, h3 {
+ border-bottom: 2px solid silver;
+}
+h2 {
+ padding-top: 0.5em;
+}
+h3 {
+ float: left;
+}
+h3 + * {
+ clear: left;
+}
+h5 {
+ font-size: 1.0em;
+}
+
+div.sectionbody {
+ margin-left: 0;
+}
+
+hr {
+ border: 1px solid silver;
+}
+
+p {
+ margin-top: 0.5em;
+ margin-bottom: 0.5em;
+}
+
+ul, ol, li > p {
+ margin-top: 0;
+}
+ul > li { color: #aaa; }
+ul > li > * { color: black; }
+
+.monospaced, code, pre {
+ font-family: "Courier New", Courier, monospace;
+ font-size: inherit;
+ color: navy;
+ padding: 0;
+ margin: 0;
+}
+
+
+#author {
+ color: #527bbd;
+ font-weight: bold;
+ font-size: 1.1em;
+}
+#email {
+}
+#revnumber, #revdate, #revremark {
+}
+
+#footer {
+ font-size: small;
+ border-top: 2px solid silver;
+ padding-top: 0.5em;
+ margin-top: 4.0em;
+}
+#footer-text {
+ float: left;
+ padding-bottom: 0.5em;
+}
+#footer-badges {
+ float: right;
+ padding-bottom: 0.5em;
+}
+
+#preamble {
+ margin-top: 1.5em;
+ margin-bottom: 1.5em;
+}
+div.imageblock, div.exampleblock, div.verseblock,
+div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
+div.admonitionblock {
+ margin-top: 1.0em;
+ margin-bottom: 1.5em;
+}
+div.admonitionblock {
+ margin-top: 2.0em;
+ margin-bottom: 2.0em;
+ margin-right: 10%;
+ color: #606060;
+}
+
+div.content { /* Block element content. */
+ padding: 0;
+}
+
+/* Block element titles. */
+div.title, caption.title {
+ color: #527bbd;
+ font-weight: bold;
+ text-align: left;
+ margin-top: 1.0em;
+ margin-bottom: 0.5em;
+}
+div.title + * {
+ margin-top: 0;
+}
+
+td div.title:first-child {
+ margin-top: 0.0em;
+}
+div.content div.title:first-child {
+ margin-top: 0.0em;
+}
+div.content + div.title {
+ margin-top: 0.0em;
+}
+
+div.sidebarblock > div.content {
+ background: #ffffee;
+ border: 1px solid #dddddd;
+ border-left: 4px solid #f0f0f0;
+ padding: 0.5em;
+}
+
+div.listingblock > div.content {
+ border: 1px solid #dddddd;
+ border-left: 5px solid #f0f0f0;
+ background: #f8f8f8;
+ padding: 0.5em;
+}
+
+div.quoteblock, div.verseblock {
+ padding-left: 1.0em;
+ margin-left: 1.0em;
+ margin-right: 10%;
+ border-left: 5px solid #f0f0f0;
+ color: #888;
+}
+
+div.quoteblock > div.attribution {
+ padding-top: 0.5em;
+ text-align: right;
+}
+
+div.verseblock > pre.content {
+ font-family: inherit;
+ font-size: inherit;
+}
+div.verseblock > div.attribution {
+ padding-top: 0.75em;
+ text-align: left;
+}
+/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
+div.verseblock + div.attribution {
+ text-align: left;
+}
+
+div.admonitionblock .icon {
+ vertical-align: top;
+ font-size: 1.1em;
+ font-weight: bold;
+ text-decoration: underline;
+ color: #527bbd;
+ padding-right: 0.5em;
+}
+div.admonitionblock td.content {
+ padding-left: 0.5em;
+ border-left: 3px solid #dddddd;
+}
+
+div.exampleblock > div.content {
+ border-left: 3px solid #dddddd;
+ padding-left: 0.5em;
+}
+
+div.imageblock div.content { padding-left: 0; }
+span.image img { border-style: none; }
+a.image:visited { color: white; }
+
+dl {
+ margin-top: 0.8em;
+ margin-bottom: 0.8em;
+}
+dt {
+ margin-top: 0.5em;
+ margin-bottom: 0;
+ font-style: normal;
+ color: navy;
+}
+dd > *:first-child {
+ margin-top: 0.1em;
+}
+
+ul, ol {
+ list-style-position: outside;
+}
+ol.arabic {
+ list-style-type: decimal;
+}
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+div.compact ul, div.compact ol,
+div.compact p, div.compact p,
+div.compact div, div.compact div {
+ margin-top: 0.1em;
+ margin-bottom: 0.1em;
+}
+
+tfoot {
+ font-weight: bold;
+}
+td > div.verse {
+ white-space: pre;
+}
+
+div.hdlist {
+ margin-top: 0.8em;
+ margin-bottom: 0.8em;
+}
+div.hdlist tr {
+ padding-bottom: 15px;
+}
+dt.hdlist1.strong, td.hdlist1.strong {
+ font-weight: bold;
+}
+td.hdlist1 {
+ vertical-align: top;
+ font-style: normal;
+ padding-right: 0.8em;
+ color: navy;
+}
+td.hdlist2 {
+ vertical-align: top;
+}
+div.hdlist.compact tr {
+ margin: 0;
+ padding-bottom: 0;
+}
+
+.comment {
+ background: yellow;
+}
+
+.footnote, .footnoteref {
+ font-size: 0.8em;
+}
+
+span.footnote, span.footnoteref {
+ vertical-align: super;
+}
+
+#footnotes {
+ margin: 20px 0 20px 0;
+ padding: 7px 0 0 0;
+}
+
+#footnotes div.footnote {
+ margin: 0 0 5px 0;
+}
+
+#footnotes hr {
+ border: none;
+ border-top: 1px solid silver;
+ height: 1px;
+ text-align: left;
+ margin-left: 0;
+ width: 20%;
+ min-width: 100px;
+}
+
+div.colist td {
+ padding-right: 0.5em;
+ padding-bottom: 0.3em;
+ vertical-align: top;
+}
+div.colist td img {
+ margin-top: 0.3em;
+}
+
+@media print {
+ #footer-badges { display: none; }
+}
+
+#toc {
+ margin-bottom: 2.5em;
+}
+
+#toctitle {
+ color: #527bbd;
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 1.0em;
+ margin-bottom: 0.1em;
+}
+
+div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+div.toclevel2 {
+ margin-left: 2em;
+ font-size: 0.9em;
+}
+div.toclevel3 {
+ margin-left: 4em;
+ font-size: 0.9em;
+}
+div.toclevel4 {
+ margin-left: 6em;
+ font-size: 0.9em;
+}
+
+span.aqua { color: aqua; }
+span.black { color: black; }
+span.blue { color: blue; }
+span.fuchsia { color: fuchsia; }
+span.gray { color: gray; }
+span.green { color: green; }
+span.lime { color: lime; }
+span.maroon { color: maroon; }
+span.navy { color: navy; }
+span.olive { color: olive; }
+span.purple { color: purple; }
+span.red { color: red; }
+span.silver { color: silver; }
+span.teal { color: teal; }
+span.white { color: white; }
+span.yellow { color: yellow; }
+
+span.aqua-background { background: aqua; }
+span.black-background { background: black; }
+span.blue-background { background: blue; }
+span.fuchsia-background { background: fuchsia; }
+span.gray-background { background: gray; }
+span.green-background { background: green; }
+span.lime-background { background: lime; }
+span.maroon-background { background: maroon; }
+span.navy-background { background: navy; }
+span.olive-background { background: olive; }
+span.purple-background { background: purple; }
+span.red-background { background: red; }
+span.silver-background { background: silver; }
+span.teal-background { background: teal; }
+span.white-background { background: white; }
+span.yellow-background { background: yellow; }
+
+span.big { font-size: 2em; }
+span.small { font-size: 0.6em; }
+
+span.underline { text-decoration: underline; }
+span.overline { text-decoration: overline; }
+span.line-through { text-decoration: line-through; }
+
+div.unbreakable { page-break-inside: avoid; }
+
+
+/*
+ * xhtml11 specific
+ *
+ * */
+
+div.tableblock {
+ margin-top: 1.0em;
+ margin-bottom: 1.5em;
+}
+div.tableblock > table {
+ border: 3px solid #527bbd;
+}
+thead, p.table.header {
+ font-weight: bold;
+ color: #527bbd;
+}
+p.table {
+ margin-top: 0;
+}
+/* Because the table frame attribute is overriden by CSS in most browsers. */
+div.tableblock > table[frame="void"] {
+ border-style: none;
+}
+div.tableblock > table[frame="hsides"] {
+ border-left-style: none;
+ border-right-style: none;
+}
+div.tableblock > table[frame="vsides"] {
+ border-top-style: none;
+ border-bottom-style: none;
+}
+
+
+/*
+ * html5 specific
+ *
+ * */
+
+table.tableblock {
+ margin-top: 1.0em;
+ margin-bottom: 1.5em;
+}
+thead, p.tableblock.header {
+ font-weight: bold;
+ color: #527bbd;
+}
+p.tableblock {
+ margin-top: 0;
+}
+table.tableblock {
+ border-width: 3px;
+ border-spacing: 0px;
+ border-style: solid;
+ border-color: #527bbd;
+ border-collapse: collapse;
+}
+th.tableblock, td.tableblock {
+ border-width: 1px;
+ padding: 4px;
+ border-style: solid;
+ border-color: #527bbd;
+}
+
+table.tableblock.frame-topbot {
+ border-left-style: hidden;
+ border-right-style: hidden;
+}
+table.tableblock.frame-sides {
+ border-top-style: hidden;
+ border-bottom-style: hidden;
+}
+table.tableblock.frame-none {
+ border-style: hidden;
+}
+
+th.tableblock.halign-left, td.tableblock.halign-left {
+ text-align: left;
+}
+th.tableblock.halign-center, td.tableblock.halign-center {
+ text-align: center;
+}
+th.tableblock.halign-right, td.tableblock.halign-right {
+ text-align: right;
+}
+
+th.tableblock.valign-top, td.tableblock.valign-top {
+ vertical-align: top;
+}
+th.tableblock.valign-middle, td.tableblock.valign-middle {
+ vertical-align: middle;
+}
+th.tableblock.valign-bottom, td.tableblock.valign-bottom {
+ vertical-align: bottom;
+}
+
+
+/*
+ * manpage specific
+ *
+ * */
+
+body.manpage h1 {
+ padding-top: 0.5em;
+ padding-bottom: 0.5em;
+ border-top: 2px solid silver;
+ border-bottom: 2px solid silver;
+}
+body.manpage h2 {
+ border-style: none;
+}
+body.manpage div.sectionbody {
+ margin-left: 3em;
+}
+
+@media print {
+ body.manpage div#toc { display: none; }
+}
+
+
+</style>
+<script type="text/javascript">
+/*<+'])');
+ // Function that scans the DOM tree for header elements (the DOM2
+ // nodeIterator API would be a better technique but not supported by all
+ // browsers).
+ var iterate = function (el) {
+ for (var i = el.firstChild; i != null; i = i.nextSibling) {
+ if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
+ var mo = re.exec(i.tagName);
+ if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
+ result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
+ }
+ iterate(i);
+ }
+ }
+ }
+ iterate(el);
+ return result;
+ }
+
+ var toc = document.getElementById("toc");
+ if (!toc) {
+ return;
+ }
+
+ // Delete existing TOC entries in case we're reloading the TOC.
+ var tocEntriesToRemove = [];
+ var i;
+ for (i = 0; i < toc.childNodes.length; i++) {
+ var entry = toc.childNodes[i];
+ if (entry.nodeName.toLowerCase() == 'div'
+ && entry.getAttribute("class")
+ && entry.getAttribute("class").match(/^toclevel/))
+ tocEntriesToRemove.push(entry);
+ }
+ for (i = 0; i < tocEntriesToRemove.length; i++) {
+ toc.removeChild(tocEntriesToRemove[i]);
+ }
+
+ // Rebuild TOC entries.
+ var entries = tocEntries(document.getElementById("content"), toclevels);
+ for (var i = 0; i < entries.length; ++i) {
+ var entry = entries[i];
+ if (entry.element.id == "")
+ entry.element.id = "_toc_" + i;
+ var a = document.createElement("a");
+ a.href = "#" + entry.element.id;
+ a.appendChild(document.createTextNode(entry.text));
+ var div = document.createElement("div");
+ div.appendChild(a);
+ div.className = "toclevel" + entry.toclevel;
+ toc.appendChild(div);
+ }
+ if (entries.length == 0)
+ toc.parentNode.removeChild(toc);
+},
+
+
+/////////////////////////////////////////////////////////////////////
+// Footnotes generator
+/////////////////////////////////////////////////////////////////////
+
+/* Based on footnote generation code from:
+ * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
+ */
+
+footnotes: function () {
+ // Delete existing footnote entries in case we're reloading the footnodes.
+ var i;
+ var noteholder = document.getElementById("footnotes");
+ if (!noteholder) {
+ return;
+ }
+ var entriesToRemove = [];
+ for (i = 0; i < noteholder.childNodes.length; i++) {
+ var entry = noteholder.childNodes[i];
+ if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
+ entriesToRemove.push(entry);
+ }
+ for (i = 0; i < entriesToRemove.length; i++) {
+ noteholder.removeChild(entriesToRemove[i]);
+ }
+
+ // Rebuild footnote entries.
+ var cont = document.getElementById("content");
+ var spans = cont.getElementsByTagName("span");
+ var refs = {};
+ var n = 0;
+ for (i=0; i<spans.length; i++) {
+ if (spans[i].className == "footnote") {
+ n++;
+ var note = spans[i].getAttribute("data-note");
+ if (!note) {
+ // Use [\s\S] in place of . so multi-line matches work.
+ // Because JavaScript has no s (dotall) regex flag.
+ note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
+ spans[i].innerHTML =
+ "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
+ "' title='View footnote' class='footnote'>" + n + "</a>]";
+ spans[i].setAttribute("data-note", note);
+ }
+ noteholder.innerHTML +=
+ "<div class='footnote' id='_footnote_" + n + "'>" +
+ "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
+ n + "</a>. " + note + "</div>";
+ var id =spans[i].getAttribute("id");
+ if (id != null) refs["#"+id] = n;
+ }
+ }
+ if (n == 0)
+ noteholder.parentNode.removeChild(noteholder);
+ else {
+ // Process footnoterefs.
+ for (i=0; i<spans.length; i++) {
+ if (spans[i].className == "footnoteref") {
+ var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
+ href = href.match(/#.*/)[0]; // Because IE return full URL.
+ n = refs[href];
+ spans[i].innerHTML =
+ "[<a href='#_footnote_" + n +
+ "' title='View footnote' class='footnote'>" + n + "</a>]";
+ }
+ }
+ }
+},
+
+install: function(toclevels) {
+ var timerId;
+
+ function reinstall() {
+ asciidoc.footnotes();
+ if (toclevels) {
+ asciidoc.toc(toclevels);
+ }
+ }
+
+ function reinstallAndRemoveTimer() {
+ clearInterval(timerId);
+ reinstall();
+ }
+
+ timerId = setInterval(reinstall, 500);
+ if (document.addEventListener)
+ document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
+ else
+ window.onload = reinstallAndRemoveTimer;
+}
+
+}
+asciidoc.install();
+/*]]>*/
+</script>
+</head>
+<body class="manpage">
+<div id="header">
+<h1>
+fvwm-crystal(1) Manual Page
+</h1>
+<h2>NAME</h2>
+<div class="sectionbody">
+<p>fvwm-crystal -
+ an easy to use, eye-candy but also powerful desktop environment for GNU/Linux or other Unix-like operating systems.
+</p>
+</div>
+</div>
+<div id="content">
+<div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>None</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><strong>FVWM-Crystal</strong> aims to be an easy to use, eye-candy but also powerful desktop environment based on the F? Virtual Window Manager (FVWM). It uses following programs: FVWM as a window manager and "main core", icons on the desktop with support for more than 10 different file managers and custom commands (with optional Nautilus or ROX-Filer support), different terminal emulators inclusive xterm, aterm, mrxvt or urxvt, different music and medias players inclusive MPD, XMMS2 or MPlayer (there’s built-in support for controlling these programs, and several other tools for different functions, like setting a wallpaper or making screen shots. Fvwm-Crystal provide some unique features like the ability to bring in full screen virtually any application, and to flow through the full-screened applications and the desktop. In this document you will find a general description of <strong>FVWM-Crystal</strong>, how to begin with it and how to customize it.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_usage">USAGE</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_first_start">First Start</h3>
+<div class="paragraph"><p><strong>FVWM-Crystal</strong> checks while your first login if <code>~/.fvwm-crystal</code> exist and if old preferences must be converted to the new Fvwm InfoStore variables. In all cases, it should just start.</p></div>
+<div class="paragraph"><p><strong>FVWM-Crystal</strong> will also check your locale and create the XDG localized user directories if they don’t exist. Those directories are common to most modern OS and are used to store dedicated files. As example <code>$HOME/Music</code>, <code>$HOME/Documents</code> and <code>$HOME/Pictures</code>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_initial_media_player_setup">Initial Media Player Setup</h3>
+<div class="paragraph"><p>MPlayer is the default media player. A help screen can pop-up and show you how to setup the Media directories preferences, which tell FVWM-Crystal where your music and movie files are. You can do it now or later, but it must be done before to use the play-lists features found in the Music menu (or button).</p></div>
+<div class="paragraph"><p>For that, edit the file <code>~/.fvwm-crystal/preferences/MediaDirectories</code>:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>audio $HOME/Music
+video $HOME/Video
+cdrom /dev/cdrom0
+dvd /dev/cdrom1</code></pre>
+</div></div>
+<div class="paragraph"><p>You can put as many lines you need. Each line have the following format:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>type path</code></pre>
+</div></div>
+<div class="paragraph"><p>where <strong>type</strong> is one of [<code>audio</code> <code>video</code> <code>cdrom</code> <code>dvd</code>]
+and <strong>path</strong> is the <code>full path</code> to a directory or a device.
+Devices are used only for <code>cd</code> and <code>dvd</code>.
+Note that all players doesn’t support all the provided features. Their respective menus will be adjusted accordingly.</p></div>
+<div class="paragraph"><p>As example, you can have:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>audio /home/name/Music
+viedo /home/name/Video
+audio /mnt/work/Music
+video /mnt/usb/Video
+dvd /dev/cdrom</code></pre>
+</div></div>
+<div class="paragraph"><p>When you are done, save the file. You can load the control for your preferred player from the preferences menu</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>Crystal -> Music -> Player -> Music player</code></pre>
+</div></div>
+<div class="paragraph"><p>or from the menu on the first music button.</p></div>
+<div class="paragraph"><p>In the same menu, you will find <code>Recreate the playlists</code>. This script will scan the paths pointed by the MediaDirectories preference file, and create the play-lists into <code>$HOME/.fvwm-crystal/Playlists</code>. They will be separated into an Audio and a Video part. We can cal them the Crystal play-lists. Don’t edit those files, all your changes will be lost the next time you run <code>Recreate the playlists</code>. Instead, 2 other directories will be created: <code>$HOME/Playlists/Audio</code> and <code>$HOME/Playlists/Video</code>. They are the User play-lists.</p></div>
+<div class="paragraph"><p>In the same Music menu, the play-lists operation are grouped. You can of course load them into the selected player. <code>Copy playlist</code> will copy the selected play-list from the Crystal play-lists to the User play-lists. <code>Remove playlist</code> will remove the selected play-lists from the User play-lists. Some players provide they own play-lists management system, FVWM-Crystal try to support them as well.</p></div>
+<div class="paragraph"><p>Some supported players must be setup before FVWM-Crystal can use them. For that, please refer to their respective documentation. If you have a DVB card, please refer also to the linuxtv.org V4L-DVB Wiki at <a href="http://linuxtv.org/wiki/index.php/Main_Page">http://linuxtv.org/wiki/index.php/Main_Page</a>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_desktop_organisation">Desktop Organisation</h3>
+<div class="paragraph"><p>17 different desktop layouts, named recipes, are available.</p></div>
+<div class="paragraph"><p>Some are very simple and provide very few decorations. Others provide many buttons and decorations. A few of them mimic existing OS, like Nebulae which loosely mimic Windows or Amiga which mimic the Amiga OS.</p></div>
+<div class="paragraph"><p>You can change them via Fvwm-Crystal system menu</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>Preferences -> Recipes -> System</code></pre>
+</div></div>
+<div class="paragraph"><p>The other preferences apply to all recipes and are independent from each others.
+By example, you can choose to have desktop icons showing the XDG user directories and the mounted partitions, and to not have applications icons.</p></div>
+<div class="paragraph"><p>It is 2 menus, the system menu available with <strong>Alt + Win_R</strong> (Meta + Windows Left) and the application menu available with <strong>Alt + Menu</strong> (Meta + a "menu" key). A menu can also be available by holding a <strong>Left click</strong> on the root window (the desktop) if selected in System → Preferences → Desktop menu (On by default). The content of that menu depend on the recipe in use.</p></div>
+<div class="sect3">
+<h4 id="_decorations_common_to_all_recipes">Decorations common to all recipes</h4>
+<div class="paragraph"><p>Not all recipes use all followings decorations called buttons, but they can be used in any recipe, inclusive your own ones.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+<em>The "Crystal" Button</em>
+</dt>
+<dd>
+<div class="paragraph"><p>or "FvwmButtons-MainMenu" is the little button with a diamond.</p></div>
+<div class="paragraph"><p>There are some mouse bindings available:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+left clicking open the system menu
+</p>
+</li>
+<li>
+<p>
+middle clicking change the wallpaper randomly
+</p>
+</li>
+<li>
+<p>
+right clicking on some recipes open the applications menu
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>The Amiga recipe is different:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+left clicking shift the top bar to a menu bar and back
+</p>
+</li>
+<li>
+<p>
+middle clicking change the wallpaper randomly
+</p>
+</li>
+<li>
+<p>
+right clicking open the system menu
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>When the button is located at the top left corner:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+mouse wheeling will change the screen resolution
+</p>
+</li>
+</ul></div>
+</dd>
+<dt class="hdlist1">
+<em>The Media Buttons</em>
+</dt>
+<dd>
+<div class="paragraph"><p>They are 4 grouped media buttons - FvwmButtons-Music - providing controls and menus for the supported media players and mixers. For a description of their bindings, consult <strong>man MouseBindings</strong> and <strong>man KeyboardBindings</strong>, or the html documentation.</p></div>
+<div class="paragraph"><p>The same functionalities are provided by the Music menu, which is located in the System menu.</p></div>
+<div class="paragraph"><p>The supported media players are <code>alsaplayer</code>, <code>audacious</code>, <code>cdcd</code>, <code>cmus</code>, <code>mocp</code>, <code>mpd</code>, <code>mplayer</code>, <code>mplayer2</code>, <code>quodlibet</code> and <code>xmms2</code>.</p></div>
+<div class="paragraph"><p>The supported audio mixers are <code>alsamixer</code> and <code>aumix</code>, plus the mixers of the players. <code>QJackCTL</code> is also supported.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+left clicking on the first media button will open a menu.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In it, <code>Music player</code> is where you choose the player and can start it. <code>Recreate the playlists</code> will scan your music and video files and create the play-lists for you. For that, it will use the preferences file you edited in the section "First Start". It is also a mixer preferences menu where you can choose the mixer and the sound card.</p></div>
+<div class="paragraph"><p>Each player have its own features set, and the Music menu and functions will change accordingly.</p></div>
+<div class="paragraph"><p>As example, with <strong>cdcd</strong> you have a cd player and you will be able to control it, when with <strong>mplayer</strong>, you have an universal media player, and FVWM-Crystal will even recognize if you have a DVB card and use it. Basic stream capture is enabled and use the standard <em>C</em> MPlayer key binding. See <strong>man mplayer</strong>. This will create a stream dump in $HOME. That file will be usable only with MPEG sources, and it can be edited with applications like <code>Kino</code>.</p></div>
+</dd>
+<dt class="hdlist1">
+<em>The Application Panel</em>
+</dt>
+<dd>
+<div class="paragraph"><p>It is an auto generated panel which provide one button for each <strong>FreeDesktop</strong> menu main category. The icon of each button is the icon of the preferred application of that category. The mouse bindings available are:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+left clicking open the application menu of the category
+</p>
+</li>
+<li>
+<p>
+middle clicking on some recipes launch the second preferred application
+</p>
+</li>
+<li>
+<p>
+right clicking launch the preferred application
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>These menus have full support for the additional FreeDesktop categories, which mean much less modifications will be needed in comparison with many other desktops. And last but not least, your modifications will never be lost. It is why at the first place I begun with Crystal and I will keep it that way. See <strong>man ApplicationDatabase</strong> for how to customize the application menu (the examples are at the end).</p></div>
+<div class="paragraph"><p>More: the files in the applications database are scripts. You can put anything you want into them. You will find them into <code>$prefix/share/fvwm-crystal/fvwm/Applications</code> and <code>$HOME/.fvwm-crystal/Applications</code>, and can copy them fro this first location to the second one. The files in the second path will take the precedence. The same apply for the icons directory.</p></div>
+<div class="paragraph"><p>The same database is used to generate the application menu available with the system menu on some recipes, and with the Alt+Menu key binding.</p></div>
+<div class="paragraph"><p>The application database provided by <code>FVWM_Crystal</code> contain a large set of menu entries and application icons. You can generate extra database menu entries and icons from the preferences menu: <code>Diamond → Preferences → Generate application menu</code>. This will populate <code>$HOME/.fvwm-crystal/Applications</code> and <code>$HOME/.fvwm-crystal/icons</code>.</p></div>
+<div class="paragraph"><p>The 2 first time you run this script, it will copy 2 preferences files and show help messages.</p></div>
+<div class="paragraph"><p>Those files are <code>$HOME/.fvwm-crystal/preferences/IconDirs</code> and <code>$HOME/.fvwm-crystal/preferences/DesktopDirs</code>. They must contain the full path to where the icon and desktop files provided by the applications are stored, typically something like <code>/usr/share/icons</code> and <code>/usr/share/pixmaps</code> for the icons, and <code>/usr/share/applications</code> and <code>/usr/share/applications/kde4</code> for the desktop files. The 2 preference files ar...
[truncated message content] |
