The Artists' Guide to the Linux Desktop—Part IV
The two previous articles in this series were focused on particular window managers: Enlightenment and Window Maker. I looked very closely at those two window managers because they epitomize the personalization that is possible in the Linux desktop. Unlike in the Mac or PC world, the look and feel of the Linux desktop can vary to the extreme. One Linux user's windowing interface need not look—or act—anything like anyone else's. The windowing interface you choose is like a big empty apartment. Not until you add the furniture and hang some pictures does it become a livable space. The kitchen is still a kitchen, but in Linux, it's your kitchen.
In this, the fourth and final part of the series, I'm going to take a quick look at some of the other, less well-known window managers available for Linux. Most of them have unique benefits over any other window manager—smaller memory footprints, more efficient code, better extensibility and so forth. They all look and behave slightly differently, although aside from AfterStep, none are designed with the graphical variety intended in both Enlightenment and Window Maker. That doesn't mean you don't want to consider them. On the contrary, there are definite situations in which you'll want to consider these alternatives, particularly if you do much work on a laptop.
Requirements: XPM, JPEG and PNG libraries are recommended, but these should already be on any recent Linux distribution.
Compliance: GNOME (partial), KDE (unknown)
Extras: if it runs on Window Maker, chances are good it runs with AfterStep, but it's not guaranteed.
When I originally started this series, I had planned on looking at AfterStep in the same thorough manner I looked at E and Window Maker. After doing some research, I discovered Window Maker and AfterStep are pretty much the same beast. Internally and politically they may differ, but from an end-user perspective they're very similar, so much that if you read the previous article, you're up to date with AfterStep.
Still, there are a few things I need to mention about this window manager. AfterStep adds a bar across the top of the display, similar to the task bar of GNOME and KDE. The bar actually shows up only when the first application has been started; after that, each application gets added to the bar. It allows you to jump to applications very quickly, although personally I don't particularly like these types of features.
AfterStep features can be enabled or disabled prior to compiling the software. The configure script has far more options than most of the other window managers. This allows you to turn off some features, hopefully slimming down the window manager for use on resource-limited systems. However, if you use the -prefix option, be aware that the “make install” process doesn't create the /bin and /man directories under the directory you specified—you'll have to do that manually.
Unlike Window Maker, AfterStep has a pager similar to FVWM's pager, which I like quite a bit. It appears to look and work much like the one I'm used to and is available in the default configuration. Although I probably won't switch to AfterStep (the icon features I disliked in Window Maker are also present in AfterStep), I am more curious about it now that I've found a reasonable pager.
Compliance: GNOME (no), KDE (partial)
Extras: BBPager, BBTime, various others; all available from the main Blackbox site. Supports Window Maker dock applications through the use of a built-in tool called the Slit.
Of all the window managers I tried, Blackbox is certainly the easiest to build and install. It needs no special libraries, has no special requirements and took only a minute or two to compile. Obviously, this will depend on your hardware configuration, but the point is, this is the slimmest, most streamlined window manager available. That also means it's the one with the fewest bells and whistles.
While most of the other window managers provide some form of pizzazz through icons or image handling, Blackbox provides nothing more than simple gradients. It does include a tool for placing background images on the root window, but that's about all the pizzazz you'll find here. Still, the implementation does include support for dockable applications from Window Maker, through a built-in function called the Slit. I didn't try this feature, since the point of Blackbox is to not add snazzy appearance. It's truly a window manager designed to provide a decent look with as small a memory footprint as possible. This makes Blackbox a likely candidate for use on laptops.
Like with most window managers, you have to edit text files to make changes to the root menu. This isn't a serious problem, however. A fairly complete description of the menu file format is available on-line, linked from the Blackbox web site.
Blackbox has a panel across the bottom of the screen which includes a clock, two sets of arrows for cycling through windows and desktops, and an area displaying the title from the window which currently has the keyboard focus. An additional tool, BBPager, is available which provides many of the same pager features that FVWM's and AfterStep's pagers do. Although the pager accepts standard -geometry settings to set its position on the screen, the panel appears to be forced to the bottom of the display. I'd like a way of changing that, to move it to the top or side of the display, but didn't see whether that was possible.
One thing Blackbox doesn't do is enforce edge resistance by default. Edge resistance lets you slide a window up against an edge of the display, but not past it without a little applied force. I like window managers that do this; I seldom use windows that span workspaces, but do like to butt windows up against the edge of the display.
In general, I like Blackbox; I just need to learn how to configure it properly.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide