I don’t think it would be fair to any discussion on Fluxbox to fail to mention Tabs. Everybody loves tabs. Tabbed browsing has taken web browsers by storm. Tabbed file managers are becoming the next big thing. It should be no surprise that Fluxbox has had tabbed windowing for years.
Fluxbox allows you to merge several applications’ windows together into one… for lack of a better term: unit. The unit then has tabs for each application that you can flip between. You can move the unit around on the workspace, move it to other workspaces, etc., and thus, all the apps move around together. The unit then has a single icon in the Iconbar, and all the apps then share other states as well. Some people call this the best feature of Fluxbox.
Personally, I don’t use this feature much, but I can think of the advantages. For example, say I hated multiple workspaces, and thus, needed to have all my apps on one. My Iconbar would be packed full, and I wouldn’t be able to see any information in them. With tabs I could lump my three or four Firefox windows into one, and all my Open Office docs onto another, then my two Bluefish projects into one, all the Gimp windows into one. Suddenly I’d have reduced the number of icons down to four, a far more manageable number.
There are many third party apps developed to work with Fluxbox to extend its functionality. For example, if you absolutely adore those pretty little icons on your desktop, you can use Fbdesk or Idesk to get them back. Try Google and the Fluxbox Wiki for more.
Fluxbox comes with a great number of “System Styles” or “Themes” which allow you to change the basic appearance of the Toolbar, Root Menu, window appearance, etc. Fluxbox also allows you to have other “User Styles” which are simply placed in the ~/.fluxbox/styles/ directory. There are hundreds of User Styles available for download off the net, but one can also go about creating one’s own. Personally, I tend to find a style close to what I want, then make changes to please my overly critical eye. This is remarkably easy as styles are defined in a single text file that is not too complicated. This guy has some more information. Styles, both System and User, are easily changed via the Root Menu.
I think I should note here that the Fluxbox style will likely not do everything you want. To get the complete look you’re after, you also have to change your GkrellM theme – if you use it – of which 191 themes are available in a single tarball here (untar into ~/.gkrellm2/themes/).
More importantly, many applications use what is called a GUI toolkit for designing their windows. There are several toolkits in use on *nix systems, predominantly GTK (most Gnome apps) and QT (most KDE apps). Some GTK themes are available here. It doesn’t matter where they are placed as long as in your home directory you link .gtkrc and .gtkrc-2.0 to the appropriate files in the theme’s directory (should be obvious). QT can be changed in several ways: if KDE is installed you can use the kcontrol app, and on some systems you can use qt3-qtconfig. There are also various third-party apps that allow you to use one theme for both GTK and QT toolkits.
Between your Fluxbox style and your GTK/QT style, with perhaps a little editing by hand, you should be able to get the look you’re after. Add in a similar GkrellM (or other applet) theme, a really cool background image, customize some aterms, and you’ve got that badass Linux system that makes your geek friends drool and your *doze friends start asking how hard it is to learn Linux.
But while you can really impress with the appearance of Fluxbox, that won’t be why you stay with it. Much of what you can visually do with it can be accomplished with other window managers, although the task might be a tad more difficult. Beyond the superficial lies the truly brilliant design that ties all the functionality for highly efficient day-to-day operation into a mere handful of easy-to-edit text files. And once you really start using that functionality, when you try to flip back to other window managers you’ll find yourself increasingly frustrated by their failings and limitations, and asking the bewildering question, “Why don’t they just implement something simple to fix this – like Fluxbox?”