[Opensim-dev] Ini file(s) loading

[Dahlia Trimble]

Is there any reason why we wouldn't want to update the defaults in the code
to sane values?

On Fri, Mar 6, 2009 at 1:57 AM, Melanie <melanie at t-data.com> wrote:

> We did that because the hardcoded defaults won't work anymore. They
> are different fromt he OpenSim.ini.example values.
> However, my proposal provides a sane mechanism to provide external
> defaults, while not requiring user action at all.
>
> Melanie
>
> Frisby, Adam wrote:
> > I did wonder why we started forcing users to have an opensim.ini. The
> previous 'use defaults' made more sense to me.
> >
> > Adam
> >
> >> -----Original Message-----
> >> From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-
> >> bounces at lists.berlios.de] On Behalf Of Jeff Ames
> >> Sent: Thursday, 5 March 2009 7:20 PM
> >> To: opensim-dev at lists.berlios.de
> >> Subject: Re: [Opensim-dev] Ini file(s) loading
> >>
> >> Melanie wrote:
> >> > read [the config directory] first
> >> > then read the inimaster
> >> > then read the inifile
> >>
> >> If I understand this correctly, the config/*.ini files would be
> >> essentially read-only, and all local changes would be made to the
> >> inimaster or OpenSim.ini.  But then OpenSim.ini is not broken up, and
> >> it may be confusing to users why there are two sets of config files.
> >>
> >> Is this just due to OpenSim's current behavior of requiring an .ini
> >> file to be present?  Currently the default values for all settings
> >> exist in the code itself and in the .ini.example file (itself an
> >> unfortunate duplication, but that's another topic).  Instead of
> >> requiring that an .ini be present, we could simply use the default
> >> values in the code if there is no .ini.  This would also have the
> >> pleasant side effect of matching the behavior when an empty .ini file
> >> is present.
> >>
> >> Then we could break up and move OpenSim.ini.example entirely to
> >> config/*.ini.example files, and when the user wants to change a value,
> >> create foo.ini based on foo.ini.example (copying the whole file if
> >> they want everything, or only adding the options they want to
> >> explicitly set).
> >>
> >> Then I guees the load order would be:
> >>  - read inimaster (if present)
> >>  - read config/*.ini (if present)
> >>  - use defaults in code for anything not set
> >>
> >> I think this would also avoid the merging problem, if users only add
> >> options they're explicitly setting to the *.ini files.  It would also
> >> remove the annoyance of having to copy the .ini.example file over
> >> every time on a new install.
> >>
> >> Jeff
> >> _______________________________________________
> >> Opensim-dev mailing list
> >> Opensim-dev at lists.berlios.de
> >> https://lists.berlios.de/mailman/listinfo/opensim-dev
> > _______________________________________________
> > Opensim-dev mailing list
> > Opensim-dev at lists.berlios.de
> > https://lists.berlios.de/mailman/listinfo/opensim-dev
> >
> >
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20090310/c8c46526/attachment-0001.html>