nilix/fluxbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

updated docs from curt micol

Browse source
This commit is contained in:
mathias 2004-11-30 17:47:39 +00:00
parent 518d99d8d2
commit 06dd816c9c
1 changed files with 277 additions and 226 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

511
doc/fluxstyle.1.in
View file

@ -22,7 +22,7 @@
.\" files on http://www.fluxbox.org and http://www.fluxmod.dk
.\"
.\" Created and Updated for version 0.9.7 by Curt Micol <asenchi@asenchi.com>
.\"
.\" Define this: <blockquote><pre>
.de EX
.ne 5
@ -37,91 +37,103 @@
.if n .sp 1
.if t .sp .5
..
.\" Begin actual page
.\"
.TH fluxstyle 1 "January 7th, 2004" "0.9.8"
.SH NAME
fluxstyle \- all you need to know about Fluxbox styles
.SH DESCRIPTION
.\"
.\" Taken from the documentation
.\"
.SS What is a Style?
A style is basically a theme for the
.IR Fluxbox(1)
window manager. It is a simple ASCII text file that tells Fluxbox how
to generate the appearance of the different components of the window manager.
The default installation of Fluxbox is shipped with many classic styles that
show the customization of current Fluxbox versions. They are usually located in
.IR ~/.fluxbox/styles
and in the global Fluxbox share directory
.IR @pkgdatadir@/styles
which may vary depending on the method of installation used. To use one of
the styles shipped with Fluxbox, look in your root menu under the configure
part of the menu for 'System Styles'.
.PP
Fluxbox uses its own graphics class to render its images on the fly. By using
style files, you can determine at a great level of configurability what your
desktop will look like. Fluxbox styles are compatible with those of the
Blackbox window manager (where Fluxbox originated). Users migrating from
Blackbox can use their current favourite themes.
.SH STRUCTURE OF STYLES
The style is made up of a few major components which then have their own
sub-directives. The toolbar, menu, slit and window are the major components. The
.\" Begin actual page
.TH fluxstyle 1 "November 29th, 2004" "0.9.10"
.SH NAME
fluxstyle \- A comprehensive look at styles/themes for Fluxbox
.SH DESCRIPTION
.\" Taken from the documentation
.SS What is a Style?
Styles, sometimes referred to as Themes, are a graphical overlay for the
.IR Fluxbox(1)
window manager. If you wanted to get to know Fluxbox, the styles
would be the 'look' of the 'look and feel'.
.PP
Styles are simple ASCII text files that tell Fluxbox how to generate the
appearance of different components of the window manager. The default
installation of Fluxbox 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 'System Styles' menu under your main Fluxbox menu.
.PP
Fluxbox uses it's 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 was derived from Blackbox many often
wonder if old themes will work on the latest releases of Blackbox. Well they
basically do, but you will have to tune them since the Fluxbox code has
changed quite a bit since the initial grab.
.SH STRUCTURE
A style is made up of a few major components which then have their own
sub-directives. The major components are as follows:
.PP
The
.IR window.*
directives control the appearance of your window frames,
directives control the appearance of the window frames,
.IR window.tab.*
controls the appearance of the window tabs.
controls the appearance of the window tabs,
.IR menu.*
controls the appearance of the popup menu that you see when you right click
on the desktop.
controls the appearance of the popup menu that you see when you right click on
the desktop.
.IR toolbar.*
is the bar you will see at the top or bottom of your screen. Finally the
.IR slit.*
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
.IR toolbar.*
directives instead.
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.
.PP
To understand how the style mechanism works, it is nice to know a litte about how
X11 resources work.
.PP
X11 resources consist of a key and a value. The key si constructed of several smaller
keys (sometimes referred to as children), delimited by a period (.). Keys may also
contain a asterisk (*) to serve as a wildcard, which means that one line of typed text
will match several keys. This is useful for styles that are based on one or two colors.
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.
.SH LOCATION OF STYLES
We'll cover quickly where styles can be found and placed after you create your own.
.PP
There are a number of default styles that come with the installation, while we have already
covered this, we will again just provide a central location for all style locations. These
default styles are located in
.SH LOCATION
There are many places to store your styles, the most common is in your
.IR ~/.fluxbox/styles
directory. The initial installation will place the default styles in
.IR @pkgdatadir@/styles
providing a default configureation at installation.
providing a basic usable configuration.
.PP
Once you create your own, you can create a directory in
.IR ~/.fluxbox/
called 'styles'. While there isn't an official structure of how to package your style, one way that is recommended is creating a directory named after your style and placing your pixmaps directory in there along with a theme.cfg. The theme.cfg file being your created style. So for example if I created a style called 'MyStyle' I would create the following:
When creating your own style, create a directory (normally the name of your
style) in
.IR ~/.fluxbox/styles/
(If the 'styles' 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:
.EX
mkdir -p ~/.fluxbox/styles/MyStyle
cd ~/.fluxbox/styles/MyStyle
mkdir pixmaps
vi theme.cfg (this being where you design your style with
the necessary components)
$ cd
$ mkdir -p ~/.fluxbox/styles/YourStyle/pixmaps
$ cd ~/.fluxbox/styles/YourStyle
$ nano theme.cfg
.EE
If you follow this, the path to your pixmaps will be:
.IR ~/fluxbox/styles/MyStyle/pixmaps
which makes it a bit easier to setup up and distribute your style.
Output of a packaged style should look like the following:
.EX
$ cd
$ tar -tjvf YourStyle.tar.bz2
.fluxbox/styles/YourStyle/theme.cfg
.fluxbox/styles/YourStyle/pixmaps
.fluxbox/styles/YourStyle/pixmaps/stick.xpm
...
.EE
Of course, all of these are just preferences, Fluxbox 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. :)
.SH CREATING STYLES
As discussed in the
.IR STRUCTURE
section of this man page, Fluxbox allows you to configure its four main components: the toolbar, the menus, the
slit and the window decorations. Remember that you can customize the slit with its own
directives, but if you don't, it will take the appearance of the toolbar.
.SH CREATING YOUR STYLE
As discussed above, Fluxbox 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.
.PP
Here are some quick examples to illustrate basic syntax:
.EX
@ -142,57 +154,63 @@ And with
.EX
*font: -b&h-lucida-medium-r-normal-*-*-140-*
.EE
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
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
.IR xfontsel "(1), " gtkfontsel ", or " xlsfonts "(1).)"
.PP
This last example brings up wildcards and overrides. In a Fluxbox style you can set a value
with a wild card. The previous example means that every font in the style will be what is
specified. You can do this with any value. For example if you wanted all of the text to be one
color you could do:
In the last example you will notice the wildcard (*) before font. In a
Fluxbox style you can set a value with a wild card. 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:
.EX
*textColor: rgb:3/4/5
.EE
This means you can setup a very simple style with very few properties. See
This means that you can setup a very simple style with very few properties.
See the
.IR EXAMPLES
below for an example of this in practice. You can also override wildcards in the style
file. Lets take our example above and add an override for the toolbar.clock.textColor:
below for an example of this in practice. Fluxbox also allows you to override
wildcards in your style. Lets take our example above and add an override for
the
.IR toolbar.clock.textColor
component:
.EX
*textColor: rgb:3/4/5
toolbar.clock.textColor: rgb:255/0/0
.EE
With that all of the text will be 'rgb:3/4/5' except the toolbar clock text which will be 'rgb:255/0/0'
With that all of the text will be 'rgb:3/4/5' except the toolbar clock text
which will be 'rgb:255/0/0'.
.PP
Now, what makes Fluxbox just so spectacular, is its ability to render textures
on the fly.
Texture descriptions are specified directly to the key that they
should apply to, e.g.:
Now what makes Fluxbox 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.:
.ta \w'toolbar.clock.colorTo:\ 'u
.EX
toolbar.clock: Raised Gradient Diagonal Bevel1
toolbar.clock.color: rgb:8/6/4
toolbar.clock.colorTo: rgb:4/3/2
.EE
Don't worry, we will explain right now!
A texture description consists of up to five fields, which are as follows:
Don't worry, we will explain what these mean. A texture description consists
of up to five fields, which are as follows:
.TP
.B Flat / Raised / Sunken
.B Flat | Raised | Sunken
gives the component either a flat, raised or sunken appearance.
.TP
.B Gradient / Solid
.B Gradient | Solid
tells Fluxbox to draw either a solid color or a gradient texture.
.TP
.B Horizontal / Vertical / Diagonal / Crossdiagonal / Pipecross / Elliptic / Rectangle / Pyramid
Select one of these texture types. They only work when also
.B Horizontal | Vertical | Diagonal | Crossdiagonal | Pipecross | Elliptic | Rectangle | Pyramid
Select one of these texture types. They only work when
.B Gradient
is specified!
is specified.
.TP
.B Interlaced
tells Fluxbox to interlace the texture (darken every other line).
This option is most commonly used with gradiented textures, but from Fluxbox
version 0.60.3 on, it also works in solid textures.
.TP
.B Bevel1 / Bevel2
.B Bevel1 | Bevel2
tells Fluxbox which type of bevel to use.
Bevel1 is the default bevel.
The shading is placed on the edge of the image.
@ -224,139 +242,167 @@ is used in
mode, the
.I colorTo
resource is used to find the interlacing color.
.PP
.SH A WORD ABOUT FONTS
We should comment about fonts before we move on to the complete component
list.
.PP
Fluxbox supports different options for text. These options currently include bold and shadow. To set these do this, fontname-size:options, for any of the font components in the style file. For example:
list. Fluxbox supports different options for text. These options currently
include bold, halo and shadow. To set these do this:
.IR fontname-size:options
for any of the font components in the style file. For example:
.EX
menu.title.font: sans-8:bold,shadow
.EE
The latest versions of Fluxbox (> 0.9.8) also support different values for
these text options. The possibilities are as follows:
.B Shadow
color=<colorname>
offsetx=<integer>
offsety=<integer>
.B Halo
color=<colorname>
For the case of completeness, here are some real world examples:
.EX
*.font: Verdana-10:bold,shadow:offsetx=2;offsety=4;color=green
*.font: Verdana-10:halo:color=blue
.EE
Of course this could all be placed on one line. Also note that for the offset
options, negative integers are allowed.
.SH FONT PROBLEMS
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: http://xfree.org/4.3.0/fonts2.html#3.
.SH FULL COMPONENT LIST
Here is the complete component list, together with which kind of value they take.
Comments are preceded with an exclamation sign (!), which is also used for
comments in Fluxbox style c.q. X resource files.
Here is the exhaustive component list for Fluxbox 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.
.PP
.\" The comments also to be translated!
.SS WINDOW OPTIONS
Many, many things you can do with window design in Fluxbox, below are your options. Have fun.
.EX
window.label.focus: <texture type>
window.label.focus.pixmap: <filename>
window.label.focus.color: <color>
window.label.focus.colorTo: <color>
window.label.unfocus: <texture type>
window.label.unfocus.pixmap: <filename>
window.label.unfocus.color: <color>
window.label.unfocus.colorTo: <color>
window.title.focus: <texture type>
window.title.focus.pixmap: <filename>
window.title.focus.color: <color>
window.title.focus.colorTo: <color>
window.title.unfocus: <texture type>
window.title.unfocus.pixmap: <filename>
window.title.unfocus.color: <color>
window.title.unfocus.colorTo: <color>
window.handle.focus: <texture type>
window.handle.focus.pixmap: <filename>
window.handle.focus.color: <color>
window.handle.focus.colorTo: <color>
window.handle.unfocus: <texture type>
window.handle.unfocus.pixmap: <filename>
window.handle.unfocus.color: <color>
window.handle.unfocus.colorTo: <color>
window.bevelWidth: <integer>
window.borderColor: <color>
window.borderWidth: <integer>
window.button.focus: <texture type>
window.button.focus.pixmap: <filename>
window.button.focus.color: <color>
window.button.focus.colorTo: <color>
window.button.unfocus: <texture type>
window.button.unfocus.pixmap: <filename>
window.button.unfocus.color: <color>
window.button.unfocus.colorTo: <color>
window.button.focus.picColor: <color>
window.button.focus.pixmap: <filename>
window.button.pressed: <texture type>
window.button.pressed.pixmap: <filename>
window.button.pressed.color: <color>
window.button.pressed.colorTo: <color>
window.grip.focus: <texture type>
window.grip.focus.pixmap: <filename>
window.grip.focus.color: <color>
window.grip.focus.colorTo: <color>
window.grip.unfocus: <texture type>
window.grip.unfocus.pixmap: <filename>
window.grip.unfocus.color: <color>
window.grip.unfocus.colorTo: <color>
window.label.focus.textColor: <color>
window.label.unfocus.textColor: <color>
window.button.pressed.pixmap: <filename>
window.button.unfocus: <texture type>
window.button.unfocus.color: <color>
window.button.unfocus.colorTo: <color>
window.button.unfocus.picColor: <color>
window.button.unfocus.pixmap: <filename>
window.close.pixmap: <filename>
window.close.pressed.pixmap: <filename>
window.close.unfocus.pixmap: <filename>
window.font: <font>
window.frame.focusColor: <color>
window.frame.unfocusColor: <color>
window.button.focus.picColor: <color>
window.button.unfocus.picColor: <color>
window.font: <font>
window.justify:
window.roundCorners:
window.alpha: <integer>
window.title.height: <integer>
window.bevelWidth: <integer>
window.grip.focus: <texture type>
window.grip.focus.color: <color>
window.grip.focus.colorTo: <color>
window.grip.focus.pixmap: <filename>
window.grip.unfocus: <texture type>
window.grip.unfocus.color: <color>
window.grip.unfocus.colorTo: <color>
window.grip.unfocus.pixmap: <filename>
window.handle.focus: <texture type>
window.handle.focus.color: <color>
window.handle.focus.colorTo: <color>
window.handle.focus.pixmap: <filename>
window.handle.unfocus: <texture type>
window.handle.unfocus.color: <color>
window.handle.unfocus.colorTo: <color>
window.handle.unfocus.pixmap: <filename>
window.handleWidth: <integer>
window.borderWidth: <integer>
window.borderColor: <color>
window.close.pixmap: <filename>
window.close.unfocus.pixmap: <filename>
window.close.pressed.pixmap: <filename>
window.maximize.pixmap: <filename>
window.maximize.unfocus.pixmap: <filename>
window.maximize.pressed.pixmap: <filename>
window.iconify.pixmap: <filename>
window.iconify.unfocus.pixmap: <filename>
window.iconify.pressed.pixmap: <filename>
window.iconify.unfocus.pixmap: <filename>
window.justify: <{Left|Right|Center}>
window.label.active: <texture type>
window.label.active.textColor: <color>
window.label.focus: <texture type>
window.label.focus.color: <color>
window.label.focus.colorTo: <color>
window.label.focus.pixmap: <filename>
window.label.unfocus: <texture type>
window.label.unfocus.color: <color>
window.label.unfocus.colorTo: <color>
window.label.unfocus.pixmap: <filename>
window.label.focus.textColor: <color>
window.label.unfocus.textColor: <color>
window.maximize.pixmap: <filename>
window.maximize.pressed.pixmap: <filename>
window.maximize.unfocus.pixmap: <filename>
window.roundCorners: <{Top|Bottom}{Left|Right}>
window.shade.pixmap: <filename>
window.shade.unfocus.pixmap: <filename>
window.shade.pressed.pixmap: <filename>
window.shade.unfocus.pixmap: <filename>
window.stick.pixmap: <filename>
window.stick.unfocus.pixmap: <filename>
window.stick.pressed.pixmap: <filename>
window.stick.unfocus.pixmap: <filename>
window.stuck.pixmap: <filename>
window.stuck.unfocus.pixmap: <filename>
window.title.focus: <texture type>
window.title.focus.color: <color>
window.title.focus.colorTo: <color>
window.title.focus.pixmap: <filename>
window.title.height: <integer>
window.title.unfocus: <texture type>
window.title.unfocus.color: <color>
window.title.unfocus.colorTo: <color>
window.title.unfocus.pixmap: <filename>
.EE
.SS MENU OPTIONS
Everything you need to make your menu look pretty.
.EX
menu.title.textColor: <color>
menu.frame.textColor: <color>
menu.hilite.textColor: <color>
menu.frame.disableColor: <color>
menu.title: <texture type>
menu.title.pixmap: <filename>
menu.title.color: <color>
menu.title.colorTo: <color>
menu.bevelWidth: <integer>
menu.borderColor: <color>
menu.borderWidth: <integer>
menu.bullet:
menu.bullet.position:
menu.frame: <texture type>
menu.frame.pixmap: <filename>
menu.frame.color: <color>
menu.frame.colorTo: <color>
menu.frame.disableColor: <color>
menu.frame.font: <font>
menu.frame.justify: <{Left|Right|Center}>
menu.frame.pixmap: <filename>
menu.frame.textColor: <color>
menu.hilite: <texture type>
menu.hilite.pixmap: <filename>
menu.hilite.color: <color>
menu.hilite.colorTo: <color>
menu.title.font: <font>
menu.frame.font: <font>
menu.frame.justify:
menu.title.justify:
menu.bullet.position:
menu.bullet:
menu.borderWidth:
menu.bevelWidth:
menu.borderColor: <color>
menu.submenu.pixmap: <filename>
menu.selected.pixmap: <filename>
menu.unselected.pixmap: <filename>
menu.roundCorners:
menu.titleHeight: <integer>
menu.hilite.pixmap: <filename>
menu.hilite.textColor: <color>
menu.itemHeight: <integer>
menu.title: <texture type>
menu.title.color: <color>
menu.title.colorTo: <color>
menu.title.font: <font>
menu.title.pixmap: <filename>
menu.title.textColor: <color>
menu.title.justify: <{Left|Right|Center}>
menu.titleHeight: <integer>
menu.roundCorners: <{Top|Bottom}{Left|Right}>
menu.selected.pixmap: <filename>
menu.submenu.pixmap: <filename>
menu.unselected.pixmap: <filename>
.EE
.SS ROOT COMMAND OPTION
This is how you set your background within your style. Use the official fluxbox background program, fbsetbg. It is distributed with Fluxbox, and can also be downloaded from here: http://www.xs4all.nl/~hanb/software/fluxbox/fbsetbg.html
.SS ROOT COMMAND
Rarely are you going to want to use this option. There is a command that is
similar that is used in the
.IR 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.
.EX
rootCommand: <string>
.EE
@ -364,72 +410,74 @@ rootCommand: <string>
Here are all of the options for the slit.
.EX
slit: <texture type>
slit.pixmap: <filename>
slit.color: <color>
slit.colorTo: <color>
slit.borderWidth: <integer>
slit.bevelWidth: <integer>
slit.borderColor: <color>
slit.borderWidth: <integer>
slit.color: <color>
slit.colorTo: <color>
slit.pixmap: <filename>
.EE
.SS TOOLBAR OPTIONS
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.
.EX
toolbar: <texture type>
toolbar.pixmap: <filename>
toolbar.bevelWidth: <integer (0-255)>
toolbar.borderColor: <color>
toolbar.borderWidth: <integer>
toolbar.button.scale: <integer>
toolbar.color: <color>
toolbar.colorTo: <color>
toolbar.borderWidth: <integer>
toolbar.borderColor: <color>
toolbar.bevelWidth: <0-255>
toolbar.shaped: <boolean>
toolbar.alpha: <integer>
toolbar.height: <integer>
toolbar.clock.font: <font>
toolbar.clock.textColor: <color>
toolbar.clock.justify:
toolbar.clock: <texture type>
toolbar.clock.borderColor: <color>
toolbar.clock.borderWidth: <integer>
toolbar.clock.font: <font>
toolbar.clock.justify: <{Left|Right|Center}>
toolbar.clock.pixmap: <filename>
toolbar.clock.color: <color>
toolbar.clock.colorTo: <color>
toolbar.clock.borderWidth: <integer>
toolbar.clock.borderColor: <color>
toolbar.workspace.font: <font>
toolbar.workspace.textColor: <color>
toolbar.workspace.justify:
toolbar.workspace: <texture type>
toolbar.workspace.pixmap: <filename>
toolbar.workspace.color: <color>
toolbar.workspace.colorTo: <color>
toolbar.workspace.borderWidth: <integer>
toolbar.workspace.borderColor: <color>
toolbar.clock.textColor: <color>
toolbar.height: <integer>
toolbar.iconbar.focused: <texture type>
toolbar.iconbar.focused.pixmap: <filename>
toolbar.iconbar.focused.color: <color>
toolbar.iconbar.focused.colorTo:<color>
toolbar.iconbar.focused.pixmap: <filename>
toolbar.iconbar.unfocused: <texture type>
toolbar.iconbar.unfocused.pixmap: <filename>
toolbar.iconbar.unfocused.color: <color>
toolbar.iconbar.unfocused.colorTo: <color>
toolbar.iconbar.unfocused.pixmap: <filename>
toolbar.iconbar.empty: <texture type>
toolbar.iconbar.empty.pixmap: <filename>
toolbar.iconbar.empty.color: <color>
toolbar.iconbar.empty.colorTo: <color>
toolbar.iconbar.focused.borderWidth: <integer>
toolbar.iconbar.empty.pixmap: <filename>
toolbar.iconbar.focused.borderColor: <color>
toolbar.iconbar.unfocused.borderWidth: <integer>
toolbar.iconbar.focused.borderWidth: <integer>
toolbar.iconbar.unfocused.borderColor: <color>
toolbar.iconbar.borderWidth: <integer>
toolbar.iconbar.unfocused.borderWidth: <integer>
toolbar.iconbar.borderColor: <color>
toolbar.iconbar.borderWidth: <integer>
toolbar.iconbar.focused.font: <font>
toolbar.iconbar.focused.justify: <{Left|Right|Center}>
toolbar.iconbar.focused.textColor: <color>
toolbar.iconbar.focused.justify:
toolbar.iconbar.unfocused.font: <font>
toolbar.iconbar.unfocused.justify: <{Left|Right|Center}>
toolbar.iconbar.unfocused.textColor: <color>
toolbar.iconbar.unfocused.justify:
toolbar.pixmap: <filename>
toolbar.shaped: <boolean>
toolbar.workspace.font: <font>
toolbar.workspace.justify: <{Left|Right|Center}>
toolbar.workspace.textColor: <color>
toolbar.workspace: <texture type>
toolbar.workspace.borderColor: <color>
toolbar.workspace.borderWidth: <integer>
toolbar.workspace.color: <color>
toolbar.workspace.colorTo: <color>
toolbar.workspace.pixmap: <filename>
.EE
.SH EXAMPLES
This may seem like a long list, but remember, when you create your own style, you
can easily set lots of keys with a single command, e.g.
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:
.EX
.ta \w'*unfocus.textColor:\ 'u
*color: slategrey
@ -440,14 +488,15 @@ can easily set lots of keys with a single command, e.g.
*unfocus.textColor: lightgrey
*font: lucidasans-10
.EE
This sets already nice defaults for many components.
This sets nice defaults for many components.
.SH COLOR FORMATS
These are the color formats for styles:
.EX
#000000 (Hexadecimal)
/usr/X11R6/lib/X11/rgb.txt
rgb:<0-255>/<0-255>/<0-255>
.EE
See /usr/X11R6/lib/X11/rgb.txt for an explaination.
.SH AUTHOR and CREDITS
Blackbox was written and maintained by Brad Hughes
@ -473,17 +522,21 @@ The Official Fluxbox website:
.PP
Fluxmod was a Fluxbox community site where you could find many new styles that
work with this version of Fluxbox and take advantage of all the new features.
However, fluxmod is no more, but a new site gaining popularity is:
However, fluxmod is no more, but it's maintainer still dabbles in style
creation. You can find his site here:
.nh
.B http://www.fluxcandy.org
.B http://www.ikaro.dk
.hy
.PP
You can also find more styles here:
.nh
.B http://themes.freshmeat.net/
.PP
This manpage was composed from various resources including the documentation, fluxbox
man page and numerous other resources by Curt Micol
This manpage was composed from various resources including the official
documentation,
.IR 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:
.nh
<asenchi@asenchi.com>
.hy
@ -494,9 +547,7 @@ and using the great contributions of
Numerous other languages could be available if someone jumps in.
.SH SEE ALSO
.IR fluxbox(1)
.IR fbsetbg(1)
.IR bsetroot(1)
.\" ADDITIONS TO MAKE
.\" Change layout of theme items
.\" Become a little more verbose on color usage.
.\"