::--(tlau_at_ofb.net)-(18/01/03)--::
> On Friday, Maciej Kalisiak mumbled:
> > Note though that fvwm-themes is not a panacea for new FVWM users...
> > not yet.
> Nor is it a panacea for experienced FVWM users!
> I've configured a lot of FVWM's behavior in the past, but I had yet to
> tackle the problem of making it look pretty beyond selecting different
> colors for the window borders.
> So I was intrigued by fvwm-theme's purported ability to make FVWM look
> like any number of other window managers. However, I don't need to be
> able to swap themes at the click of a button! While that's nice eye
> candy for newbies, and I did spend some time playing with the
> different looks, I just want a single lightweight configuration that I
> understand and can tweak easily. For example: I couldn't tell
> fvwm-themes that I only wanted two desktops! So what I did was to rip
> out the "nanogui" theme and hardcode it into my fvwm2rc, along with
> my existing FVWM customizations.
> However the process of ripping out just that one look-and-feel was not
> at all simple; I had to read through all of the fvwm-themes
> configurations and peel out portions of the nanogui configuration from
> a multitude of different files. There's a lot of knowledge embodied
> within the fwvm-themes package, but it's not very easy to use it
> unless you give up your existing customization and buy into the entire
> dynamically-generated-fvwm-configuration framework.
> What I did when I extracted the nanogui theme was to keep the
> nanogui-specific configuration in separate files. I'm using the
> Debian system.fvwm2rc, which reads in user-supplied hooks at key
> points. So my hooks import the nanogui theme along with my other
> customization.
> This solution is much less intimidating and less heavyweight than
> using fvwm-themes, especially for people who already have a
> configuration they're comfortable with and just want to make it look
> pretty. I would love to see other themes broken out into similar
> config-files that can be added to an existing FVWM configuration
> simply by adding a Read command.
> --Tessa
after using fvwm for a few years, I thought I had a pretty good setup
with all the minor tweaks and features I'd added here and there...
Then I tried out fvwm-themes and *really* found out just how much can be
done with this superior WM.
I too wanted to customise the theme that I eventually constructed within
the fvwm-themes framework and went about gathering all the includes
into one spot so I could be sure I knew what I was dealing with when it
came time to change anything. But still the process was suboptimal in terms
of knowing just where to go to change some detail or other...
Thankfully, it's not that much trouble to consolidate your setup from fvwm-themes...
-From the FAQ:
"You can always get the fvwm configuration in one file (a-la .fvwm2rc)
of the currently used configuration (so called "current" theme) by
executing:
% fvwm-themes-config --expand-rc >current-fvwmrc
You can skip the contents at the start responsible to manipulation of themes."
Worked for me.
After that, of course, one has to go about making the generated file comprehendable,
which for me involved splitting that large file into a bunch of Read'able ones,
but at least I knew that I had a standalone file to work with, and could forget
about changing something that would affect other configurations in other
files...
but here I've just quoted from the FAQ - and I must apologise for stating the
obvious by doing such.
chars,
^d
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Jan 17 2003 - 17:11:37 GMT