/usr/bin/wbar
is the wbar executable
/usr/bin/wbar.sh
looks like a script to kill and restart wbar. I have never directly used this
script but I suspect tce-load calls it after adding an app that has an icon.
/usr/local/tce.wbar
is the "config file" (list of icons, labels and programs) I was trying not to
call it a config file since wbar is "configured" using command line
arguments so I called it an "icon list". Sorry for any confusion caused.
/usr/local/tce.wbar.bak
I suppose this is a backup of the config file. It currently doesn't exist on
my system.
/usr/share/wbar
directory containing the icons for cpanel, appbrowser and the terminal
/usr/share/wbar/dot.wbar
looks like the default content of /usr/local/tce.wbar
/usr/local/bin/wbar0 and /usr/local/bin/wbar1 and /usr/local/bin/wbar2 are all symbolic links to /usr/bin/wbar
ln -s /usr/bin/wbar /usr/local/bin/wbar0
ln -s /usr/bin/wbar /usr/local/bin/wbar1
ln -s /usr/bin/wbar /usr/local/bin/wbar2
/home/tc/.local/bin/wbar0, /home/tc/.local/bin/wbar1 and /home/tc/.local/bin/wbar2 start/restart/kill scripts for their respective counterparts in /usr/local/bin.
I would have put these in /home/tc/bin (and I may yet) except I noticed there's some code in ~tc/,profile to add this directory to the front of $PATH if the directory exists. If I determine that the "." in ".local" is masking this directory from the executable search path, I'll use ~tc/bin and adjust .profile.
My earlier post should have read:
I manually maintain ~/.wbar1 and ~/.wbar2 as the icon lists...
On the command line for /usr/local/bin/wbar1 and /usr/local/bin/wbar2 (in the scripts), I specify the config file as ~tc/.wbar1 and ~tc/wbar2. Since these files are not mentioned in any other scripts, no icons are automatically added to them (I initialize them to the default content of /usr/local/tce.wbar) the only changes that are made to them are those that I manually make with a text editor. I do not specify a config file for /usr/local/bin/wbar0, allowing it to use the default config file (/usr/local/tce.wbar) which -is- maintained by the TC system (icons/apps/added as extensions are loaded with tce-load).
I haven't been loading a lot of apps with this setup in place, but I suspect tce-load will restart the "real" /usr/bin/wbar every time I load an app that has an an icon. Then I'll have to figure a nice automatic way to kill it... or maybe just use that instead of wbar0 and insert my command line options into /usr/bin/wbar.sh.
Caveat: I'm using jwm, not flwm and not using multiple displays or vnc or anything like that... but it seems to me that the the icons ought to be available as long as they get into the config file. Getting the proper display updated might be a different matter.