Comments on: Back to Openbox

By: K.Mandla

K.Mandla — Mon, 03 Jan 2011 02:57:54 +0000

They have similarities and differences; for my own part Openbox is cleaner and less obsfuscated. It’s rare that I see a Fluxbox setup that doesn’t confuse me with endless submenus and configuration options.

On the other hand …

http://kmandla.wordpress.com/2010/05/14/carving-up-the-corpse-of-fluxbuntu/

By: samspade10

samspade10 — Mon, 03 Jan 2011 01:43:46 +0000

How different is Openbox to Fluxbox/ I’ve been using Fluxpup (Puppy Linux with Fluxbox) for nearly two years but I think Fluxbox is now no longer updated (what is the proper word for that?) so I’ll have to make the switch at some point I guess.

Is Openbox as easy to configure for keyboard shortcuts?

By: technologyunit

technologyunit — Thu, 30 Dec 2010 01:41:57 +0000

I have always been impartial to very simple desktops, but always found my self dragged back to Gnome. Heck my gnome desktop doesn’t have any gnome panels, but instead I use AWN docks because they are more fun and versatile However it always seame as though you stick to small little Linux distros than the big fat fat-clients like Ubuntu. Why is this? Is it just a preference or is it hardware condition, or …..

Thanks… Like the wallpaper as well.

Sincerely

Tobias Mann

By: K.Mandla

K.Mandla — Mon, 27 Dec 2010 22:58:35 +0000

I think this had something to do with the way the closing application was storing its last window position, and how IceWM was interpreting that location when the application was reopened. I hadn’t ever noticed it before, but every time I opened the application, the box shifted downward slightly. It’s not a big deal, but it was one of those things I couldn’t seem to correct without undue labor.

And I don’t know if menu maker would have solved the menu problem or not. I literally entered one blank line in a working .icewm/menu file, and suddenly the file was unreadable. Very strange.

No matter. I’m sure I will be back to it in the future. I just need a little break, that’s all.

By: mulenmar

mulenmar — Mon, 27 Dec 2010 17:43:59 +0000

I don’t know if IceWM has a function to store the screen position of windows or not, but if you want a menu just use menumaker and then add or change a few lines as you see fit.

By: K.Mandla

K.Mandla — Mon, 27 Dec 2010 13:45:21 +0000

Sheesh! I gotta do everything around this place.

Enjoy!

By: jengtron

jengtron — Mon, 27 Dec 2010 12:28:53 +0000

thanks for sharing your conky mind sharing also your wallpaper? its gorgeous!

By: K.Mandla

K.Mandla — Sun, 26 Dec 2010 13:01:21 +0000

No, although any time I can impress a nerd, I call it a successful day.

Mostly I was having problems with windows migrating southward after they were closed and reopened. That, and editing the menu was somehow corrupting it and making it unreadable to the running session.

Little things like that were starting to annoy me. I should have probably just started over from scratch, with a blank IceWM installation. But the idea of building these things up from nothing is sometimes intimidating.

By: K.Mandla

K.Mandla — Sun, 26 Dec 2010 12:59:32 +0000

Sure! Although LXDE adds a lot of cool tools to the entire experience. And using LXDE doesn’t necessarily require you to use openbox, I don’t think.

By: K.Mandla

K.Mandla — Sun, 26 Dec 2010 12:54:19 +0000

I am vaguely surprised. I never thought it that interesting. Oh well, here goes:

background yes 
use_xft yes 
xftfont Dejavu Sans:size=8 
xftalpha 0.8 
update_interval 2 
own_window no 
double_buffer yes 
draw_shades yes 
draw_outline no 
border_margin 0 
border_width 1 
default_color white 
default_shade_color black 
alignment bottom_left 
minimum_size 1006 
gap_x 9 
gap_y 9 
use_spacer no 
no_buffers yes 
uppercase no 

TEXT 
${alignc}${color white}$sysname $kernel ${color darkgrey}on ${color white}$nodename ${color darkgrey}[${color white}${freq}Mhz ${execi 1000 cat /proc/cpuinfo | grep -m 1 'model name' | sed -e 's/model name.*: //' | sed -e 's/  //g'}${color darkgrey}] | ${color white}$uptime_short ${color darkgrey}uptime at ${color white}$cpu% ${color darkgrey}cpu load with ${color white}${mem}${color darkgrey} of ${color white}${memmax}${color darkgrey} (${color white}$memperc%${color darkgrey}) used by ${color white}$processes ${color darkgrey}processes 
${alignc}${color white}${fs_used /}${color darkgrey} of ${color  white}${fs_size /}${color darkgrey} root partition used, ${color  white}${fs_used /home}${color darkgrey} of ${color white}${fs_size  /home}${color darkgrey} home partition used | ${color white}${downspeed  eth0} kbps${color darkgrey} down (${color white}${totaldown eth0}${color  darkgrey} total), ${color white}${upspeed eth0} kbps${color darkgrey} up  (${color white}${totalup eth0}${color darkgrey} total) on ${color  white}${addr eth0}

Be careful, WordPress.com enjoys eating code even when it’s tagged for source code.

The sed-fu in there only strips out excess spaces from /proc/cpuinfo, so you might want to remove or edit it. Have fun!