1
.\" Title: fluxbox-style
2
.\" Author: [see the "AUTHORS" section]
3
.\" Generator: DocBook XSL Stylesheets v1.74.0 <http://docbook.sf.net/>
5
.\" Manual: Fluxbox Manual
6
.\" Source: fluxbox-style.txt 1.1.2
9
.TH "FLUXBOX\-STYLE" "5" "05/26/2009" "fluxbox\-style\&.txt 1\&.1\&.2" "Fluxbox Manual"
10
.\" -----------------------------------------------------------------
11
.\" * (re)Define some macros
12
.\" -----------------------------------------------------------------
13
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
14
.\" toupper - uppercase a string (locale-aware)
15
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17
.tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ
19
.tr aabbccddeeffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz
21
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
22
.\" SH-xref - format a cross-reference to an SH section
23
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
32
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
33
.\" SH - level-one heading that works better for non-TTY output
34
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
36
.\" put an extra blank line of space above the head in non-TTY output
43
.nr an-prevailing-indent \\n[IN]
47
.HTML-TAG ".NH \\n[an-level]"
49
.nr an-no-space-flag 1
51
\." make the size of the head bigger
56
.\" if n (TTY output), use uppercase
61
.\" if not n (not TTY), use normal case (not uppercase)
65
.\" if not n (not TTY), put a border/line under subheading
70
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
71
.\" SS - level-two heading that works better for non-TTY output
72
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
77
.nr an-prevailing-indent \\n[IN]
82
.nr an-no-space-flag 1
85
\." make the size of the head bigger
91
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
92
.\" BB/BE - put background/screen (filled box) around block of text
93
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
106
.if "\\$2"adjust-for-leading-newline" \{\
114
.nr BW \\n(.lu-\\n(.i
117
.ie "\\$2"adjust-for-leading-newline" \{\
118
\M[\\$1]\h'1n'\v'+.5v'\D'P \\n(BWu 0 0 \\n(BHu -\\n(BWu 0 0 -\\n(BHu'\M[]
121
\M[\\$1]\h'1n'\v'-.5v'\D'P \\n(BWu 0 0 \\n(BHu -\\n(BWu 0 0 -\\n(BHu'\M[]
132
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
133
.\" BM/EM - put colored marker in margin next to block of text
134
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
151
\M[\\$1]\D'P -.75n 0 0 \\n(BHu -(\\n[.i]u - \\n(INu - .75n) 0 0 -\\n(BHu'\M[]
159
.\" -----------------------------------------------------------------
160
.\" * set default formatting
161
.\" -----------------------------------------------------------------
162
.\" disable hyphenation
164
.\" disable justification (adjust text to left margin only)
166
.\" -----------------------------------------------------------------
167
.\" * MAIN CONTENT STARTS HERE *
168
.\" -----------------------------------------------------------------
170
fluxbox-style \- A comprehensive look at styles/themes for fluxbox(1)\&.
173
This document describes various options available for fluxbox styles\&.
178
Styles, 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\&.
180
Styles 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\&.
182
fluxbox(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\&.
185
A style is made up of a few major components which then have their own sub\-directives\&. The major components are as follows:
187
The \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\&.
189
To 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\&.
191
A more complete reference to this can be found in X(7), section \fIRESOURCES\fR\&.
194
There 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@pkgdatadir@/styles\fR providing a basic usable configuration\&.
196
When 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:
206
$ mkdir \-p ~/\&.fluxbox/styles/YourStyle/pixmaps
207
$ cd ~/\&.fluxbox/styles/YourStyle
217
Output of a packaged style should look like the following:
227
$ tar \-tjvf YourStyle\&.tar\&.bz2
228
\&.fluxbox/styles/YourStyle/theme\&.cfg
229
\&.fluxbox/styles/YourStyle/pixmaps
230
\&.fluxbox/styles/YourStyle/pixmaps/stick\&.xpm
240
Of 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\&. :)
241
.SH "CREATING YOUR STYLE"
243
As 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\&.
245
Here are some quick examples to illustrate basic syntax:
254
toolbar\&.clock\&.color: green
263
This sets the color resource of the toolbar clock to \fIgreen\fR\&. Another example:
272
menu*color: rgb:3/4/5
281
This 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
290
*font: \-b&h\-lucida\-medium\-r\-normal\-*\-*\-140\-*
299
you 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)\&.)
301
In 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:
310
*textColor: rgb:3/4/5
319
This 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:
328
*textColor: rgb:3/4/5
329
toolbar\&.clock\&.textColor: rgb:255/0/0
338
With 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\&.
340
Now 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\&.:
349
toolbar\&.clock: Raised Gradient Diagonal Bevel1
350
toolbar\&.clock\&.color: rgb:8/6/4
351
toolbar\&.clock\&.colorTo: rgb:4/3/2
360
Don\'t worry, we will explain what these mean\&. A texture description consists of up to five fields, which are as follows:
362
\fBFlat | Raised | Sunken\fR. gives the component either a flat, raised or sunken appearance\&.
364
\fBGradient | Solid\fR. tells fluxbox(1) to draw either a solid color or a gradient texture\&.
366
\fBHorizontal | Vertical | Diagonal | Crossdiagonal | Pipecross | Elliptic | Rectangle | Pyramid\fR. Select one of these texture types\&. They only work when
370
\fBInterlaced\fR. tells 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\&.
372
\fBBevel1 | Bevel2\fR. tells 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\&.
374
Instead of a texture description, also the option \fBParentRelative\fR is available, which makes the component appear as a part of its parent, e\&.g\&. totally transparent\&.
376
Or 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\&.
385
toolbar\&.clock: pixmap
386
toolbar\&.clock\&.pixmap: clock_background\&.xpm
395
This feature might need some investigation, reports say that sometimes the resources color and colorTo must be set and then they may not be set\&.
397
All gradiented textures are composed of two color values: the \fIcolor\fR and \fIcolorTo\fR resources\&. When \fBInterlaced\fR is used in \fBSolid\fR mode, the \fIcolorTo\fR resource is used to find the interlacing color\&.
398
.SH "A WORD ABOUT FONTS"
400
We 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:
409
menu\&.title\&.font: sans\-8:bold,shadow
418
The latest versions of fluxbox(1) (> 0\&.9\&.8) also support different values for these text options\&. The possibilities are as follows:
428
Shadow color=<colorname> offsetx=<integer> offsety=<integer> Halo color=<colorname>
438
For the case of completeness, here are some real world examples:
447
*\&.font: Verdana\-10:bold,shadow:offsetx=2;offsety=4;color=green
448
*\&.font: Verdana\-10:halo:color=blue
457
Of course this could all be placed on one line\&. Also note that for the offset options, negative integers are allowed\&.
460
If 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: \m[blue]\fBhttp://xfree\&.org/4\&.3\&.0/fonts2\&.html#3\fR\m[]
461
.SH "FULL COMPONENT LIST"
463
Here 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\&.
466
Many, many things you can do with window design in fluxbox(1), below are your options\&. Have fun\&.
475
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
476
window\&.bevelWidth: <integer>
477
window\&.borderColor: <color>
478
window\&.borderWidth: <integer>
479
window\&.button\&.focus: <texture type>
480
window\&.button\&.focus\&.color: <color>
481
window\&.button\&.focus\&.colorTo: <color>
482
window\&.button\&.focus\&.picColor: <color>
483
window\&.button\&.focus\&.pixmap: <filename>
484
window\&.button\&.pressed: <texture type>
485
window\&.button\&.pressed\&.color: <color>
486
window\&.button\&.pressed\&.colorTo: <color>
487
window\&.button\&.pressed\&.pixmap: <filename>
488
window\&.button\&.unfocus: <texture type>
489
window\&.button\&.unfocus\&.color: <color>
490
window\&.button\&.unfocus\&.colorTo: <color>
491
window\&.button\&.unfocus\&.picColor: <color>
492
window\&.button\&.unfocus\&.pixmap: <filename>
493
window\&.close\&.pixmap: <filename>
494
window\&.close\&.pressed\&.pixmap: <filename>
495
window\&.close\&.unfocus\&.pixmap: <filename>
496
window\&.font: <font>
497
window\&.frame\&.focusColor: <color>
498
window\&.frame\&.unfocusColor: <color>
499
window\&.grip\&.focus: <texture type>
500
window\&.grip\&.focus\&.color: <color>
501
window\&.grip\&.focus\&.colorTo: <color>
502
window\&.grip\&.focus\&.pixmap: <filename>
503
window\&.grip\&.unfocus: <texture type>
504
window\&.grip\&.unfocus\&.color: <color>
505
window\&.grip\&.unfocus\&.colorTo: <color>
506
window\&.grip\&.unfocus\&.pixmap: <filename>
507
window\&.handle\&.focus: <texture type>
508
window\&.handle\&.focus\&.color: <color>
509
window\&.handle\&.focus\&.colorTo: <color>
510
window\&.handle\&.focus\&.pixmap: <filename>
511
window\&.handle\&.unfocus: <texture type>
512
window\&.handle\&.unfocus\&.color: <color>
513
window\&.handle\&.unfocus\&.colorTo: <color>
514
window\&.handle\&.unfocus\&.pixmap: <filename>
515
window\&.handleWidth: <integer>
516
window\&.iconify\&.pixmap: <filename>
517
window\&.iconify\&.pressed\&.pixmap: <filename>
518
window\&.iconify\&.unfocus\&.pixmap: <filename>
519
window\&.justify: <{Left|Right|Center}>
520
window\&.label\&.active: <texture type>
521
window\&.label\&.active\&.textColor: <color>
522
window\&.label\&.focus: <texture type>
523
window\&.label\&.focus\&.color: <color>
524
window\&.label\&.focus\&.colorTo: <color>
525
window\&.label\&.focus\&.pixmap: <filename>
526
window\&.label\&.unfocus: <texture type>
527
window\&.label\&.unfocus\&.color: <color>
528
window\&.label\&.unfocus\&.colorTo: <color>
529
window\&.label\&.unfocus\&.pixmap: <filename>
530
window\&.label\&.focus\&.textColor: <color>
531
window\&.label\&.unfocus\&.textColor: <color>
532
window\&.maximize\&.pixmap: <filename>
533
window\&.maximize\&.pressed\&.pixmap: <filename>
534
window\&.maximize\&.unfocus\&.pixmap: <filename>
535
window\&.roundCorners: <{Top|Bottom}{Left|Right}>
536
window\&.shade\&.pixmap: <filename>
537
window\&.shade\&.pressed\&.pixmap: <filename>
538
window\&.shade\&.unfocus\&.pixmap: <filename>
539
window\&.stick\&.pixmap: <filename>
540
window\&.stick\&.pressed\&.pixmap: <filename>
541
window\&.stick\&.unfocus\&.pixmap: <filename>
542
window\&.stuck\&.pixmap: <filename>
543
window\&.stuck\&.unfocus\&.pixmap: <filename>
544
window\&.title\&.focus: <texture type>
545
window\&.title\&.focus\&.color: <color>
546
window\&.title\&.focus\&.colorTo: <color>
547
window\&.title\&.focus\&.pixmap: <filename>
548
window\&.title\&.height: <integer>
549
window\&.title\&.unfocus: <texture type>
550
window\&.title\&.unfocus\&.color: <color>
551
window\&.title\&.unfocus\&.colorTo: <color>
552
window\&.title\&.unfocus\&.pixmap: <filename>
553
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
563
Everything you need to make your menu look pretty\&.
572
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
573
menu\&.bevelWidth: <integer>
574
menu\&.borderColor: <color>
575
menu\&.borderWidth: <integer>
576
menu\&.bullet: <{empty|square|triangle|diamond}>
577
menu\&.bullet\&.position: <{left|right}>
578
menu\&.frame: <texture type>
579
menu\&.frame\&.color: <color>
580
menu\&.frame\&.colorTo: <color>
581
menu\&.frame\&.disableColor: <color>
582
menu\&.frame\&.font: <font>
583
menu\&.frame\&.justify: <{Left|Right|Center}>
584
menu\&.frame\&.pixmap: <filename>
585
menu\&.frame\&.textColor: <color>
586
menu\&.hilite: <texture type>
587
menu\&.hilite\&.color: <color>
588
menu\&.hilite\&.colorTo: <color>
589
menu\&.hilite\&.pixmap: <filename>
590
menu\&.hilite\&.textColor: <color>
591
menu\&.itemHeight: <integer>
592
menu\&.title: <texture type>
593
menu\&.title\&.color: <color>
594
menu\&.title\&.colorTo: <color>
595
menu\&.title\&.font: <font>
596
menu\&.title\&.pixmap: <filename>
597
menu\&.title\&.textColor: <color>
598
menu\&.title\&.justify: <{Left|Right|Center}>
599
menu\&.titleHeight: <integer>
600
menu\&.roundCorners: <{Top|Bottom}{Left|Right}>
601
menu\&.selected\&.pixmap: <filename>
602
menu\&.submenu\&.pixmap: <filename>
603
menu\&.unselected\&.pixmap: <filename>
604
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
614
Every style must specify the background option\&. If you don\'t want your style to change the user\'s background, then use `background: none\'\&. The options `centered\', `aspect\', `tiled\', and `fullscreen\' require the `background\&.pixmap\' resource to contain a valid file name\&. The `random\' option requires `background\&.pixmap\' to contain a valid directory name\&. For these options, \fBfluxbox(1)\fR will call \fBfbsetbg(1)\fR to set the background\&. The options `gradient\', `solid\', and `mod\' all require `background\&.color\' to be set\&. `gradient\' and `mod\' both require `background\&.colorTo\'\&. `mod\' requires `background\&.modX\' and `background\&.modY\' to be set as well\&. These options will be passed to \fBfbsetroot(1)\fR to set the background\&. The special option `unset\' is for use in user overlay files only\&. It specifies that fbsetbg should never be run (by default, even when `none\' is set in the overlay, fluxbox will try to run \(lqfbsetbg \-z\(rq to restore the last wallpaper)\&.
623
background: centered|aspect|tiled|fullscreen|random|solid|gradient <texture>|mod|none|unset
624
background\&.pixmap: <file or directory>
625
background\&.color: <color>
626
background\&.colorTo: <color>
627
background\&.modX: <integer>
628
background\&.modY: <integer>
638
Here are all of the options for the slit\&.
647
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
649
slit\&.bevelWidth: <integer>
650
slit\&.borderColor: <color>
651
slit\&.borderWidth: <integer>
652
slit\&.color: <color>
653
slit\&.colorTo: <color>
654
slit\&.pixmap: <filename>
655
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
663
.SH "TOOLBAR OPTIONS"
665
Below 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\&.
674
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
675
toolbar: <texture type>
676
toolbar\&.bevelWidth: <integer (0\-255)>
677
toolbar\&.borderColor: <color>
678
toolbar\&.borderWidth: <integer>
679
toolbar\&.button\&.scale: <integer>
680
toolbar\&.color: <color>
681
toolbar\&.colorTo: <color>
682
toolbar\&.clock: <texture type>
683
toolbar\&.clock\&.borderColor: <color>
684
toolbar\&.clock\&.borderWidth: <integer>
685
toolbar\&.clock\&.font: <font>
686
toolbar\&.clock\&.justify: <{Left|Right|Center}>
687
toolbar\&.clock\&.pixmap: <filename>
688
toolbar\&.clock\&.color: <color>
689
toolbar\&.clock\&.colorTo: <color>
690
toolbar\&.clock\&.textColor: <color>
691
toolbar\&.height: <integer>
692
toolbar\&.iconbar\&.focused: <texture type>
693
toolbar\&.iconbar\&.focused\&.color: <color>
694
toolbar\&.iconbar\&.focused\&.colorTo:<color>
695
toolbar\&.iconbar\&.focused\&.pixmap: <filename>
696
toolbar\&.iconbar\&.unfocused: <texture type>
697
toolbar\&.iconbar\&.unfocused\&.color: <color>
698
toolbar\&.iconbar\&.unfocused\&.colorTo: <color>
699
toolbar\&.iconbar\&.unfocused\&.pixmap: <filename>
700
toolbar\&.iconbar\&.empty: <texture type>
701
toolbar\&.iconbar\&.empty\&.color: <color>
702
toolbar\&.iconbar\&.empty\&.colorTo: <color>
703
toolbar\&.iconbar\&.empty\&.pixmap: <filename>
704
toolbar\&.iconbar\&.focused\&.borderColor: <color>
705
toolbar\&.iconbar\&.focused\&.borderWidth: <integer>
706
toolbar\&.iconbar\&.unfocused\&.borderColor: <color>
707
toolbar\&.iconbar\&.unfocused\&.borderWidth: <integer>
708
toolbar\&.iconbar\&.borderColor: <color>
709
toolbar\&.iconbar\&.borderWidth: <integer>
710
toolbar\&.iconbar\&.focused\&.font: <font>
711
toolbar\&.iconbar\&.focused\&.justify: <{Left|Right|Center}>
712
toolbar\&.iconbar\&.focused\&.textColor: <color>
713
toolbar\&.iconbar\&.unfocused\&.font: <font>
714
toolbar\&.iconbar\&.unfocused\&.justify: <{Left|Right|Center}>
715
toolbar\&.iconbar\&.unfocused\&.textColor: <color>
716
toolbar\&.pixmap: <filename>
717
toolbar\&.shaped: <boolean>
718
toolbar\&.workspace\&.font: <font>
719
toolbar\&.workspace\&.justify: <{Left|Right|Center}>
720
toolbar\&.workspace\&.textColor: <color>
721
toolbar\&.workspace: <texture type>
722
toolbar\&.workspace\&.borderColor: <color>
723
toolbar\&.workspace\&.borderWidth: <integer>
724
toolbar\&.workspace\&.color: <color>
725
toolbar\&.workspace\&.colorTo: <color>
726
toolbar\&.workspace\&.pixmap: <filename>
727
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
737
This 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:
746
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
748
*colorTo: darkslategrey
749
*unfocus\&.color: darkslategrey
750
*unfocus\&.colorTo: black
752
*unfocus\&.textColor: lightgrey
753
*font: lucidasans\-10
754
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
763
This sets nice defaults for many components\&.
766
These are the color formats for styles:
775
#000000 (Hexadecimal)
776
rgb:<0\-255>/<0\-255>/<0\-255>
785
See /usr/share/X11/rgb\&.txt for an explaination\&.
788
Blackbox was written and maintained by Brad Hughes <blackbox at alug\&.org> and Jeff Raven <jraven at psu\&.edu>\&.
790
fluxbox(1) is written and maintained by Henrik Kinnunen <fluxgen at fluxbox\&.org> with contributions and patches merged from many individuals around the world\&.
792
The Official fluxbox(1) website: \m[blue]\fBhttp://www\&.fluxbox\&.org\fR\m[] You can find a lot of styles here: \m[blue]\fBhttp://tenr\&.de/\fR\m[]
794
This 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 at asenchi\&.com> and using the great contributions of <grubert at users\&.sourceforge\&.net>\&. Numerous other languages could be available if someone jumps in\&.
797
fluxbox(1) fbsetbg(1) fbsetroot(1)
added
removed
doc/fluxbox-style.5.in
