[Opensim-dev] adding unneeded complexity to OpenSim.ini

[Ovi Chris Rouly]

Dear All,

I'm deeply with Melanie and Paul Fishwick on this.
Section delimiters in a single ASCII text configs have
served computer science very well for many years.

Why fix it if it "ain't" broke?  OpenSim works pretty
well (plus a small learning curve) right out of the box.

Respectfully,

Chris


>
> Message: 1
> Date: Sat, 14 Mar 2009 09:35:48 +0000
> From: Melanie <melanie at t-data.com>
> Subject: Re: [Opensim-dev] Round 2: Config changes preview
> To: opensim-dev at lists.berlios.de
> Message-ID: <49BB7A74.6070901 at t-data.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Has anyone notices how impossibly complicated, complex and
> unmaintainable this is going to become?
> Instead of demanding the user read a simple set of instructions,
> then do the RightThing, you try to do all their thinking for them,
> resulting in something that will make neither novice nor grid
> operator happy.
>
> You are increasing, not decreasing, complexity and the effort to get
> up and running.
> Rename, copy, multiple subdirectories, even I am hard put to see any
> sense in that, and I'm a dev, for crying out loud!
>
> Melanie
>
> Mike Mazur wrote:
>> Hi,
>>
>> On Sat, Mar 14, 2009 at 2:34 AM, Justin Clark-Casey
>> <jjustincc at googlemail.com> wrote:
>>> In this version I've done away with all the subdirectories.  There is 
>>> now a simpler structure
>>>
>>> config/OpenSim.ini.example
>>> config/defaults
>>> config/override
>>
>> On first glance, it's not obvious how the config files in these
>> directories are treated. Is the defaults/ directory scanned for valid
>> .ini files which are then processed?
>>
>> The defaults/ directory contains scripting.ini.defaults. To enable
>> these settings, what should the user do? Rename to
>> defaults/scripting.ini, then edit? Is it necessary to copy to
>> override/scripting.ini and edit instead?
>>
>> In my opinion, having both a directory a *.ini.defaults extensions is
>> one too many. Perhaps we can get away with the two directories
>> containing only .ini files?
>>
>> config/OpenSim.ini.example
>> config/available/*.ini
>> config/override/*.ini
>>
>> Or we could have just one directory which contains *.ini.defaults (or
>> *.ini.example) files alongside *.ini files:
>>
>> config/OpenSim.ini.example
>> config/*.ini{,.defaults}
>>
>> To enable settings, just rename <whatever>.ini.defaults to 
>> <whatever>.ini.
>>
>> Mike
>> _______________________________________________
>> 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
>
>
> End of Opensim-dev Digest, Vol 19, Issue 37
> *******************************************
>