[Opensim-users] Preview split up of OpenSim.ini.example now in bin/config.preview.donotuseyet

[Ovi Chris Rouly]

I agree with Paul, et al.

Chris


----- Original Message ----- 
From: "Paul Fishwick" <fishwick at cise.ufl.edu>
To: <opensim-users at lists.berlios.de>
Sent: Thursday, March 12, 2009 7:40 AM
Subject: Re: [Opensim-users] Preview split up of OpenSim.ini.example now in 
bin/config.preview.donotuseyet


>I have to agree - what is the point of making it harder to locate variables
> and settings that must be modified? From a user's perspective, the ideal
> situation is a front-end GUI "wizard" that sets everything. Short of this,
> having everything in one easy-to-remember location is the next best
> option
> p
>
>
> Tom Willans wrote:
>> Hi Justin,
>>
>> I like the simplicity of having the one .ini file. A single file in a
>> single place easy to edit and easy to check all settings with say the
>> OSGRID version, or where I had a problem. I felt that this was a
>> strength was the simple of this approach. A single place also makes
>> it easy to know where and what file to check.  I have also needed to
>> check the script engine used, avatar settings and language settings
>> even as a fairly new user. It is nice to have a directory into which
>> the examples can be stored though.
>>
>> Tom
>>
>> On 11 Mar 2009, at 21:31, Justin Clark-Casey wrote:
>>
>>
>>> Hello folks,
>>>
>>> I have done a preliminary split of the large OpenSim.ini.example
>>> file into separate files under the directory
>>> config.preview.donotuseyet/.  None of this is yet active.
>>>
>>> The separate .ini.example files are placed in a folder structure
>>> under config/ rather than all in a single directory.
>>> Where possible the structure follows that of modules and assemblies
>>> in the codebase.
>>>
>>> The idea is that all the built in OpenSim defaults will match the
>>> contents of the .ini.example files.  So where settings
>>> are not given, the builtins can be safely used.  This means that
>>> the main bin/OpenSim.ini is reduced to only the
>>> settings that 95% of people use (at the moment, [Startup],
>>> [Network], [StandAlone]).
>>>
>>> If you did want to change one of the more advanced settings in
>>> config/, then you would copy (or rename) that file to
>>> .ini or copy and paste the settings to bin/OpenSim.ini.  For
>>> example, the file
>>>
>>> user/chat/chat.ini.example
>>>
>>> contains only the in world chat configuration parameters.  If you
>>> wanted to change the whisper distance to 100m you
>>> would copy this file to
>>>
>>> user/chat/chat.ini
>>>
>>> and edit the setting.  All .ini files in the config/ directory will
>>> get picked up by OpenSim in addition to bin/OpenSim.ini
>>>
>>> Please tell me what you think.  Expressions of agreement are as
>>> welcome as constructive criticism.  This restructuring
>>> is largely unrelated to other --inimaster, etc. discussions.
>>>
>>> -- 
>>> justincc
>>> Justin Clark-Casey
>>> http://justincc.wordpress.com
>>> _______________________________________________
>>> Opensim-users mailing list
>>> Opensim-users at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-users
>>>
>>
>> _______________________________________________
>> Opensim-users mailing list
>> Opensim-users at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-users
>>
>>
>
>
> -- 
> Paul Fishwick, PhD
> Professor and Director, Digital Arts and Sciences Programs
> University of Florida
> Computer & Information Science and Eng. Dept.
> Bldg. CSE, Room 301
> P.O. Box 116120
> Gainesville, FL 32611
> Email: fishwick at cise.ufl.edu
> Phone: (352) 392-1414
> Fax: (352) 392-1220
> Web: http://www.cise.ufl.edu/~fishwick
>
> _______________________________________________
> Opensim-users mailing list
> Opensim-users at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-users
>