[Opensim-dev] Withdrawing preview config changes for now

[Chris Hart]

Perhaps start with baby steps - how about just a simple move to change
opensim.ini.example and opensim.ini default locations out of the bin and
put it in a config folder - I for one am tired of looking for config
files in among all the rest. Can we do the same with the *.config files
for the other servers too? 

While I'm here, one more idea - default save locations for a save-oar,
or save-xml to a specific folder? Again, why clutter up the bin?

-----Original Message-----
From: opensim-dev-bounces at lists.berlios.de
[mailto:opensim-dev-bounces at lists.berlios.de] On Behalf Of Tommi
Laukkanen
Sent: 18 March 2009 18:49
To: opensim-dev at lists.berlios.de
Subject: Re: [Opensim-dev] Withdrawing preview config changes for now

I apologise that I linked the latter chapter to this specific thread.
I should have posted it as a separate message as it was a more general
comment on our decission making process.

I guess it sprung from my wonderment about how the decission turned
out to be not to fix the overtly long config file in the way justincc
suggested. I think that the decission did not take into account people
like administrators and developers who use the system. Yes the
framework code can be more complex but it can produce benefits for
administrators and developers who need to deal with the long ini file.
I would even say that almost anything which splits the file is an
improvement to the current system.

Putting down an effort which tries to fix a problem at least can be
said to be counter productive.  I should reformulate my message: We
should in general suggest alternatives rather than just say "ouch I
dont like this". Our vote has consequences and if we use it we should
spend a little time to look into the issue and help the team to find a
better solution.

-tommi
_______________________________________________
Opensim-dev mailing list
Opensim-dev at lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev

No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.238 / Virus Database: 270.11.15/2003 - Release Date:
03/18/09 07:17:00