Ghost Config Distribution

[GoogleCodeExporter]

In distribution of new ghost versions, please rename ghost.cfg to
ghost.cfg.dist

Reason:
I figure when people overwrite old files, the config doesn't get
overwritten. Also when ghost launches and only sees ghost.cfg.dist, it
would automatically rename it, or make a copy of it as ghost.cfg for people
with a new installation.

Original issue reported on code.google.com by Absolute...@gmail.com on 5 Sep 2009 at 3:18

[GoogleCodeExporter]

I like this idea.

Original comment by hogantp on 5 Sep 2009 at 4:56

• Changed state: Accepted

[GoogleCodeExporter]

I've thought about this some more and I'm not sure I like it so much because it 
would
require users to run GHost++ at least once in order to copy ghost.cfg.dist to
ghost.cfg before editing it. It would be possible to print a message to this 
effect
and exit when it copies it but I'm reducing this to low priority while I think 
about
how I want to handle it, if at all.

Original comment by hogantp on 14 Sep 2009 at 6:37

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

For some time now I've been feeling that the configuration files should be 
stored 
within subfolders.
1 for language files
1 for configuration files (ghost.cfg, motd.txt, gameloaded.txt, gameover.txt)
1 for documentation

If this system were adopted, then you could have a folder called 'original' 
within 
the 'configuration' folder.  By default, always store ghost.cfg in the 
'original' 
folder, and ghost could perform accordingly:
1) if ghost.cfg exists in both the originals & configuration folders, do a 
comparitive search and add additional values that exist in the 'original' 
ghost.cfg 
that do not exist in the 'configuration' ghost.cfg.  This gets annoying and I 
don't 
recommend it, because eventually ghost.cfg gets very messy due to the general 
sloppiness of such a procedure.

2) if ghost.cfg exists in just the configuration folder, then no changes would 
be 
made.

3) if ghost.cfg exists only in the 'original' folder, then it would be copied 
to 
the 'configuration' folder, and will stop loading because it "loaded default 
values 
and needs to be configured." 

All and all, not really a practical concept without an automatic GHost++ 
updater and 
a preprogrammed GUI for adding additional values.  Values should be updated in 
the 
GUI and entered into a textfile, not really the other way around.

Original comment by LukeWith...@gmail.com on 1 Dec 2009 at 10:30

[GoogleCodeExporter]

I present a possibly better solution here:
http://www.codelain.com/forum/index.php?topic=9812.0

Original comment by LukeWith...@gmail.com on 3 Dec 2009 at 10:30

[GoogleCodeExporter]

good idea

Original comment by darkpo...@gmail.com on 9 Oct 2010 at 10:59