Page 1 of 2

Memory usage in different window managers

PostPosted: February 9th, 2015, 4:45 pm
by Lou

Re: Memory usage in different window managers

PostPosted: February 9th, 2015, 8:21 pm
by mean_dean
I try others over and over again but always end up back on icewm...

The original icewm project even seems to be abandoned nowadays, which is usually the kick I need to move on, but havent found anything I like better.

Re: Memory usage in different window managers

PostPosted: February 9th, 2015, 11:25 pm
by bmc5311
I just stick with openbox, it easy and simple - like me.

Re: Memory usage in different window managers

PostPosted: February 9th, 2015, 11:37 pm
by Randicus Draco Albus
I fired up the proxy service to look at the WordPress article and was rather disappointed. The article is little more than a list of the most-used WMs with the earth-shattering news that WMs use less memory than DEs. I got the impression the writer's purpose is to inform Ubuntu users that there is more available than just Unity. This Wm uses 3MB of memory, while that WM uses 3 1/2 and that one uses 5MB. I do not find such comparisons very useful. Hardware that can run Openbox can also run Awesome, i3 and IceWM.

Re: Memory usage in different window managers

PostPosted: February 9th, 2015, 11:44 pm
by mean_dean
bmc5311 wrote:I just stick with openbox, it easy and simple - like me.

xml makes my brain explode

seriously though I dont understand the purpose of xml config files

Re: Memory usage in different window managers

PostPosted: February 10th, 2015, 9:13 am
by cynwulf
xml is supposed to be both human readable (right...) and machine readable. It's for GUI based configuration editors, which openbox provides (obconf, obmenu, etc). It's not a huge leap from that to binary config. gnome's config is a good example of this - rather than trawling through six directories deep of xml configuration, while struggling with poor or non-existent documentation - it's easier to just nuke a few of the dot directories and start again...

I prefer fluxbox - it has a panel - and it has human readable plain text configuration. You can literally just open ~/.fluxbox/menu and just bang in whatever you want in your menu and done.

In the article he lists openbox as blackbox derived, which isn't true. Early versions were forked from blackbox, but later on it was completely rebuilt/reimplemented in C and is GPL licenced (fluxbox and blackbox are coded in C++ and MIT licenced).

Re: Memory usage in different window managers

PostPosted: February 10th, 2015, 4:44 pm
by mean_dean
Yea I prefer plain text configs too. Of course xml isn't as bad as I make it out to be, but I gotta have some fun somehow. But yea I guess the structure makes sense for gui tools to parse and the benefit is that it can be human readable and tweakable too.

Re: Memory usage in different window managers

PostPosted: February 10th, 2015, 6:46 pm
by Lou
mean_dean wrote:I try others over and over again but always end up back on icewm...


Ditto here. Lately, i alternate btwn icewm and jwm every other month.

I'm not much of a menu/click and point guy, my choice is keybinds and use the Fn keys to launch everything, even to restart the wm.
Gnome/KDE/Ubuntu are out in my book.

Re: Memory usage in different window managers

PostPosted: February 10th, 2015, 7:46 pm
by mean_dean
cynwulf wrote:You can literally just open ~/.fluxbox/menu and just bang in whatever you want in your menu and done.
argh the brackets and curlys are everywhere :D
thank goodness for copy/paste, didnt take but a minute to turn my icewm menu into fluxbox menu

Code: Select all
prog "iceweasel"        xxx.png         iceweasel
prog "mirage"           xxx.png         mirage
prog "writer"           xxx.png         soffice --writer
prog "calc"             xxx.png         soffice --calc
prog "lxterminal"       xxx.png         lxterminal
prog "gimp"             xxx.png         gimp
prog "pcmanfm"          xxx.png         pcmanfm
prog "geany"            xxx.png         geany
prog "run"              xxx.png         gmrun
menu "mplayer"          xxx.png         {
prog "rock70s"          xxx.png         xterm -e "mplayer /home/user/music/rock70s/*"
prog "rock80s"          xxx.png         xterm -e "mplayer /home/user/music/rock80s/*"
prog "recent"           xxx.png         xterm -e "mplayer /home/user/music/recent/*"
}

Code: Select all
[begin] (fluxbox)
[exec] (run) {gmrun} <>
[exec] (writer) {soffice --writer} <>
[exec] (calc) {soffice --calc} <>
[exec] (pcmanfm) {pcmanfm} <>
[exec] (iceweasel) {iceweasel} <>
[exec] (mirage) {mirage} <>
[exec] (lxterminal) {lxterminal} <>
[exec] (gimp) {gimp} <>
[exec] (geany) {geany} <>
[submenu] (mplayer) {}
[exec] (rock70s) {xterm -e "mplayer /home/user/music/rock70s/*"} <>
[exec] (rock80s) {xterm -e "mplayer /home/user/music/rock80s/*"} <>
[exec] (recent) {xterm -e "mplayer /home/user/music/recent/*"} <>
[end]
[restart] (Restart)
[exit] (Exit)
[end]

Re: Memory usage in different window managers

PostPosted: February 10th, 2015, 7:53 pm
by mean_dean
Lou wrote:Ditto here. Lately, i alternate btwn icewm and jwm every other month.

I usually end up running into some niggle with jwm...cant recall any specifically now tho...will have to try it again...

I'm not much of a menu/click and point guy, my choice is keybinds

I am okay with a menu if my apps are listed without any nesting. That and a good run utility mapped to alt+f2 is my usual method.