fluxbox-style

NAME

fluxbox-style - A comprehensive look at styles/themes for fluxbox(1).

SYNOPSIS

This document describes various options available for fluxbox styles.

DESCRIPTION

What is a Style? 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 look of the look and feel. 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 System Styles menu under your main fluxbox(1) menu. 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.

STRUCTURE

A style is made up of a few major components which then have their own sub-directives. The major components are as follows: The window.* directives control the appearance of the window frames, window.tab.* controls the appearance of the window tabs, menu.* controls the appearance of the popup menu that you see when you right click on the desktop. toolbar.* is the bar you will see at the top or bottom of your screen. Finally the 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 toolbar directives instead. 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. A more complete reference to this can be found in X(7), section RESOURCES.

LOCATION

There are many places to store your styles, the most common is in your ~/.fluxbox/styles directory. The initial installation will place the default styles in /usr/share/fluxbox/styles providing a basic usable configuration. When creating your own style, create a directory (normally the name of your style) in ~/.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: Output of a packaged style should look like the following: 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. :)

CREATING YOUR STYLE

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. Here are some quick examples to illustrate basic syntax: This sets the color resource of the toolbar clock to green. Another example: This sets the color resource of the menu and all of its children to ‘rgb:3/4/5’. (For a description of color names, see X(1).) So this one also applies to menu.title.color and menu.frame.color. And with 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).) 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: 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: With that all of the text will be rgb:3/4/5 except the toolbar clock text which will be rgb:255/0/0. 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.: Don’t worry, we will explain what these mean. A texture description consists of up to five fields, which are as follows: Flat | Raised | Sunken. gives the component either a flat, raised or sunken appearance. Gradient | Solid. tells fluxbox(1) to draw either a solid color or a gradient texture. Horizontal | Vertical | Diagonal | Crossdiagonal | Pipecross | Elliptic | Rectangle | Pyramid. Select one of these texture types. They only work when Gradient is specified. Interlaced. 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. Bevel1 | Bevel2. 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. Instead of a texture description, also the option ParentRelative is available, which makes the component appear as a part of its parent, e.g. totally transparent. 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. 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. All gradiented textures are composed of two color values: the color and colorTo resources. When Interlaced is used in Solid mode, the colorTo resource is used to find the interlacing color.

FONT EFFECTS

In addition to specifying the font-family and the font-weight via the supported font-rendering-engine (eg, Xft), fluxbox(1) supports some effects: halo and shadow. To set the shadow effect: To set the halo effect:

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

FULL COMPONENT LIST

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 appropriately. 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.

WINDOW OPTIONS

Many, many things you can do with window design in fluxbox(1), below are your options. Have fun.

MENU OPTIONS

Everything you need to make your menu look pretty.

BACKGROUND

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, fluxbox(1) will call fbsetbg(1) 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 fbsetroot(1) 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 “fbsetbg -z” to restore the last wallpaper).

SLIT

Here are all of the options for the slit.

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.

EXAMPLES

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: This sets nice defaults for many components.

COLOR FORMATS

These are the color formats for styles: See /usr/share/X11/rgb.txt for an explanation.

AUTHORS

Blackbox was written and maintained by Brad Hughes <blackbox at alug.org> and Jeff Raven <jraven at psu.edu>. fluxbox(1) is written and maintained by Henrik Kinnunen <fluxgen at fluxbox.org> with contributions and patches merged from many individuals around the world. The Official fluxbox(1) website: http://www.fluxbox.org You can find a lot of styles here: http://tenr.de/ 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.

SEE ALSO

fluxbox(1) fbsetbg(1) fbsetroot(1)

AUTHOR

Henrik Kinnunen <[email protected]>