Re: XWin design suggestion

["Early Ehlinger" <early at respower dot com>]

"Harold L Hunt II" <huntharo@msu.edu> wrote:
> I don't think it would break any hearts if we put one more file with
> preferences (not stuff needed to run) in another directory.


How about yaclo (yet-another-command-line-option)... XWin.exe -configfile
<windows-filename> -sysconfigfile <windows-filename>

The user can then put system-wide config stuff in the sysconfigfile, and
user-specific stuff in the configfile.

These could then be in the "Documents and Settings" path or in the cygwin
/etc path, at the user's discretion.  The default should probably be the
"Documents and Settings" path as XWin is a windows program.  IMHO the only
registry setting should be "where are the config files."  The big problem I
have with the registry is the deployment problem.  When I get a new
workstation/laptop/whatever (this is actually a pretty common occurrence for
me), I've already got a zillion apps that need to be installed because they
munge the registry.  I'd rather they all use configuration files.  Then I
could simply copy their respective directories, my home directory, and be
done with it.

BTW, if you can port it to not be dependent on Cygwin, I really look forward
to that.  I'm not a big Cygwin fan (I prefer Mingw32) and actually have it
installed *solely* to run XWin so I can ssh over to my linux boxen!

Ideally, IMHO, XWin should run as an NT service (!!) so that I don't have to
ever remember to launch it.  It would always be on and waiting for me to
launch xterm / ssh / etc., and would have a control panel applet to
configure it.  Sure, I can put it into my startup folder, but that's not
really a service - it's just a program that gets launched with explorer.

Anyway, there's my 2 cents on the topic.



--
-- Early Ehlinger CEO, ResPower Inc - Toll-Free : 866-737-7697
-- www.respower.com -- 500+ GHz Supercomputer Starting At USD$0.50/GHz*Hour