On Mon, Jun 03, 2002 at 08:56:22PM +0000, Mikhael Goikhman wrote: > One more idea, storing a final configuration after some script or module > sent dynamical changes to FvwmButtons. Something like: > > SendToModule FvwmButtons-Alias SaveConfig > > The config file name may default to $FVWM_USERDIR/FvwmButtons-Alias . > I.e. to invoke the initial configuration: > > Read FvwmButtons-Alias > FvwmButtons FvwmButtons-Alias > > The first line may be even redudant, i.e. the second one may do it > automatically just like FvwmForm does.
As much as I'd like the idea of saving a configuration, I'm against this way to implement it. As you said in your other mail, there is a need for a scripting language. The configuration commands could be dumped into a file then. With the current implementation of FvwmButtons, it would have to know it's own syntax and print some configuration lines that would reproduce the current layout. That output will most likely look totally different from the original configuration. And even worse, we'd have to remember updating that "save yourself" feature with each new option. There is at least one module that had this functionality (I can't even remember which), but it hasn't been updated for years. No, we need an approach that keeps the additional maintenance cost low. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
