VSIDO ISO's Updated
Quote from: PackRat on March 17, 2014, 07:40:54 PMTook a look at IceWm For some odd reason, it regards conky and tint2 as an open window and gives you warning to "save the data" in the conky and tint2 clients before closing.
# Command to start logout# LogoutCommand=""to# Command to start logoutLogoutCommand="vsido-exit"
QuoteFirst you'll need to make sure you have gcc and the necessary development headers installed. On Debian, I think the following packages are necessary:gcc libxpm-dev libxft-dev libxinerama-dev libxmu-dev libx11-dev libjpeg8-dev libfreetype6-dev libfontconfig1-dev libcairo2-dev libpng12-dev libxext-dev libxrender-devYou may not need all of those libraries if you don't want all of the JWM features built in (support for JPEG images, for example). Of course, without installing a fresh install of Debian, it's hard for me to be sure that list is complete.Extract the tarball: tar -xJf jwm-2.2.2.tar.xzNext "cd jwm-2.2.2" and run "./configure". This should report which JWM features will be built in. If some are missing, you should be able to add them by installing additional development libraries and re-running "./configure". If you don't want some of them, re-run "configure" with "--disable-feature" where "feature" is what you want disabled ("--disable-jpeg", for example).By default, JWM will be installed in /usr/local/bin. If you want to change that, you can run configure with "--prefix=/usr", for example, to install JWM in "/usr". There are lots of options to configure, you can see them all by running "./configure --help".Once JWM is configured how you want it, you can build JWM by running "make". Finally, assuming all went well, you can install JWM by running "make install" as root.Now you should have a working copy of JWM installed. Getting it to run at startup is dependent on which login manager you use (if you use one at all). With my setup, I usually have a file "~/.xsession" which is executable ("chmod +x ~/.xsession"). In that file, you can do "exec /usr/local/bin/jwm" (assuming JWM is in /usr/local/bin"). Of course, I don't know if that works for all login managers.You will also want to modify the JWM configuration to your liking. If you don't already have one, "cp /usr/local/etc/system.jwmrc ~/.jwmrc", and modify ~/.jwmrc to point to the programs you want, etc. I recommend running "jwm -p" after modifying the configuration to see if there are any errors.- Joe
Quote from: PackRat on March 16, 2014, 10:13:11 PMI think it is an option on antix and maybe one of the bbq
Quote from: PackRat on March 16, 2014, 09:30:37 PMRevisited jwm window manager the past few days. Wanted something with a bit more Windows-like user interface to set up my kids user account; and since there always seems to be an interest in wm's that are light on resources, I decided to post the results.Version 2.1 is in the Sid repos; or you can get Version 2.2.2 from git - http://www.joewing.net/index.shtml Besides being light on resources (up to 50% less than openbox on some systems, although I get nothing close to that), one thing I like about jwm is that it is self contained. Jwm has it's own panel (called the tray) that can contain a menu, pager, app launch buttons, taskbar, systemtray (called the dock <- poor choice of names there, imo), and the clock. The tray can be horizontal or vertical, and multiple trays can be configured by adding additional Tray entries to the $HOME/.jwmrc; or you can use jwm without a tray by completely removing the Tray section.In addition to the systemtray, jwm also has the ability to swallow apps into the tray - the example in the Arch wiki is to swallow wicd-gtk --tray - but I haven't gotten it to work. Maybe because I pulled the current version from git.The other nice thing about jwm is that it is still being developed by the original author, although there can be a lot of time between releases.All configuration is done through the $HOME/.jwmrc file. This is file is in xml format like the openbox rc.xml file. In addition to the tray configuration, there are sections for autostarted apps, key bindings, and styles - http://www.joewing.net/projects/jwm/config.shtml ; Very easy to navigate and get the wm up and running to suit your needs. However, there are no gui apps to configure the .jwmrc file.Jwm plays well with conky, not so much with compositing (on my system anyway). For the screenshot, I added a second panel with just a clock:So, if you're in the market for a wm that uses a bit less resources that *box, but still want that panel, systemtray, etc ... take a look at jwm.
#!/bin/sh# will need to know actual name of processpgrep wicd --gtk &>/dev/null; [ $? = 0 ] && killall wicd --gtk(sleep 2s && wicd --gtk) &