I am for having a second file, that Config.hs imports, which provides each option as a Maybe. so say GuiGeneratedConfig.hs could provide Just 8 for border width, and Config.hs would define border width as borderwidth=(phsedocode as I've forgoten the function) if ggborderwidth is a just, then ggborderwidth, else 7
that way the user could in their Config.hs, put whatever they wanted, and it could be replaced in GuiGeneratedConfig.hs, without modifying the old Config.hs.
I think that hotkeys would be best done by concatinating gghotkeys, with a filter so that if gghotkeys conflicted, it would overwrite the event for that hotkey.
I DO NOT think that the program that makes GuiGeneratedConfig.hs belongs in contrib, I think it should be an entirely separate executable.
Timothy.
On 9/17/07,
Xiao-Yong Jin <xj2106@columbia.edu> wrote:
Sam Walters <sam.walters@gmail.com> writes:
> On Fri, Sep 14, 2007 at 07:35:22PM -0400, Xiao-Yong Jin wrote:
> :| It would be possible to make a GUI-based utility to
> :| configure some simple behaviours through some variables.
> :| However, maintaining a Config.hs file is indispensable to
> :| make xmonad highly configurable.
>
> I think there has been an unspoken assumption that having a configuration
> utility excludes having a user-modifiable Config.hs file. If the
I would like a utility that can modify an existing Config.hs
file. Probably, some special mark-ups in the file could
permit this. Something like the customize-* functions in
Emacs would do.
Of course, it could also be a separated file. We could have
two configuration files. One is automatically generated by
the utility, and the other can be customized by the user.
Some programs also do that.
>
> utility generates a fresh Config.hs instead of modifying
> an existing one, you get the best of both worlds. The
> user would have the choice of using the generated file,
> modifying the generated file or using a file that came
> from another source.
In that case, you could only use that utility once, if you
want to modify it a bit. But I don't think that utility
is meant to be used only once.
>
>
> Sam
>
>
> --
> Do not spoil what you have by desiring what you have not; remember that what
> you now have was once among the things you only hoped for.
> -- Epicurus
> _______________________________________________
> Xmonad mailing list
> Xmonad@haskell.org
> http://www.haskell.org/mailman/listinfo/xmonad
>
>
--
c/* __o/*
<\ * (__
*/\ <
_______________________________________________
Xmonad mailing list
Xmonad@haskell.org
http://www.haskell.org/mailman/listinfo/xmonad
--
-
Tim
tim.thelion@gmail.com