#-------------------------------------------------------------------
fixed options
u can enable it with --enable-fixeditems
u must have @after_share@/fixed directory and it can contain:
   feels/       - merge feels in this dir with user's local ones
   looks/       - dtto.
   backgrounds/ - dtto.
   start/       - start menu entries.

 It all works all okay with one exception - when one's using
 ordered directories (ie. 2_Applications) and in /u/s/a/f/s/ is
 Applications for example (unordered directory), those two won't get
 merged. 

#-------------------------------------------------------------------
start tree (startmenu)
Directories and/or files can now be prefixed with a <number>_, which
explicitly states their order in the menu. AS an example
~/G/L/A/s/0_My-Z-Directory
~/G/L/A/s/1_My-z-File
~/G/L/A/s/2_My-A-Directory
~/G/L/A/s/3_My-R-File
etc...
order.
Entry example:
  Exec "Name to be in startmenu" exec application &
  MiniPixmap "some-mini.xpm"
a <#>_nop file:
1) with - Nop " " - will produce a space at # point in the vertical list
2) with - Nop ""  - will produce a horizontal line at # poin in list


-------------------------------------------------------------------
feel:

switching among windows
  AutoReverse 0:    default switching among the windows (circulating in
		    one direction)
  AutoReverse 1:    #1->#2->#3->#4 and then #4->#3->#2->#1
  AutoReverse 2:    #1->#2->#3->#4 and then #4->#1->#3->#2 etc. (as in
		    wind*ze 9x)
  AutoReverse		<number>

window switching through desks?
  AutoTabThroughDesks

Support Motif window manager function hints
  MWMFunctionHints

Support Motif window manager decoration hints
  MWMDecorHints

Allow overriding of Motif function hints
 MWMHintOverride

-------------------------------------------------------------------
look:
TitleButtonStyle	0	- make a space at sides of the title bar
TitleButtonStyle	1	- don't make a space at sides of the title
				  bar  (like in WindowMaker)

define the number of pixels among titlebar buttons
  TitleButtonSpacing	<number>

Do you want minipixmaps in root menu ?
[This was previously in the feel.file]
  MenuMiniPixmaps

Sort Start menu entries by ... 1=alphabetical order, 0=date (default)
[This was previously in the feel.file]
  StartMenuSortMode		<number>

0 Draws no borders;
1 Draws borders around each menu_item; and
2 Draws border around both menu_title and main menu body
  DrawMenuBorders			<number>

-------------------------------------------------------------------
pager:
next line turns on balloons
  Balloons
color and font spec are standard
  BalloonFore			<color>
  BalloonBack			<color>
  BalloonFont			<font>
  BalloonBorderColor		<color>
width is in pixels, and is a non-negative integer
  BalloonBorderWidth		<width>
offset is in pixels, and is an integer
(offset < 0)  => balloon will be above client window (ie, button)
(offset >= 0) => balloon will be below client window (ie, button)
  BalloonYOffset            	<offset>
delay is in milliseconds, and can be any non-negative integer
  BalloonDelay			<milliseconds>

-------------------------------------------------------------------
wharf:
next line turns on balloons
  *WharfBalloons
color and font spec are standard
  *WharfBalloonFore               <color>
  *WharfBalloonBack               <color>
  *WharfBalloonFont               <font>
  *WharfBalloonBorderColor        <color>
width is in pixels, and is a non-negative integer
  *WharfBalloonBorderWidth        <width>
offset is in pixels, and is an integer
(offset < 0)  => balloon will be above client window (ie, button)
(offset >= 0) => balloon will be below client window (ie, button)
  *WharfBalloonYOffset            <offset>
delay is in milliseconds, and can be any non-negative integer
  *WharfBalloonDelay              <milliseconds>

steps can be any non-negative integer
  *WharfAnimateSteps      <steps>
  *WharfAnimateStepsMain  <steps>

delay is in microseconds, and can be any non-negative integer
  *WharfAnimateDelay      <delay>

Swallow vs. MaxSwallow:
version 1.0 - version 1.4.5.55N
  Swallow:    assume swallowed window is 48x48, and place it accordingly
  MaxSwallow: if swallowed window is larger than 55x57, it is resized to
	      55x57

version 1.4.5.55N2 - version 1.5pre4
  Swallow:    (same as 1.0)
  MaxSwallow: if swallowed window is larger than button size (usually 64x64) 
              it is resized to the button size

version 1.5pre6 - current
  Swallow:    (same as 1.5pre4 MaxSwallow)
  MaxSwallow: if swallowed window is larger than button size (usually 64x64),
              the button is resized to fit the swallowed window

The Size keyword specifies the size of a wharf button
<width> and <height> are non-negative integers
  *Wharf label pixmap Size <width> <height>

On the subject of button sizes, here's a brief description of how Wharf 
chooses the size of a button, in decreasing order of precedence:
  1. if the Size keyword is specified, use that
  2. if MaxSwallow is used, use the size of the swallowed window
  3. if WharfPixmap is given, use the size of the pixmap
  4. use 64x64

If swallowed Module is larger than button size (usually 64x64),
the button is resized to fit the swallowed Module [ Currently only
Pager is a feasible Swallowable Module :)]
  MaxSwallowModule

In case you haven't noticed, Wharf now supports Folders within Folders.

-------------------------------------------------------------------
zharf:
next line turns on balloons
  *ZharfBalloons

color and font spec are standard
  *ZharfBalloonFore               <color>
  *ZharfBalloonBack               <color>
  *ZharfBalloonFont               <font>
  *ZharfBalloonBorderColor        <color>

width is in pixels, and is a non-negative integer
  *ZharfBalloonBorderWidth        <width>

offset is in pixels, and is an integer
(offset < 0)  => balloon will be above client window (ie, button)
(offset >= 0) => balloon will be below client window (ie, button)
  *ZharfBalloonYOffset            <offset>

delay is in milliseconds, and can be any non-negative integer
  *ZharfBalloonDelay              <milliseconds>


version 1.5beta4 - current
New Pager options :
defines XPM or JPEG image to be displayed in Pager window for
specified desk.
  *PagerImage  <desk#> <image_filename>

Defines image to be displayed in Root for specified desk. XPM, JPEG, or
PNG images supported internally( unless PagerXImageLoaderArgs are
specified ), other formats uses external image loader, like xli, or xv.
  *PagerDesktopImage  <desk#> <image_filename>

Defines arguments to be passed to external image loader, when showing Root
background. 
!!!!!!! This Option will disable inernal support for XPM and JPEG !!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
if desk# is ommited args will have effect for all desks, but will not
disable internal JPEG and XPM support
  *PagerXImageLoaderArgs  [<desk#>] <image loader args without prog name>

When image is dislayed on root using external app this option will let
you cache image in memory, to not invoke this app every time you switch
desks, saving lots of time. This feature will not work with some user
application, specificaly KDE desktop it will also restore all icons when
you switch desks first time. Use it with care and at your own risk
  *PagerFastBackground <desk#> <yes/no> [<tile_height> [<tile_width>]]

This option will let you reduce the number of colors used for background
image, when loading JPEG or XPM internally. Implementation of this depends
on image library, therefore you not always get what you want :)
  MaxBackgroundColors <number_of_colors>

1.5beta4 patch07

added configure option --enable-pagerbackground=yes/no to enable/disable
all background support in Pager. Default is 'yes' (background support
enabled)

1.5beta5 patch10

added configure option --enable-png=yes/no. Default is "yes".
added Pager config option PagerHideInactiveLabels. See man pages.
added Pager config option PagerLabelBelowDesk. See man pages.

1.5beta5 patch13 [17]

added configure option --enable-staticlibs=yes/no. Default is "yes".
This will force AS to be built with libafterstep, libasimage, libWidgets
statically linked. By default all libs are linked statically.

1.5beta5 patch14

Added option *PagerFastStartup to pager configuration.
This will force Pager to inform Afterstep that it is started, right 
after the first desk's background is loaded. Pager will also set the
global Atom to background Pixmap, so that Eterm can work nicely, with 
transparency emulation.
This option should speedup AS startup, when different pictures are used
for different desks.

1.5beta5 patch16

configure options --with-gnustep-lib and --with-afterdir where changed
so now  you need to supply patch within gnustep dir and within gnusteplib
dir respectevely ( like --with-gnustep-lib=Library
--with-afterdir=AfterStep )

1.5beta5 patch21

added:
ViewportX x, ViewportY y
styles to database - allowing to do flexible StartOnPage
stuff. It will move screen to the specifyed pos on desk, before placing 
the window.

1.7.0 patch 10

added following Pager options :
PagerDecoration option - possible values :
   DeskBorderWidth #  - border width between desks
   NoPageSeparator    - removes lines separating one page from another
   NoSelection        - removes frame surrounding selected page 
   GridColor <color>  - defines color of page separating grid and desk 
                        borders
 Usage : 
 *PagerDecoration  DeskBorderWidth 1,NoPageSeparator,NoSelection,GridColor green
 ( you can use any combination of options )

*PagerHilightBorders
Tells the pager to hilight the border of focused window as well as its
label


1.7.0 patch 19

added following Pager option :

*PagerSetRootOnStartup 
to make it show 
root background on startup - before notification from AfterStep
about current desk. This is needed if aterm is started from autoexec
or even before AfterStep with transparent option.
