lucky13
Group: Members
Posts: 1478
Joined: Feb. 2007 |
 |
Posted: June 12 2008,15:48 |
 |
The only other variable left in .jwmrc is the root menu height, which can't be factored out unless you factor out the whole root menu. Dittos for the tray height, which is already now part of the .jwmrc-tray file. For some reason, Joe W left those variables within those functions instead of separating them like the window height and color, etc. Not sure if they can be factored out as-is or if it would require source tweaks. I'll try to look at it later and see if it can be done (or if it's feasible).
I have a couple more points. First, I've written that my .jwmrc is already basically a list of include tags -- including my menus as well as the things DSL has already factored out. I think it's practical to move as much of it out of the config file as possible so it can be edited or even left out as desired (such as if a user wants to run a < 1-2kb menu/config instead of 14kb to trim resource use as much as possible). My MyDSL menu is no longer in the root menu but in another. I also moved out my "groups" variables into their own file as well.
Second, I agree with jaapz that there are enough files that it's at least worth considering a special .jwm directory for the files included in .jwmrc. I've already done that on my computers.
If that's done in the base, .jwmrc should stay in ~/ and move the include files to (for example) ~/.jwm. Then those files wouldn't need to be hidden within it and could be like the standard ~/.fluxbox files: keys, menu, tray, theme, settings (for window group configuration), etc. I don't know if that would conflict too much with the existing theme switcher.
(heavily edited)
--------------
"It felt kind of like having a pitbull terrier on my rear end."
-- meo (copyright(c)2008, all rights reserved)
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
