File: README

package info (click to toggle)
fvwmconf 0.19-3
  • links: PTS
  • area: main
  • in suites: slink
  • size: 808 kB
  • ctags: 406
  • sloc: perl: 6,191; makefile: 47; sh: 2
file content (152 lines) | stat: -rw-r--r-- 5,083 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
Installation Instructions for 

FvwmConf 
VERSION 0.19  Wed, 15 Apr 1998 02:41:30 -0700    

Copyright 1997 John Lapeyre
This software is distributed under the terms of the
GNU GENERAL PUBLIC LICENSE.  See the file 'GPL' 
in this directory for futher information.


These are generic installation instructions. If you
have the debian package installed, only some of the following 
applies (eg, install directories will be different).

This is a module for fvwm2 written in perl
using the Perl/Tk module.  It requires Perl/Tk.
To make best use of the image handling features, you
will also need the netpbm package  or the imagemagick suite
(available from sunsite, etc. and with many linux distributions.)
Its not clear yet which works best--- probably imagemagick.  It
seems more robust at this point.  It gives fvwmconf support for 
more image types.  fvwmconf will prefer  imagemagick  if both are
available. 

  What is an fvwm2 Module ?
A module is a helper program for fvwm2.  To use a module you must
have fvmw2 call it. You cannot call it from the command line. (This is
because the two programs need to communicate.)  So you need to put a line
in your .fvwm2rc file which calls the module.  Most example .fvwm2rc files
have lines calling other modules. (eg, the FvwmPager is a module)

-----------------------------------------------

Unpack fvwmconf.xxx.tar.gz   somewhere.

Enter the directory 

cd fvwmconf.xxx

The script  ./install has lines near the top to
put the support files  in 
/usr/local/lib/fvwmconf
and to put the module FvwmConf in 
/usr/local/lib/X11/fvwm2   .

Change this if you want to put them somewhere else.
That is edit the two lines in the file ./install before you run it.

Run the install script with the command

perl install

This should install the module and support files.

If you want just build the FvwmConf file to check if things
were written correctly use

perl install build 

This will read the file FvwmConf.in and change some things and
write FvwmConf.

The install script should locate the perl interpreter and
change the first line of FvwmConf accordingly.

'perl install rc' will create a sample .fvwm2rc file for you
to use. Alternatively you can add a couple of lines to 
your existing .fvwm2rc (see below).


FvwmConf is an fvwm2 module. This means that it must be started
from within fvwm2 , not from the command line. See below.

If do not have ~/.fvwmconf/,  FvwmConf will create it for you ,
and put the neccessary things in it.


--------------------------------------------------
Modifing  your .fvwm2rc


   fvwmconf does not handle menus and functions yet.  But you can 
   remove the other commands (back it up first !) from your .fvwm2rc and
   add the following. (Don't need the comments !)


	# add .fvwmconf/lib to your module path.  Your standard modules
	# may be in a different place than /usr/X11R6/lib/X11/fvwm2 .
	# this first path is not neccessary if you have FvwmConf
	# installed in one of the other two paths
	# substitue your home directory for USERHOME

	# changing the module path may or may not be neccesary, depending on 
        # where you installed things. The debian distribution does not need to 
	# change the module path.

	ModulePath USERHOME/.fvwmconf/lib:\
	/usr/X11R6/lib/X11/fvwm2:/usr/local/lib/X11/fvwm2

	# fvwmconf uses full pathnames for pixmaps so don't worry about that.

	# put this in some menu .
	+	"FvwmConf"  FvwmConf

	# If you want to be able to use a configuration that you made with  
	# fvwmconf without running it again, use the 'Write' function in 
	# fvwmconf.  It will write to ~/.com.fvwm  .  Add this line so that
	# this file will always be read, even if you choose not to run fvwmconf.
	# alternatively you can put FvwmConf in your InitFunction.

	Read .com.fvwm
--------------------------------------------------------------



If you downloaded some image files , you can untar them in 
your home directory.
The gif and xpm tar files often contain duplicates of images in 
the two formats. 
I have switched to displaying ppms, so having ppms will be fastest, and
you must have netpbm or imagemagick(preferred) to browse images.


-----------------------------------------------------------------------

A Note On Colormaps.

Its easy to eat up your colormap using fvwmconf.

If you run at a lower resolution and use a larger colormap, you won't run
out of colors.  On linux, the X Server gets a 16bpp option.  How to give the 
argument is hardware specific.


-----------------------------------------------------------------------

John Lapeyre <lapeyre@physics.arizona.edu>

Please send me mail with any comment or suggestion or bug, etc,
or even if you don't have anything to say.  I would appreciate
knowing which Unix systems it works on and if there are installation
problems.


#######################################################
Some code was taken from  X11::Fvwm by
Randy J. Ray <randy@byz.org> .
I may simply use his module in the future, but
a the present time it is more than the configuration module needs. 
I also don't know the fvwm2 API