The first thing to know about the Slit is that it is not the Fluxbox taskbar.
The Slit is a place where dockable applications can 'dock'. We have an entire chapter devoted to the Slit: Chapter 7. Read it before asking any questions about what the slit is and how it works.
In Fluxbox versions after 0.1.10, yes. There's an explanation in Chapter 7.
Change this line in your init:
session.screen0.strftimeFormat: %a %d %H:%M
For information on the format, run man 3 strftime on your machine.
This is a bug in versions of Fluxbox prior to 0.1.8-bugfix2. Please upgrade to the latest version / bugfix before reporting this.
See Chapter 4.
As soon as you activate AA with Fluxbox, it relies on Freetype2 to render the characters. If you don't use AA, X11s native font rendering can be used. As FT2 does not support all the formats that X11 supports, the choice of fonts for Fluxbox becomes limited. As of this writing, FT2 supports the following formats:
TrueType files (.ttf) and collections (.ttc)
Type 1 font files both in ASCII (.pfa) or binary (.pfb) format
Type 1 Multiple Master fonts
Type 1 CID-keyed fonts
OpenType/CFF (.otf) fonts
CFF/Type 2 fonts
Adobe CEF fonts (.cef)
Windows FNT/FON bitmap fonts
Freetype 1, on the other hand, does only support TrueType fonts, although support for GX and OTF fonts can be enabled by using another library. Details can be found on the Freetype homepage.
There is an explanation in Appendix D
If you like the Artwiz fonts, but don't like the way they look in terminals, consider checking out the LFP fontpack, from the Linux Font Project. There are two sets of fonts there, The LFP Fixed-Width Fonts (good for terminals), and LFP Variable-Width Fonts (good for other things). The fixed-width fonts are also available for the Linux console.
This is explained in Chapter 6.
There is a solution in Chapter 6.
You may certainly, be sure to add some lines for titlebar and keygrabbing, though. It may also be wise to symlink your blackboxrc and ~/.fluxbox/init together somehow.
See Appendix A.
Yes. The tarballs for both packages should be 100% interchangeable. This should also stay true for the Waimea and Openbox projects, although I can't guarantee it. I've not seen such a promise from either of the two projects, but one of the goals of Fluxbox is to stay compatible with Blackbox styles.
See Appendix A.
Yeah, use the configure option --enable-kde. This ensures that KDE tray icons will appear in the slit.
Yeah, use the configure option --enable-gnome. This enables the Gnome hints. In Fluxbox versions 0.1.12 and later this is the default.
Simply link your ~/.blackboxrc to your ~/.fluxbox/init, for example with this command:
$ ln -s ~/.fluxbox/init ~/.blackboxrc
0.1.14 or preceeding versions.
To make the tabs look (even more) pretty you'll need to add some extra entries to your desired style (theme). However, note that you don't have to do this, Fluxbox is very capable of setting the tabs to a proper color/style by itself, but if you want to have more control of how they look, you might want to add a few lines like this:
Example B-1. Customized tabs in style file
! -- tab style (for Fluxbox) window.tab.justify: Right window.tab.label.unfocus: Flat Solid window.tab.label.unfocus.color: rgb:AC/AC/AC window.tab.label.unfocus.textColor: black window.tab.label.focus: Raised Solid window.tab.label.focus.color: rgb:CC/CC/CC window.tab.label.focus.textColor: black window.tab.borderWidth: 1 window.tab.borderColor: rgb:10/10/10 window.tab.font: fixed ! --- end, tab style
Okay, so what does all this do then? Well the same stuff as any other thing in a theme, I'm sure you get it if you have ever made a Blackbox theme before (Chapter 10 might be interesting if you haven't).
Also note that a style containing these extra entries will still work perfectly in Blackbox, so you loose nothing by adding this.