These are screenshots of the desktops I have used in 2015. No dramatic changes–still using Openbox, still loving the Erthe theme for work, still keeping it simple.

Early in the year I replaced Varuna, a Thinkpad X60 that was prone to overheat, with Soma, a Thinkpad X200. The screenshots of both are of a 23″ screen I use with it. Savitar is my old, battered, but beloved Thinkpad X41. On Soma, I’ve mainly used the last two desktops. The two screenshots of Savitar are those from last year, as I did not change anything to that desktop the entire year. Savitar is still my work laptop.

Varuna

beatus01

Openbox 3.5.2, with the Mythos Gtk and Openbox themes, and the AnyColorYouLike (ACYL) icon theme.

Soma

wave02

Openbox 3.5.2, with the Alghattas Gtk and Openbox themes, and the MeliaeSVG icon theme. I can’t remember where I found the wallpaper image.

caitanya01

kcaitanya02

Openbox 3.5.2, with the Alghattas Gtk and Openbox themes, and the MeliaeSVG icon theme.

journey01

Openbox 3.5.2, with an unreleased Gtk and Openbox themes, and the ACYL icon theme. The wallpaper is from here (G3, scaling the 960×800 image with Feh).

Savitar

erthe02

erthe01

Gnome 2.30.2 with Openbox 3.5.0, still using the Erthe themes and ACYL icon theme.

 

 

Advertisements

These are the very few screenshots I took in 2014. I change my desktop much less frequently than I used to when I started documenting this, seven years ago, but it still serves as a good index of my thoughts and moods of the past year.

Savitar is a Thinkpad X41, running Debian Testing, with Openbox and Gnome 2.30 (still!). It is the computer I use for most of my work, and its looks have changed very little since 2012. Varuna is a Thinkpad X60, with an external monitor, running Linux Mint Debian edition. I generally use Openbox on it (with several Xfce components) and occasionally Pekwm. The second desktop setup, with the Groove themes, is the one I used for most of 2014.

Varuna

peaks01

peaks02

Openbox 3.5, with the Laza-mod themes.

groove01

Openbox 3.5, with the Groove themes, and the ported AestheticGroove icon theme.

Fawn-pekwm

Pekwm 0.1.17, with the Fawn Gtk and Pekwm theme, and the Children of the Earth icon theme.

Savitar

erthe02

erthe01

Gnome 2.30.2 with Openbox 3.5.0, still using the Erthe themes and ACYL icon theme.

I still use Openbox daily, but recently decided to finally give some of the big desktop environments a serious try. The last time I really tried Gnome or KDE was before their big shifts (to 3. and 4. respectively). A friend had been speaking highly of the latest Gnome versions and claimed several features of it enhanced his workflow and productivity. Was I missing out on all these great developments by sticking with Openbox? I gave Gnome and KDE another try, using them for my usual work for a few days each. There are indeed some nice features in these newer versions, and I particularly liked some of the new aspects of KDE.

But I am now back with Openbox, because I feel so much more at home in it (having spent a few years fine tuning a desktop that suits my needs), and because I still don’t understand why I need to spend so much of my laptop’s resources on window and desktop management (resources that are not a plenty with older laptops!).

One feature of KDE I particularly liked: middle click on the desktop and the text in your primary X clipboard (the clipboard that contains the text that is merely highlighted, and that is normally pasted with a middle mouse click) is pasted into a new note on the desktop. Very handy for information you quickly want to store somewhere (for however long you want to)!

When I moved back to Openbox, I immediately decided to implement that in my Openbox desktop, using xpad. Here is how I did it.

Open your favourite text editor and create the following script:

#!/bin/sh
FILE="/tmp/xpadclick.txt"
xclip -selection p -o > $FILE ; xpad --new-from-file=$FILE

(If, for some reason, you want this to work with the text you copied with Ctrl+C use “xclip -selection c -o” instead of “xclip -selection p -o” in the above script.)

Note that this requires xclip to be installed (besides xpad, obviously). If you don’t have it installed, you can do so on Debian systems with the following command:

sudo apt-get install xclip

Save the script (I saved it as ~/.scripts/xpad-middleclick.sh), and make it executable (chmod +x ~/.scripts/xpad-middleclick.sh).

Now you have to tell Openbox to run the script whenever you middle click on the desktop. Open your rc.xml file and search for <mousebind action=”Press” button=”Middle”> in the mouse section, under <context name=”Root”>. The default is as follows:

<mousebind button="Middle" action="Press">
<action name="ShowMenu"><menu>client-list-combined-menu</menu></action>
</mousebind>

Change this into the following (make sure the path points to wherever you saved the above script):

<mousebind action="Press" button="Middle">
<action name="Execute">
<execute>~/.scripts/xpad-middleclick.sh</execute>
</action>
</mousebind>

Reconfigure Openbox, and you can quickly create an xpad note of the selected text whenever you middle click on the desktop.

If you don’t want Openbox to draw window decorations for xpad, add the following to your rc.xml (in the applications section):

<application name="xpad">
<decor>no</decor>
</application>

And here is a totally unnecessary picture of the end result:

xpadnote

(For those of you who prefer Tomboy: I’m not sure whether you can do this with Tomboy. Unlike xpad, Tomboy does not have a cli option to create a new note from file. Perhaps it is possible to achieve a similar result using tomboycli, but I have not tried to do so.)

This is my fifth annual screenshot review, recording my changing aesthetics and moods. Early in the year, I moved back to Gnome (with Openbox, of course) on my laptop (Savitar, a Thinkpad X41), and in November began using MATE on my desktop (Loka). Early in the year, for a few months I also returned to Pekwm, a wonderful little window manager I hadn’t used much in the previous year. I also played with Awesome for a short while, but that window manager, however much I like it, remains more of a distracting novelty for me than an productive work environment.

As you can see below, I’ve mainly used dark themes this year (and particularly the Erthe themes), and have changed my setup a lot less often than I did when I started posting these annual overviews.

Both Savitar and Loka still run Debian Testing (Wheezy), though Savitar’s is far from up to date (as should be obvious from the Gnome 2 screenshots below).

All my Openbox and Gtk themes (including those that I merely modified) can now be found on github.

Savitar

Gnome 2, with Openbox, using the Erthe themes, and the AnyColorYouLike icons.

Openbox 3.5, with the Dandelion Openbox and Gtk theme, and the nuoveXT-1.7 icons. The desktop background is a painting of the Six Gosvamis of Vrindavan.

Gnome 2, with Openbox, using the Erthe themes, and the AnyColorYouLike icons. The desktop background I found here.

Loka

Pekwm, with the Infinity Pekwm and Gtk theme, and the moblin icons.

Pekwm with the Royalty themes, and the AnyColorYouLike icons.

Openbox 3.5, with modified royalty themes and Somatic icons. The dock holds bbdock, bbpager, lal, and docker.

Openbox 3.5 and XFCE 4.8, with the Erthe themes, and AnyColorYouLike icons.

Awesome 3.4.13, with the Eidolon themes.

MATE 1.4.2 with Openbox 3.5, using modified Laza themes and the Gnome-Noble icons.

Probably more for my own amusement (especially in a year’s time) than for anyone else’s, and in an attempt to document the evolution of my aesthetics, I here give a summary of my own 2008, in screenshots.

The wallpapers I use for my desktops generally reflect my mood, and have some special significance for me at the time. What follows is therefore not just a collection of screenshots, but a reflection of what has been on my mind the last year. Not all the screenshots I’ve taken the past year are here. I’ve left out the odd desktops (like this one or this one) that didn’t last very long.

The screenshots are arranged per computer, roughly chronologically. Yantra is my main computer, on which I do most of my work. Grantha is the computer at my office. Mitra is the old Dell Inspiron 2500 laptop I wrote about earlier.

Most of the screenshots are of Openbox, which I started using in early 2007 (if my memory serves me well…). By the end of 2007, I discovered Pekwm and used that window manager almost exclusively for a few months in the beginning of 2008. In the summer, I started experimenting with Awesome 2.3, which became the standard window manager on one of my computers (mitra), and which I use frequently on another (yantra). All of these screenshots are of Debian or Ubuntu systems. Early in 2008, grantha still ran Windows XP, but that now runs Debian Testing (lenny). One of the early mitra screenshots may be one of Arch Linux, which I had installed on that laptop for a few weeks when I just started using it.

I’ve been using the same themes on grantha and mitra for months now (see the last screenshots for both). The themes on yantra tend to change more often, though I’ve been alternating a lot the last few months between the Children of the Earth themes and the Mythos theme.

I’ve had a lot of dark desktops this year, and have used a couple of dark Gtk themes often (Royalty, Mythos and Eidolon). It really is very pleasant on the eyes, especially at night, even if not all websites go well with it.

For all of you with a slow internet connection: know that this is quite a lengthy post, with more than 40 300×225 thumbnails!

Read the rest of this entry »

Changing the size of BBdock

December 2, 2008

EDIT: It turns out that all this can be accomplished in a much easier way by launching BBdock with the command “bbdock -d 24×24” (or width x height), as David mentions in the first comment to this post. Oh well… 🙂

BBdock, one of the many useful little applications created to work with Blackbox, is a handy application launcher or dock. Though created for Blackbox and not updated in a few years, it can be used in any window manager that has a place to load dockapps, such as Openbox or Fluxbox. It is entirely configurable in a single text file (~/.bbdockrc). You can any .png file you want for the icons, and BBdock is able to raise applications you have already launched, instead of launching a new one.

The only downside to BBdock is its size. The default icon size it uses is the standard 64×64 of WindowMaker dockapps. Even if you use smaller image files, the dock itself will remain at that clunky size.

Luckily, this is not very hard to change. I prefer to have icons of 24×24, so that BBdock integrates nicely with lal, and bbpager (another one of the BBtools). Here is picture of BBdock and some other dockapps running in Openbox:

bbdock

BBdock, lal, BBpager, and docker in Openbox 3.4.7

So, how do you change the default size? You’ll need to edit the source code and then compile that, so start by downloading the source code from the BBdock website:

	wget http://bbdock.nethence.com/download/bbdock-0.2.8.tar.gz

Extract the archive, and move into the src directory of the newly extracted tarbal:

	tar xzf bbdock-0.2.8.tar.gz
	cd bbdock-0.2.8/src

Next, you’ll have to edit the Dock.hh file:

	nano Dock.hh

Search for the slotwidth( 64 ) and slotheight( 64 ) values (they should be on line 116-117), and change them to whatever size you’d prefer BBdock to use for its icons (I chose a square of 24×24):

	Settings() :
	   slotwidth( 24 ),
	   slotheight( 24 ),

Save the file and exit. Now you can compile the source code in the usual way. First install the necessary dependencies (make sure you have the source (deb-src) urls enabled in /etc/apt/sources.list!):

	sudo apt-get build-dep bbdock

Move back into the root directory of the source code, compile and install BBdock:

	cd ..
	./configure
	make
	sudo make install

(Use sudo checkinstall if you’d like to create a .deb package of the source code and install that, so that you can remove it easily later on through apt, aptitude or Synaptic)

If the installation is successful, the default icon size will be 24×24 (or whatever else you specified). Note that this size is static; even if you use smaller or bigger images, the size will remain the same.

To configure BBdock, create and edit the ~/.bbdockrc file. Each line in that file configures an icon in bbdock. You first specify the path to the icon file, followed by the command BBdock should execute when you click on the icon. If you’d like BBdock to raise applications that have already been launched instead of raising a new instance, you can specify that too. Here are some examples from my ~/.bbdockrc:

	~/.icons/bbdock/window.png:xte 'key Pause'::
	~/.icons/bbdock/text.png:mousepad::
	~/.icons/bbdock/opera.png:opera:*opera
	

The first icon uses xte to simulate a keypress of the PrintScreen key, which I have configured in Openbox’s rc.xml to launch the client-list-combined-menu which shows all running applications on all desktops. The second icon will launch a new instance of Mousepad whenever I click the icon, and the third icon will launch Opera or raise an already running instance of Opera.

Here is a question to all of my kind hearted readers with some knowledge of programming. 🙂

I’m one of those users that loves the dock in Openbox. For nearly as long as I’ve been using Openbox (once I figured out what it really was), I’ve used it to load the few things I normally required from a panel: a clock (initially bbtime and later lal) and a system tray/notification area (always the simple docker). Later I added bbpager to it, and now, inspired by mulberry, created a little dock by combining all the above with bbdock (modified so its default icons are 24×24 in size, rather than the standard 64×64). Here is what it looks like:

bbdock, lal, bbpager and docker

I’d like to do more with the dock, though. Unfortunately, most dockapps are either too big (the standard 64X64 Window Maker squares) or aesthetically not very pleasing, or both. The BB-tools, created to be used with Blackbox, are much nicer and smaller, but rather limited and no longer developed (apart from bbpager, it seems).

For a little while now, I’ve been trying to get more things to display in my dock. I’d like to be able to show my reminders in it (using remind), and possibly even things like current cpu/memory usage (in a more attractive way than the existing dockapps). The things I normally use conky or dzen2 for, in other words.

Wouldn’t it be great if you could load conky into the dock? Or even better, wouldn’t it be great if you could load dzen2 into the dock?

Awesome is able to do something like this, by creating widgets with dzen2 and loading them into the statusbar — though this seems a little less complicated than it would be in Openbox (you can’t autohide or move the widgets around like you can in Openbox’ dock).

I don’t know exactly how something similar would be accomplished in Openbox, or even if it could. Perhaps the dzen2 code could be modified so as to give it the window properties of a dockapp, or perhaps this would be done through a third party application that loads into the dock and into which dzen2 loads, perhaps Openbox itself would need to be modified.

I am no programmer — I know just enough bash to get me around and can only make some very simple modifications to existing code, often through trial and much error, and that is about it. But if you are a competent programmer, you share my enthusiasm for this and are willing to invest some time into it, please do! You’d make this happy Openbox user, and perhaps countless others, even happier. And you might even become famous. 😉

My Openbox keybindings

July 22, 2008

One of Openbox’ great strengths is that you can control every aspect of the window manager with your keyboard, provided you spend some time configuring your keybindings. Since I use my computer extensively to process text, I have configured Openbox such that I only need to use the mouse when I really want to, and don’t have to move away from the keyboard. It speeds things up considerably, once you are used to it!

Below I give all the keybindings I use in Openbox. Some of these keybindings I don’t use very regularly. The ones that I use extensively are those that launch applications (Win+F1-9 to launch applications, or Alt+F1-6 to launch menus or application launchers); those that control the volume (Ctrl-Up/Down) and mpc (Ctrl-Alt + other keys); those to switch windows (Alt-Tab and Win-Tab) or to switch workspace (Ctrl-Alt-Left/Right); those for basic window actions, such as close (Win-A-C), maximize (Win-A-M), iconify (Win-A-I), send to bottom (Win-A-B), etc; those to move windows in the current workspace (Win + some direction key); to move windows to the next workspace (Win-A-N) or previous workspace (Win-A-P); or to follow windows to the next (Win-A-Shift-N) or previous workspace (Win-A-Shift-P).

When I mention “(with osdsh)”, it means that the action that is performed is shown on screen with osdsh. Thus, when I reconfigure Openbox, the message “reconfiguring” on my screen, or when I turn the volume up it says “volume up”. (I know osdsh has a mixer display, but that uses a lot of CPU in Hardy!). When I mention “(with script)” in the launcher section, I launch a script to raise the application if it is already running or to open a new instance if it isn’t. The shutdown and logout keybindings (Win-O-S and Win-O-E) launch a gmessage script that gives me the option to reboot, shutdown, logout, or lock the screen.

As you will see below, I make extensive use of keychains. Keychains are great! They enable me to keep most of my keybindings fairly simple and straightforward: Win-A starts the keychain for window actions (thus ‘Win-A + C’ closes the focused window, and ‘Win-A + N moves it to the next workspace); Win-O governs all the Openbox related actions (Reconfiguring, editing the configuration files, etc.).

I have also posted my current rc.xml file, for those interested. I’m pretty sure there are some additional keybindings in that file (probably duplicate actions) that are not mentioned below; if that is the case they are keybindings I no longer use, but forgot to remove.

        #########################
	## Launchers and Menus ##
	#########################
	Alt F1		root menu
	Alt F2		gmrun
	Alt F3		dmenu
	Alt F5		dmenu for configuration files
	Alt F6		client-combined-list
	
	Win F1		mousepad
	Win F2		notecase
	Win F3		xfce4-terminal (script)
	Win F4		thunar (script)
	Win F5		gmpc
	Win F6		epiphany
	Win F7		ooffice writer
	Win F8		opera (script)
	Win F9		stardict
	Win F10		gedit
	Win F11		gnome-alsamixer
	Win F12		Lock screen (xlock)
		
	Ctrl Alt Del	htop
		
	#########
	## MPD ##
	#########
	Ctrl Alt space	mpc toggle (with osdsh)
	Ctlr Alt Prior	mpc next (with osdsh)
	Ctlr Alt Next	mpc previous (with osdsh)
	
	####################
	## Volume control ##
	####################
	Ctrl Up		Volume up (PMC) (with osdsh)
	Ctrl Down	Volume down (PMC) (with osdsh)
	Ctrl Shift Up	Volume up (Master) (with osdsh)
	Ctrl Shift Down	Volume down (Master) (with osdsh)
	Ctrl Alt End	Volume mute (with osdsh)
	
	####################
	## Window actions ##
	####################
	Win a		Window actions
		m	Toggle maximize full
		v	Toggle maximize vertical
		h	Toggle maximize horizontal
		i	Iconify
		c	Close
		s	Toggle Shade
		t	Toggle always on top
		b	Send to bottom
		Shift b	Toggle always below
		Shift l	Send to normal layer
		Shift d	Toggle omnipresent
		d	Toggle decorations
		l	Lower, focus to bottom, unfocus
		p	Send to previous workspace
		n	Send to next workspace
		Shift p	Follow to previous workspace
		Shift n	Follow to next workspace
		
		g	GrowTo
			Left	GrowToEdgeWest
			Right	GrowToEdgeEast
			Down	GrowToEdgeSouth
			Up	GrowToEdgeNorth
			
		Win space	Show client-menu
		
	#############
	## Openbox ##
	#############
	Win o		Openbox actions
		r	Reconfigure (with osdsh)
		c	Edit rc.xml
		m	Edit menu.xml
		s	Shutdown (gmessage)
		e	Exit/logout (gmessage)
		l	Lock screen (xlock)
	
	###############
	## Worspaces ##
	###############
	Ctrl Alt Left	Go to the workspace on the left
	Ctrl Alt Right	Go to the workspace on the right
	Alt Shift Left	Send window to the workspace on the left
	Alt Shift Right	Send window to the workspace on the right
	
	Win Shift F1	Send window to workspace 1
	Win Shift F2	Send window to workspace 2
	Win Shift F3	Send window to workspace 3
	
	Win d		Show desktop
		
	######################
	## Window switching ##
	######################
	Alt Tab		Next window
	Alt Shift Tab	Previous window
	Win Tab		Next window (all desktops)
	Win Shift Tab	Previous window (all desktops)
	
	##################
	## Move Windows ##
	##################
	Win Left	Move window left
	Win Right	Move window right
	Win Down	Move window down
	Win Up		Move window up
	
	Win Prior	Move window to top right corner
	Win Next	Move window to bottom right corner
	Win Home	Move window to top left corner
	Win End		Move window to bottom left corner
		
	####################
	## Resize Windows ##
	####################
	Alt Left	Increase left edge
	Alt Right	Increase right edge
	Alt Up		Increase top edge
	Alt Down	Increase bottom edge
		
	Alt Shift Left	Decrease right edge
	Alt Shift Right	Decrease left edge
	Alt Shift  Up	Decrease bottom edge
	Alt Shift Down	Decrease top edge
	
	Alt F12		Toggle fullscreen
	
		
	Ctrl Alt d	Toggle autohide dock

A “tabbed” desktop

July 21, 2008

K.Mandla has already written about my “tabbed desktop”. Here is a little more information:

To create the effect of a ‘tabbed’ desktop, I have been running tint2 at the top of my screen, covering the window decorations. With the right colour and size settings, you can easily create the appearance of a tabbed desktop.

Hayagriva and my “tabbed” desktop

Two things make this method somewhat practical: First of all, I run most of my applications maximized; smaller, ‘floating’ windows somewhat destroy the tabbed feel of the desktop. Secondly, since tint covers the window decorations and makes it thus unable to close, iconify or shade the window, make it sticky, or send it to another desktop, you should be able to perform these actions with the keyboard, through keybindings.

Since K.Mandla’s post, I’ve made a small adjustment to the desktop: I added a clock and remind to my top task bar, using dzen2 (I initially also had a volume bar in it, but dropped that). My dmenu scripts also load in that exact area, using the same colour settings and covering both tint and dzen.

If you’re interested, this is my dzen2 script, and this is my tintrc. The Openbox and Gtk theme I use is Bygone (somewhat modified).

Update!

May 26, 2008

Over the last few weeks, I have slowly been updating the Openbox guide. Openbox 3.4.7 has been out for a little while now, and Ubuntu Hardy was also recently released. I needed to update a few sections of the guide (mainly those covering the installation of Openbox, Obconf and Obmenu, and the shutdown/reboot section). The Openbox FAQ has been changed a little as well.

But this new version of the guide is more than just an update. I have thoroughly revised the entire guide, rewritten some parts of it, and added a lot of new material. So what has changed?

First of all, it has a table of contents now 🙂 , which should make navigation easier and give the reader a better grasp of what areas the guide covers.

I have added a lot of new material to it: I have enlarged the sections on panels, docks, system trays, pagers and clocks. The list of ‘useful applications’ at the end of the guide is now much longer (it now contains eleven applications, whereas the old one contained three). I have tried to give KDE/Qt applications more attention, and included a section on how to deal with Qt themes in Openbox. The guide contains more information about font configuration and mouse cursor themes.

I have tried to clarify and explain the commands and applications more, hopefully making it more accessible and educational for persons relatively new to Linux and/or window managers. I have also added a lot more links to external sources of information, project websites and howtos/guides.

Here are some statistics:

The old guide contained 7275 words; the new version of the guide has 9343 words (2068 words more). The old version had 90 links to external sites, the new version has 159 links (69 links more).

The old guide was completed on 26 November 2007, and revised on 22 January 2008 (some minor changes were made in between and since then). Since it was posted, the Openbox guide has received 14,218 views (13,302 and 916 before it was moved to its own page). That is an rough average of 78 persons a day. Not the most frequented website in the world, but a lot more than I thought I would get when I wrote that guide. The entire blog has had 25,968 people over, so more than half of the views were for the guide. ‘(An) Openbox guide’ is the second most common search term that lead people to my blog (297; the first place is occupied by ‘dmenu‘ with 304 hits — it seems there isn’t that much information about dmenu available on the internet…).

Here is a picture of the stats for this blog:

And here is one for the Openbox guide alone:

Writing and maintaining the Openbox guide sometimes forces me to venture into areas I would normally not go: I don’t like docks, for example, but have tried some of them out so I could write about them. I no longer use xcompmgr and transset, but need to know how to use it as my of the readers of the guide are interested in it. I need to download, compile and install a lot of applications. One of my computers is (not exclusively) used for that. It started with a slim command-line Ubuntu Hardy install, and has now well over a thousand packages installed! I do discover a lot of interesting applications this way, though — especially old(er) ones, many of which are no longer developed, but are still handy, interesting and/or fun.

So that’s it. Go and have a look at the new guide 😉 I hope you find it useful. If you have any suggestions for improvements, or find some grave, less-grave or not-very-grave errors in the guide, please let me know. I love feedback.