aboutsummaryrefslogtreecommitdiff
path: root/doc/asciidoc/fluxbox-style.1
diff options
context:
space:
mode:
authormathias <mathias>2006-10-27 07:02:14 (GMT)
committermathias <mathias>2006-10-27 07:02:14 (GMT)
commit4c6378564ddee251734ddeab3a14ee100622857a (patch)
tree9232908a4fcc738b22d9e71a39172f2eca8c06c1 /doc/asciidoc/fluxbox-style.1
parent10082d821d6691f42a8d8ad6fa2e42e5b3f44edd (diff)
downloadfluxbox-4c6378564ddee251734ddeab3a14ee100622857a.zip
fluxbox-4c6378564ddee251734ddeab3a14ee100622857a.tar.bz2
small changes to the asciidoc-docs
Diffstat (limited to 'doc/asciidoc/fluxbox-style.1')
-rw-r--r--doc/asciidoc/fluxbox-style.1483
1 files changed, 483 insertions, 0 deletions
diff --git a/doc/asciidoc/fluxbox-style.1 b/doc/asciidoc/fluxbox-style.1
new file mode 100644
index 0000000..5aa4963
--- /dev/null
+++ b/doc/asciidoc/fluxbox-style.1
@@ -0,0 +1,483 @@
1.\"Generated by db2man.xsl. Don't modify this, modify the source.
2.de Sh \" Subsection
3.br
4.if t .Sp
5.ne 5
6.PP
7\fB\\$1\fR
8.PP
9..
10.de Sp \" Vertical space (when we can't use .PP)
11.if t .sp .5v
12.if n .sp
13..
14.de Ip \" List item
15.br
16.ie \\n(.$>=3 .ne \\$3
17.el .ne 3
18.IP "\\$1" \\$2
19..
20.TH "FLUXSTYLE" 1 "" "" ""
21.SH NAME
22fluxstyle \- A comprehensive look at styles/themes for fluxbox(1).
23.SH "SYNOPSIS"
24
25.SH "DESCRIPTION"
26
27
28What is a Style?
29
30
31Styles, sometimes referred to as Themes, are a graphical overlay for the fluxbox(1) window manager\&. If you wanted to get to know fluxbox, the styles would be the \fIlook\fR of the \fIlook and feel\fR\&.
32
33
34Styles are simple ASCII text files that tell fluxbox(1) how to generate the appearance of different components of the window manager\&. The default installation of fluxbox(1) is shipped with many classic examples that show a great deal of what one could do\&. To use one of the standard styles navigate to the \fISystem Styles\fR menu under your main fluxbox(1) menu\&.
35
36
37fluxbox(1) uses its own graphics class to render its images on the fly\&. By using styles you can determine, at a great level of configurability, what your desktop will look like\&. Since fluxbox(1) was derived from blackbox many often wonder if old themes will work on the latest releases of fluxbox(1)\&. Well they basically do, but you will have to tune them since the fluxbox(1) code has changed quite a bit since the initial grab\&.
38
39.SH "STRUCTURE"
40
41
42A style is made up of a few major components which then have their own sub\-directives\&. The major components are as follows:
43
44
45The \fIwindow\&.*\fR directives control the appearance of the window frames, window\&.tab\&.* controls the appearance of the window tabs, \fImenu\&.*\fR controls the appearance of the popup menu that you see when you right click on the desktop\&. \fItoolbar\&.*\fR is the bar you will see at the top or bottom of your screen\&. Finally the \fIslit\&.*\fR has options you can use to customize the appearance of the slit\&. However if you don't set the slit directives specifically, the slit's appearance is controlled by the toolbar directives instead\&.
46
47
48To understand how the style mechanism works, it is nice to know a little about how X11 resources work\&. X11 resources consist of a key and a value\&. The key is constructed of several smaller keys (sometimes referred to as children), delimited by a period (\&.)\&. Keys may also contain an asterisk (*) to serve as a wildcard, which means that one line of text will match several keys\&. This is useful for styles that are based on one or two colors\&.
49
50
51A more complete reference to this can be found in X(7), section \fIRESOURCES\fR\&.
52
53.SH "LOCATION"
54
55
56There are many places to store your styles, the most common is in your \fI~/\&.fluxbox/styles\fR directory\&. The initial installation will place the default styles in \fI/usr/share/fluxbox/styles\fR providing a basic usable configuration\&.
57
58
59When creating your own style, create a directory (normally the name of your style) in \fI~/\&.fluxbox/styles/\fR (If the \fIstyles\fR directory doesn't exist, create that also)\&. While there isn't an official structure, it is common to create a directory named after your style and place your pixmaps directory (if required) in there along with a file called theme\&.cfg (may also be named style\&.cfg)\&. This file is where you will construct your style using the components covered later in this manual page\&. An example of steps taken when beginning a style project of your own may look like:
60
61.nf
62$ cd
63$ mkdir \-p ~/\&.fluxbox/styles/YourStyle/pixmaps
64$ cd ~/\&.fluxbox/styles/YourStyle
65$ nano theme\&.cfg
66.fi
67
68
69Output of a packaged style should look like the following:
70
71.nf
72$ cd
73$ tar \-tjvf YourStyle\&.tar\&.bz2
74 \&.fluxbox/styles/YourStyle/theme\&.cfg
75 \&.fluxbox/styles/YourStyle/pixmaps
76 \&.fluxbox/styles/YourStyle/pixmaps/stick\&.xpm
77 \&.\&.\&.
78.fi
79
80
81Of course, all of these are just preferences, fluxbox(1) allows for the customization of many things, including how you handle your styles\&. Just remember, however, that if you plan to distribute your style you may find some community bickering if you don't follow practices\&. :)
82
83.SH "CREATING YOUR STYLE"
84
85
86As discussed above, fluxbox(1) allows you to configure its four main components: the toolbar, menus, slit and window decorations\&. Remember that you can customize the slit with its own directives, otherwise the slit will take the appearance of the toolbar\&.
87
88
89Here are some quick examples to illustrate basic syntax:
90
91.nf
92toolbar\&.clock\&.color: green
93.fi
94
95
96This sets the color resource of the toolbar clock to \fIgreen\fR\&. Another example:
97
98.nf
99menu*color: rgb:3/4/5
100.fi
101
102
103This sets the color resource of the menu and all of its \fIchildren\fR to `rgb:3/4/5'\&. (For a description of color names, see X(1)\&.) So this one also applies to \fImenu\&.title\&.color\fR and \fImenu\&.frame\&.color\fR\&. And with
104
105.nf
106*font: \-b&h\-lucida\-medium\-r\-normal\-*\-*\-140\-*
107.fi
108
109
110you set the font resource for all keys to this font name all at once (For information about the fonts installed on your system, you can use a program like xfontsel(1), gtkfontsel, or xlsfonts(1)\&.)
111
112
113In the last example you will notice the wildcard (*) before font\&. In a Fluxbox style you can set a value with a wildcard\&. The example means that every font in the style will be what is specified\&. You can do this with any component/value\&. For example if you wanted all of the text to be one color you would do:
114
115.nf
116*textColor: rgb:3/4/5
117.fi
118
119
120This means that you can setup a very simple style with very few properties\&. See the EXAMPLES below for an example of this in practice\&. fluxbox(1) also allows you to override wildcards in your style\&. Lets take our example above and add an override for the toolbar\&.clock\&.textColor component:
121
122.nf
123*textColor: rgb:3/4/5
124toolbar\&.clock\&.textColor: rgb:255/0/0
125.fi
126
127
128With that all of the text will be \fIrgb:3/4/5\fR except the toolbar clock text which will be \fIrgb:255/0/0\fR\&.
129
130
131Now what makes fluxbox(1) so spectacular is its ability to render textures on the fly\&. A texture is a fillpattern that you see on some styles\&. Texture descriptions are specified directly to the key that they should apply to, e\&.g\&.:
132
133.nf
134toolbar\&.clock: Raised Gradient Diagonal Bevel1
135toolbar\&.clock\&.color: rgb:8/6/4
136toolbar\&.clock\&.colorTo: rgb:4/3/2
137.fi
138
139
140Don't worry, we will explain what these mean\&. A texture description consists of up to five fields, which are as follows:
141
142.PP
143gives the component either a flat, raised or sunken appearance\&.
144
145.PP
146tells fluxbox(1) to draw either a solid color or a gradient texture\&.
147
148.PP
149Select one of these texture types\&. They only work when \fIGradient\fR is specified\&.
150
151.PP
152tells fluxbox(1) to interlace the texture (darken every other line)\&. This option is most commonly used with gradiented textures, but it also works in solid textures\&.
153
154.PP
155tells fluxbox(1) which type of bevel to use\&. Bevel1 is the default bevel\&. The shading is placed on the edge of the image\&. Bevel2 is an alternative\&. The shading is placed one pixel in from the edge of the image\&.
156
157
158Instead of a texture description, also the option \fIParentRelative\fR is available, which makes the component appear as a part of its parent, e\&.g\&. totally transparent\&.
159
160
161Or for even more possibilities Pixmap\&. If pixmap texture is specified (it might not be necessary on every occasion) the pixmap file is specified in a separate pixmap resource\&.
162
163.nf
164toolbar\&.clock: pixmap
165toolbar\&.clock\&.pixmap: clock_background\&.xpm
166.fi
167
168
169This feature might need some investigation, reports say that sometimes the resources color and colorTo must be set and then they may not be set\&.
170
171
172All gradiented textures are composed of two color values: the \fIcolor\fR and \fIcolorTo\fR resources\&. When \fIInterlaced\fR is used in \fISolid\fR mode, the \fIcolorTo\fR resource is used to find the interlacing color\&.
173
174.SH "A WORD ABOUT FONTS"
175
176
177We should comment about fonts before we move on to the complete component list\&. fluxbox(1) supports different options for text\&. These options currently include bold, halo and shadow\&. To set these do this: fontname\-size:options for any of the font components in the style file\&. For example:
178
179.nf
180menu\&.title\&.font: sans\-8:bold,shadow
181.fi
182
183
184The latest versions of fluxbox(1) (> 0\&.9\&.8) also support different values for these text options\&. The possibilities are as follows:
185
186.nf
187\-\-\-\-\-\-\-\-
188Shadow color=<colorname> offsetx=<integer> offsety=<integer> Halo color=<colorâ\\u20acname>
189\-\-\-\-\-\-\-\-
190.fi
191
192
193For the case of completeness, here are some real world examples:
194
195.nf
196*\&.font: Verdana\-10:bold,shadow:offsetx=2;offsety=4;color=green
197*\&.font: Verdana\-10:halo:color=blue
198.fi
199
200
201Of course this could all be placed on one line\&. Also note that for the offset options, negative integers are allowed\&.
202
203.SS "FONT PROBLEMS"
204
205
206If you have problems installing fonts or getting them to work, you should read the docs page at xfree\&.org\&. Here is a link to one of these: http://xfree\&.org/4\&.3\&.0/fonts2\&.html#3
207
208.SH "FULL COMPONENT LIST"
209
210
211Here is the exhaustive component list for fluxbox(1) styles\&. Each one is listed with their type of value required\&. Comments in a style file are preceded with an exclamation point (!) which we also use here so that these can be pasted into a new theme\&.cfg to be customized appropiately\&. Please note that in order to keep styles consistent it is often the practice of stylists to provide all of the theme\-items in their style file even if they are not used\&. This allows the user the ease of changing different components\&.
212
213.SH "WINDOW OPTIONS"
214
215
216Many, many things you can do with window design in fluxbox(1), below are your options\&. Have fun\&.
217
218.nf
219\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
220window\&.bevelWidth: <integer>
221window\&.borderColor: <color>
222window\&.borderWidth: <integer>
223window\&.button\&.focus: <texture type>
224window\&.button\&.focus\&.color: <color>
225window\&.button\&.focus\&.colorTo: <color>
226window\&.button\&.focus\&.picColor: <color>
227window\&.button\&.focus\&.pixmap: <filename>
228window\&.button\&.pressed: <texture type>
229window\&.button\&.pressed\&.color: <color>
230window\&.button\&.pressed\&.colorTo: <color>
231window\&.button\&.pressed\&.pixmap: <filename>
232window\&.button\&.unfocus: <texture type>
233window\&.button\&.unfocus\&.color: <color>
234window\&.button\&.unfocus\&.colorTo: <color>
235window\&.button\&.unfocus\&.picColor: <color>
236window\&.button\&.unfocus\&.pixmap: <filename>
237window\&.close\&.pixmap: <filename>
238window\&.close\&.pressed\&.pixmap: <filename>
239window\&.close\&.unfocus\&.pixmap: <filename>
240window\&.font: <font>
241window\&.frame\&.focusColor: <color>
242window\&.frame\&.unfocusColor: <color>
243window\&.grip\&.focus: <texture type>
244window\&.grip\&.focus\&.color: <color>
245window\&.grip\&.focus\&.colorTo: <color>
246window\&.grip\&.focus\&.pixmap: <filename>
247window\&.grip\&.unfocus: <texture type>
248window\&.grip\&.unfocus\&.color: <color>
249window\&.grip\&.unfocus\&.colorTo: <color>
250window\&.grip\&.unfocus\&.pixmap: <filename>
251window\&.handle\&.focus: <texture type>
252window\&.handle\&.focus\&.color: <color>
253window\&.handle\&.focus\&.colorTo: <color>
254window\&.handle\&.focus\&.pixmap: <filename>
255window\&.handle\&.unfocus: <texture type>
256window\&.handle\&.unfocus\&.color: <color>
257window\&.handle\&.unfocus\&.colorTo: <color>
258window\&.handle\&.unfocus\&.pixmap: <filename>
259window\&.handleWidth: <integer>
260window\&.iconify\&.pixmap: <filename>
261window\&.iconify\&.pressed\&.pixmap: <filename>
262window\&.iconify\&.unfocus\&.pixmap: <filename>
263window\&.justify: <{Left|Right|Center}>
264window\&.label\&.active: <texture type>
265window\&.label\&.active\&.textColor: <color>
266window\&.label\&.focus: <texture type>
267window\&.label\&.focus\&.color: <color>
268window\&.label\&.focus\&.colorTo: <color>
269window\&.label\&.focus\&.pixmap: <filename>
270window\&.label\&.unfocus: <texture type>
271window\&.label\&.unfocus\&.color: <color>
272window\&.label\&.unfocus\&.colorTo: <color>
273window\&.label\&.unfocus\&.pixmap: <filename>
274window\&.label\&.focus\&.textColor: <color>
275window\&.label\&.unfocus\&.textColor: <color>
276window\&.maximize\&.pixmap: <filename>
277window\&.maximize\&.pressed\&.pixmap: <filename>
278window\&.maximize\&.unfocus\&.pixmap: <filename>
279window\&.roundCorners: <{Top|Bottom}{Left|Right}>
280window\&.shade\&.pixmap: <filename>
281window\&.shade\&.pressed\&.pixmap: <filename>
282window\&.shade\&.unfocus\&.pixmap: <filename>
283window\&.stick\&.pixmap: <filename>
284window\&.stick\&.pressed\&.pixmap: <filename>
285window\&.stick\&.unfocus\&.pixmap: <filename>
286window\&.stuck\&.pixmap: <filename>
287window\&.stuck\&.unfocus\&.pixmap: <filename>
288window\&.title\&.focus: <texture type>
289window\&.title\&.focus\&.color: <color>
290window\&.title\&.focus\&.colorTo: <color>
291window\&.title\&.focus\&.pixmap: <filename>
292window\&.title\&.height: <integer>
293window\&.title\&.unfocus: <texture type>
294window\&.title\&.unfocus\&.color: <color>
295window\&.title\&.unfocus\&.colorTo: <color>
296window\&.title\&.unfocus\&.pixmap: <filename>
297\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
298.fi
299
300.SH "MENU OPTIONS"
301
302
303Everything you need to make your menu look pretty\&.
304
305.nf
306\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
307menu\&.bevelWidth: <integer>
308menu\&.borderColor: <color>
309menu\&.borderWidth: <integer>
310menu\&.bullet: <{empty|square|triangle|diamond}>
311menu\&.bullet\&.position: <{left|right}>
312menu\&.frame: <texture type>
313menu\&.frame\&.color: <color>
314menu\&.frame\&.colorTo: <color>
315menu\&.frame\&.disableColor: <color>
316menu\&.frame\&.font: <font>
317menu\&.frame\&.justify: <{Left|Right|Center}>
318menu\&.frame\&.pixmap: <filename>
319menu\&.frame\&.textColor: <color>
320menu\&.hilite: <texture type>
321menu\&.hilite\&.color: <color>
322menu\&.hilite\&.colorTo: <color>
323menu\&.hilite\&.pixmap: <filename>
324menu\&.hilite\&.textColor: <color>
325menu\&.itemHeight: <integer>
326menu\&.title: <texture type>
327menu\&.title\&.color: <color>
328menu\&.title\&.colorTo: <color>
329menu\&.title\&.font: <font>
330menu\&.title\&.pixmap: <filename>
331menu\&.title\&.textColor: <color>
332menu\&.title\&.justify: <{Left|Right|Center}>
333menu\&.titleHeight: <integer>
334menu\&.roundCorners: <{Top|Bottom}{Left|Right}>
335menu\&.selected\&.pixmap: <filename>
336menu\&.submenu\&.pixmap: <filename>
337menu\&.unselected\&.pixmap: <filename>
338\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
339.fi
340
341.SH "BACKGROUND"
342
343
344Rarely are you going to want to use this option\&. There is a command that is similar that is used in the init file\&. It is bad style to use this in your style, as it forces the user to use your background\&. So note that it is good practice to leave this blank or out of the style altogether\&.
345
346.nf
347background: centered|aspect|tiled|fullscreen|random|solid|gradient <texture>
348background\&.pixmap: <file (or directory for random)>
349background\&.color: <color>
350background\&.colorTo: <color>
351.fi
352
353.SH "SLIT"
354
355
356Here are all of the options for the slit\&.
357
358.nf
359\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
360slit: <texture type>
361slit\&.bevelWidth: <integer>
362slit\&.borderColor: <color>
363slit\&.borderWidth: <integer>
364slit\&.color: <color>
365slit\&.colorTo: <color>
366slit\&.pixmap: <filename>
367\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
368.fi
369
370.SH "TOOLBAR OPTIONS"
371
372
373Below you will find all of the configuration possibilities for the toolbar\&. The list is pretty extensive and offers you many options to make your toolbar look just the way you want it\&.
374
375.nf
376\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
377toolbar: <texture type>
378toolbar\&.bevelWidth: <integer (0\-255)>
379toolbar\&.borderColor: <color>
380toolbar\&.borderWidth: <integer>
381toolbar\&.button\&.scale: <integer>
382toolbar\&.color: <color>
383toolbar\&.colorTo: <color>
384toolbar\&.clock: <texture type>
385toolbar\&.clock\&.borderColor: <color>
386toolbar\&.clock\&.borderWidth: <integer>
387toolbar\&.clock\&.font: <font>
388toolbar\&.clock\&.justify: <{Left|Right|Center}>
389toolbar\&.clock\&.pixmap: <filename>
390toolbar\&.clock\&.color: <color>
391toolbar\&.clock\&.colorTo: <color>
392toolbar\&.clock\&.textColor: <color>
393toolbar\&.height: <integer>
394toolbar\&.iconbar\&.focused: <texture type>
395toolbar\&.iconbar\&.focused\&.color: <color>
396toolbar\&.iconbar\&.focused\&.colorTo:<color>
397toolbar\&.iconbar\&.focused\&.pixmap: <filename>
398toolbar\&.iconbar\&.unfocused: <texture type>
399toolbar\&.iconbar\&.unfocused\&.color: <color>
400toolbar\&.iconbar\&.unfocused\&.colorTo: <color>
401toolbar\&.iconbar\&.unfocused\&.pixmap: <filename>
402toolbar\&.iconbar\&.empty: <texture type>
403toolbar\&.iconbar\&.empty\&.color: <color>
404toolbar\&.iconbar\&.empty\&.colorTo: <color>
405toolbar\&.iconbar\&.empty\&.pixmap: <filename>
406toolbar\&.iconbar\&.focused\&.borderColor: <color>
407toolbar\&.iconbar\&.focused\&.borderWidth: <integer>
408toolbar\&.iconbar\&.unfocused\&.borderColor: <color>
409toolbar\&.iconbar\&.unfocused\&.borderWidth: <integer>
410toolbar\&.iconbar\&.borderColor: <color>
411toolbar\&.iconbar\&.borderWidth: <integer>
412toolbar\&.iconbar\&.focused\&.font: <font>
413toolbar\&.iconbar\&.focused\&.justify: <{Left|Right|Center}>
414toolbar\&.iconbar\&.focused\&.textColor: <color>
415toolbar\&.iconbar\&.unfocused\&.font: <font>
416toolbar\&.iconbar\&.unfocused\&.justify: <{Left|Right|Center}>
417toolbar\&.iconbar\&.unfocused\&.textColor: <color>
418toolbar\&.pixmap: <filename>
419toolbar\&.shaped: <boolean>
420toolbar\&.workspace\&.font: <font>
421toolbar\&.workspace\&.justify: <{Left|Right|Center}>
422toolbar\&.workspace\&.textColor: <color>
423toolbar\&.workspace: <texture type>
424toolbar\&.workspace\&.borderColor: <color>
425toolbar\&.workspace\&.borderWidth: <integer>
426toolbar\&.workspace\&.color: <color>
427toolbar\&.workspace\&.colorTo: <color>
428toolbar\&.workspace\&.pixmap: <filename>
429\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
430.fi
431
432.SH "EXAMPLES"
433
434
435This list may seem intimidating, but remember, when you create your own style you can easily set a majority of these keys with a single component\&. For an example of this:
436
437.nf
438\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
439*color: slategrey
440*colorTo: darkslategrey
441*unfocus\&.color: darkslategrey
442*unfocus\&.colorTo: black
443*textColor: white
444*unfocus\&.textColor: lightgrey
445*font: lucidasans\-10
446\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
447.fi
448
449
450This sets nice defaults for many components\&.
451
452.SH "COLOR FORMATS"
453
454
455These are the color formats for styles:
456
457.nf
458#000000 (Hexadecimal)
459rgb:<0\-255>/<0\-255>/<0\-255>
460.fi
461
462
463See /usr/X11R6/lib/X11/rgb\&.txt for an explaination\&.
464
465.SH "AUTHOR AND CREDITS"
466
467
468Blackbox was written and maintained by Brad Hughes <blackbox@alug\&.org> and Jeff Raven <jraven@psu\&.edu>\&.
469
470
471fluxbox(1) is written and maintained by Henrik Kinnunen <fluxgen@fluxbox(1)\&.org> with contributions and patches merged from many individuals around the world\&.
472
473
474The Official fluxbox(1) website: http://www\&.fluxbox(1)\&.org You can find a lot of styles here: http://fluxmod\&.org/
475
476
477This manpage was composed from various resources including the official documentation, fluxbox(1) man page and numerous other resources by Curt "Asenchi" Micol\&. If you notice any errors or problems with this page, please contact him here: <asenchi@asenchi\&.com> and using the great contributions of <grubert@users\&.sourceforge\&.net>\&. Numerous other languages could be available if someone jumps in\&.
478
479.SH "SEE ALSO"
480
481
482fluxbox(1) fbsetbg(1) fbsetroot(1)
483