MG> A solid, correctly written program doesn't have to 
 MG> be "ugly"; it can be easy and intuitive for the 
 MG> user as well. The sorts of programs that work well 
 MG> while at the same time having an intuitive 
 MG> interface for the user show the true mark of a well 
 MG> written program.
 
I think we're in violent agreement here. I certainly would encourage any
one who wants to write a good GUI or TUI for max/squish configuration to
step forward. Or even "new sysop setup wizards", or something
similar. Making configuration software emit nice, readable configuration
files is really not significantly more difficult than any other kind of
output.
 
In fact, I'll step up to the plate here -- once max/squish are stable under
UNIX, I'd be willing to write scanners/parsers for the Maximus/Squish
configuration files based on the Maximus sources (for optimal
compatibility) and code to write the files back out again. Somebody else
will have to the UI itself, however -- that's not realyl something I'm in
to, and frankly I'm not very good at it, either.
 
FWIW, I'd probably lean toward a Tcl/Tk-based configuration engine --
lightweight, and very portable (At least among unices, Win32, and OS/2 --
not sure about DOS). Another options would be to use dialog; it's a limited
toolset, but it's very easy to use to create TUIs and also has an X-Windows
equivalent (it normally runs under curses).
 
Wes

--- Maximus/2 3.01