<div>With all due respect,</div>
<div> </div>
<div>I would have to agree with Melanie, Paul Fishwick, Charles, Chris and all the others that seem very concerned about this foolishly insane concept.</div>
<div> </div>
<div>Why make things much more complex than they really need to be?</div>
<div> </div>
<div>Melanie stated:</div>
<div> </div>
<div>
<div><strong><em>> 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.</em></strong></div></div>
<div> </div>
<div>I completely agree with her statement as well. The point of doing things (as a developer) is to make things EASIER (not harder) for the users, Grid Operators, Administrators, and this seems to go in the exact opposite direction of where the users/grid operators would want to go.</div>
<div> </div>
<div>Please let's NOT make things any harder or any more complicated than they really need to be. (Remember the phrase "Keep it simple stupid"). As Chris has mentioned, simple ASCII text files (ini files) have worked for decades. We don't need to get rid of any directory structures (directories are what keeps things neat, organized, and orderly. Folders are a good thing). One simple ASCII text configuration file is the simplest solution, and it works for MySQL, Apache, and all the others, so why change something that isn't broken?</div>
<div> </div>
<div>Just to make things more complicated? Make things more difficult and complex? Create havok? Just to break things? It really makes no sense.</div>
<div> </div>
<div>Chris said things pretty well in his comment:</div>
<div> </div>
<div><strong><em>> 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.</em></strong></div>
<div><strong><em>> Why fix it if it "ain't" broke? OpenSim works pretty<br>>well (plus a small learning curve) right out of the box.</em></strong></div>
<div><strong><em></em></strong> </div>
<div>I certainly would have to agree. Stick with what works. If you want to make our lives simpler, work on some nice powerful GUI's or something that will make our lives easier as grid operators/administrators, and make a nice GUI that will modify the ini files for us. But leave the ini's and folder structure the way they are. No reason to break things that aren't broken. Some people (such as myself) prefer a nice simple text file (in one spot) that we can edit and modify. </div>
<div> </div>
<div>It keeps the tutorials simple, and gets users up and running extremely quickly, and the "learning curve" is reduced (with a simple and single ASCI text ini file). The folder and directory structure makes sense, so please just leave it be.</div>
<div> </div>
<div> Thanks,</div>
<div> </div>
<div> Mark</div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Sat, Mar 14, 2009 at 10:12 AM, Charles Krinke <span dir="ltr"><<a href="mailto:cfk@pacbell.net">cfk@pacbell.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: arial,helvetica,sans-serif">
<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 : <a href="http://opensimulator.org/wiki/" target="_blank">http://opensimulator.org/wiki/</a><newOpenSimIniConfigDirectoryChanges><br>
</div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: arial,helvetica,sans-serif"><br>
<div style="FONT-SIZE: 13px; FONT-FAMILY: arial,helvetica,sans-serif"><font face="Tahoma" size="2">
<hr size="1">
<b><span style="FONT-WEIGHT: bold">From:</span></b> Ovi Chris Rouly <<a href="mailto:maelzel@ieee.org" target="_blank">maelzel@ieee.org</a>>
<div class="im"><br><b><span style="FONT-WEIGHT: bold">To:</span></b> <a href="mailto:opensim-dev@lists.berlios.de" target="_blank">opensim-dev@lists.berlios.de</a><br></div><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>
<div>
<div></div>
<div class="h5"><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 href="mailto:melanie@t-data.com" target="_blank">melanie@t-data.com</a>><br>
> Subject: Re: [Opensim-dev] Round 2: Config changes preview<br>> To: <a href="mailto:opensim-dev@lists.berlios.de" target="_blank">opensim-dev@lists.berlios.de</a><br>> Message-ID: <<a href="mailto:49BB7A74.6070901@t-data.com" target="_blank">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 href="mailto:jjustincc@googlemail.com" target="_blank">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 href="mailto:Opensim-dev@lists.berlios.de" target="_blank">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 href="mailto:Opensim-dev@lists.berlios.de" target="_blank">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 href="mailto:Opensim-dev@lists.berlios.de" target="_blank">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></div></div></div><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></blockquote></div><br>