<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6001.18203" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN lang=EN>
<P>Sane values are desperately needed. I deal with many new users every
week, in game and on forums. Most are x-pat SL content creators that are on top
of that side but get hyper confused with an OpenSim binary. Many will tough it
out and get an instance started but too many give up in frustration. </P>
<P>Lately my improved technique is to have them fetch the OpenSim.ini from
OSGrid dl, that at least gets past the first hurdles sanely. Or if
standalone, use that .ini with very minimal edit.</P>
<P>I suggest anyone here open ini.example and look at it from a new user semi
technical viewpoint.</P></SPAN></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=dahliatrimble@gmail.com href="mailto:dahliatrimble@gmail.com">Dahlia
Trimble</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=opensim-dev@lists.berlios.de
href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 10, 2009 11:21
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Opensim-dev] Ini file(s)
loading</DIV>
<DIV><BR></DIV>Is there any reason why we wouldn't want to update the defaults
in the code to sane values?<BR><BR>
<DIV class=gmail_quote>On Fri, Mar 6, 2009 at 1:57 AM, Melanie <SPAN
dir=ltr><<A
href="mailto:melanie@t-data.com">melanie@t-data.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">We
did that because the hardcoded defaults won't work anymore. They<BR>are
different fromt he OpenSim.ini.example values.<BR>However, my proposal
provides a sane mechanism to provide external<BR>defaults, while not
requiring user action at all.<BR><FONT color=#888888><BR>Melanie<BR></FONT>
<DIV>
<DIV></DIV>
<DIV class=h5><BR>Frisby, Adam wrote:<BR>> I did wonder why we started
forcing users to have an opensim.ini. The previous 'use defaults' made more
sense to me.<BR>><BR>> Adam<BR>><BR>>> -----Original
Message-----<BR>>> From: <A
href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</A>
[mailto:<A href="mailto:opensim-dev-">opensim-dev-</A><BR>>> <A
href="mailto:bounces@lists.berlios.de">bounces@lists.berlios.de</A>] On
Behalf Of Jeff Ames<BR>>> Sent: Thursday, 5 March 2009 7:20
PM<BR>>> To: <A
href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</A><BR>>>
Subject: Re: [Opensim-dev] Ini file(s) loading<BR>>><BR>>>
Melanie wrote:<BR>>> > read [the config directory]
first<BR>>> > then read the inimaster<BR>>> > then read
the inifile<BR>>><BR>>> If I understand this correctly, the
config/*.ini files would be<BR>>> essentially read-only, and all local
changes would be made to the<BR>>> inimaster or OpenSim.ini. But
then OpenSim.ini is not broken up, and<BR>>> it may be confusing to
users why there are two sets of config files.<BR>>><BR>>> Is
this just due to OpenSim's current behavior of requiring an .ini<BR>>>
file to be present? Currently the default values for all
settings<BR>>> exist in the code itself and in the .ini.example file
(itself an<BR>>> unfortunate duplication, but that's another topic).
Instead of<BR>>> requiring that an .ini be present, we could
simply use the default<BR>>> values in the code if there is no .ini.
This would also have the<BR>>> pleasant side effect of matching
the behavior when an empty .ini file<BR>>> is
present.<BR>>><BR>>> Then we could break up and move
OpenSim.ini.example entirely to<BR>>> config/*.ini.example files, and
when the user wants to change a value,<BR>>> create foo.ini based on
foo.ini.example (copying the whole file if<BR>>> they want everything,
or only adding the options they want to<BR>>> explicitly
set).<BR>>><BR>>> Then I guees the load order would
be:<BR>>> - read inimaster (if present)<BR>>> - read
config/*.ini (if present)<BR>>> - use defaults in code for
anything not set<BR>>><BR>>> I think this would also avoid the
merging problem, if users only add<BR>>> options they're explicitly
setting to the *.ini files. It would also<BR>>> remove the
annoyance of having to copy the .ini.example file over<BR>>> every
time on a new install.<BR>>><BR>>> Jeff<BR>>>
_______________________________________________<BR>>> Opensim-dev
mailing list<BR>>> <A
href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</A><BR>>>
<A href="https://lists.berlios.de/mailman/listinfo/opensim-dev"
target=_blank>https://lists.berlios.de/mailman/listinfo/opensim-dev</A><BR>>
_______________________________________________<BR>> Opensim-dev mailing
list<BR>> <A
href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</A><BR>>
<A href="https://lists.berlios.de/mailman/listinfo/opensim-dev"
target=_blank>https://lists.berlios.de/mailman/listinfo/opensim-dev</A><BR>><BR>><BR>_______________________________________________<BR>Opensim-dev
mailing list<BR><A
href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</A><BR><A
href="https://lists.berlios.de/mailman/listinfo/opensim-dev"
target=_blank>https://lists.berlios.de/mailman/listinfo/opensim-dev</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>Opensim-dev mailing
list<BR>Opensim-dev@lists.berlios.de<BR>https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></BLOCKQUOTE></BODY></HTML>