<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div>I have to admit puzzlement on this complexity also.<br><br>But, as I read all this, I would also urge that if a significant change is made that a wiki entry can be made so that the question : "My OpenSim doesnt work anymore and I think it is config?" can be answered : http://opensimulator.org/wiki/<newOpenSimIniConfigDirectoryChanges><br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Ovi Chris Rouly <maelzel@ieee.org><br><b><span style="font-weight: bold;">To:</span></b> opensim-dev@lists.berlios.de<br><b><span style="font-weight: bold;">Sent:</span></b> Saturday, March 14, 2009 6:30:21
AM<br><b><span style="font-weight: bold;">Subject:</span></b> [Opensim-dev] adding unneeded complexity to OpenSim.ini<br></font><br>
Dear All,<br><br>I'm deeply with Melanie and Paul Fishwick on this.<br>Section delimiters in a single ASCII text configs have<br>served computer science very well for many years.<br><br>Why fix it if it "ain't" broke? OpenSim works pretty<br>well (plus a small learning curve) right out of the box.<br><br>Respectfully,<br><br>Chris<br><br><br>><br>> Message: 1<br>> Date: Sat, 14 Mar 2009 09:35:48 +0000<br>> From: Melanie <<a ymailto="mailto:melanie@t-data.com" href="mailto:melanie@t-data.com">melanie@t-data.com</a>><br>> Subject: Re: [Opensim-dev] Round 2: Config changes preview<br>> To: <a ymailto="mailto:opensim-dev@lists.berlios.de" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>> Message-ID: <<a ymailto="mailto:49BB7A74.6070901@t-data.com" href="mailto:49BB7A74.6070901@t-data.com">49BB7A74.6070901@t-data.com</a>><br>> Content-Type: text/plain; charset=ISO-8859-1;
format=flowed<br>><br>> Has anyone notices how impossibly complicated, complex and<br>> unmaintainable this is going to become?<br>> Instead of demanding the user read a simple set of instructions,<br>> then do the RightThing, you try to do all their thinking for them,<br>> resulting in something that will make neither novice nor grid<br>> operator happy.<br>><br>> You are increasing, not decreasing, complexity and the effort to get<br>> up and running.<br>> Rename, copy, multiple subdirectories, even I am hard put to see any<br>> sense in that, and I'm a dev, for crying out loud!<br>><br>> Melanie<br>><br>> Mike Mazur wrote:<br>>> Hi,<br>>><br>>> On Sat, Mar 14, 2009 at 2:34 AM, Justin Clark-Casey<br>>> <<a ymailto="mailto:jjustincc@googlemail.com" href="mailto:jjustincc@googlemail.com">jjustincc@googlemail.com</a>> wrote:<br>>>> In this version I've done away with
all the subdirectories. There is <br>>>> now a simpler structure<br>>>><br>>>> config/OpenSim.ini.example<br>>>> config/defaults<br>>>> config/override<br>>><br>>> On first glance, it's not obvious how the config files in these<br>>> directories are treated. Is the defaults/ directory scanned for valid<br>>> .ini files which are then processed?<br>>><br>>> The defaults/ directory contains scripting.ini.defaults. To enable<br>>> these settings, what should the user do? Rename to<br>>> defaults/scripting.ini, then edit? Is it necessary to copy to<br>>> override/scripting.ini and edit instead?<br>>><br>>> In my opinion, having both a directory a *.ini.defaults extensions is<br>>> one too many. Perhaps we can get away with the two directories<br>>> containing only .ini files?<br>>><br>>>
config/OpenSim.ini.example<br>>> config/available/*.ini<br>>> config/override/*.ini<br>>><br>>> Or we could have just one directory which contains *.ini.defaults (or<br>>> *.ini.example) files alongside *.ini files:<br>>><br>>> config/OpenSim.ini.example<br>>> config/*.ini{,.defaults}<br>>><br>>> To enable settings, just rename <whatever>.ini.defaults to <br>>> <whatever>.ini.<br>>><br>>> Mike<br>>> _______________________________________________<br>>> Opensim-dev mailing list<br>>> <a ymailto="mailto:Opensim-dev@lists.berlios.de" 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>><br>> ------------------------------<br>><br>>
_______________________________________________<br>> Opensim-dev mailing list<br>> <a ymailto="mailto:Opensim-dev@lists.berlios.de" 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>> End of Opensim-dev Digest, Vol 19, Issue 37<br>> *******************************************<br>> <br><br><br>_______________________________________________<br>Opensim-dev mailing list<br><a ymailto="mailto:Opensim-dev@lists.berlios.de" 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></div></body></html>