Re: A standard package for config files is needed

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

Works for me. Its the sorts of things that one would find in the Windows
Registry - information about the installation of the program on a particular
machine, directory paths & files that are normally involved in execution -
or defaults or most recently used (think of how some apps remember that you
were in a particular directory or working with a particular file as the last
thing you were doing.) Or, as you observe, various user default parameters -
colors, fonts, signatures, etc.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com


<tmoran@acm.org> wrote in message
news:TYRJ8.14898$i47.203973743@newssvr14.news.prodigy.com...
>
>   I'm starting to wonder if everyone is thinking of the same thing when
> they use the term "configuration data".  Or are we all on different
> wavelengths here.  I myself am thinking of persistent information that
> is specific to a particular user and installation, but not a particular
> execution (eg, not an individual document in the case of a word
> processing program).  I also include information that is needed for
> installation and un-installation on a machine, independent of the
> particular user.  That's a pretty broad definition, including file
> lists and file paths and such text as, for instance, standard
> signatures.  My definition also includes settings of flags and
> semi-constants, including structured constants like color palettes or
> fonts.  Those are typically not textual and understanding them requires
> at least some understanding of the inner workings of the program.  Does
> that jibe with what the term is meaning to other folks?