<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Personally, I have no problem with xml config files; the only thing is, I usually want to be able to<BR>
<BR>
a) partition the config file (but having a 'real' "[Network]" grouping thingy in an ini works just as well<BR>
b) specify several instances<BR>
c) nest levels, when needed (related to b)<BR>
<BR>
But hell, as always, we should go for the simplest, readliest, solution that does what we want it to.<BR>
<BR>
And no, I've long forgotten the Nini case that bothered me, so I'm justa goinga shutta uppa'bout it. (until I remember)<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Thu, 26 Jun 2008 08:39:02 -0400<BR>> From: adam@deepthink.com.au<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Module/Plugin Loading<BR>> <BR>> I +1 this. XML config files drive me crazy with frequency.<BR>> <BR>> > -----Original Message-----<BR>> > From: opensim-dev-bounces@lists.berlios.de [mailto:opensim-dev-<BR>> > bounces@lists.berlios.de] On Behalf Of Dr Scofield<BR>> > Sent: Thursday, 26 June 2008 5:27 AM<BR>> > To: opensim-dev@lists.berlios.de<BR>> > Subject: Re: [Opensim-dev] Module/Plugin Loading<BR>> > <BR>> > Sean Dague wrote:<BR>> > > On Thu, Jun 26, 2008 at 09:49:11AM +0200, Stefan Andersson wrote:<BR>> > ><BR>> > >>> Those attributes are just syntactic sugar. Once you start really<BR>> > using> the features of Mono.Addins you're best of configuring your<BR>> > addins> with the XML file.<BR>> > >>><BR>> > >> That's probably the way to go, yeah.<BR>> > >> > Its also worth nothing that there is nothing in Mono.Addin's<BR>> XML><BR>> > config file that replaces anything in OpenSim.ini, nor vice versa.><BR>> > They are completely orthogonal configuration files which are><BR>> > unrelated. There is no OpenSim v. Mono.Addins dilemma.<BR>> > >> I think that what some of us are worried about is the configuration<BR>> > creep; there's slowly getting more and more ways of configuring<BR>> various<BR>> > aspects of OpenSim, and each configuration is something more to grok<BR>> in<BR>> > order to use.<BR>> > >><BR>> > >> afaik, we have Prebuild, log4net, NHibernate, Nini, the database<BR>> > >> configuration files, the opensim.ini, various grid inis, some<BR>> > settings<BR>> > >> are stored in a yap database, the region configs - and now Mono<BR>> > >> Addins. Each following different syntax and structure.<BR>> > >><BR>> > ><BR>> > > Fortunately this list actually has been pruned down (at least I've<BR>> > been<BR>> > > trying :))<BR>> > > * .yap have been pulled (db4o is no longer in the tree)<BR>> > > * database configs are now deprecated, you can fully specify them<BR>> > all<BR>> > > as connection strings in either opensim.ini or grid configs<BR>> (there<BR>> > > are even user messages telling people that if they are using the<BR>> > old<BR>> > > model).<BR>> > > * NHibernate doesn't need any of it's own user changable config<BR>> > outside<BR>> > > of opensim.ini. The nhibernate config is just annotations to<BR>> make<BR>> > > some log messages go away.<BR>> > ><BR>> > > So that does get us down to:<BR>> > > * estate settings<BR>> > > * grid configs<BR>> > > * Nini based stuff (opensim.ini, stock content libraries)<BR>> > > * .configs on .exe files for log4net<BR>> > > * region configs<BR>> > ><BR>> > > But that's still *a lot*, especially as each of those are different.<BR>> > > One of the reasons no one has touched estate settings is that it's<BR>> > the<BR>> > > deepest darkest part of config. Our first config mechanism. There<BR>> > be<BR>> > > dragons there, and not the anthropomorphic friendly type. :)<BR>> > ><BR>> > ><BR>> > >> So, we're starting to get something like what we're trying to solve<BR>> > >> with unifying the plugin architecture.<BR>> > >><BR>> > ><BR>> > > +1. 100% agreed.<BR>> > ><BR>> > ><BR>> > >> At some point, we need to look at unifying our configs. Introducing<BR>> > >> Nini was a stab at that, but seems to have lost momentum.<BR>> > Personally,<BR>> > >> I have somewhat lost faith in Nini, as it doesn't really seem to<BR>> > >> handle hierarchical data on several instances too well.<BR>> > >><BR>> > ><BR>> > > Is there a good example on that? The Nini XML used for assets<BR>> > doesn't<BR>> > > seem too bad. I do agree that on the ini side we've got some work<BR>> > > there.<BR>> > ><BR>> > > Having looked, and thrown up my hands on modding estate settings,<BR>> I'd<BR>> > > suggest Nini replacements for the rest of the non nini, custom<BR>> > loaders,<BR>> > > would help *a lot* in cleaning up the source base, and making it<BR>> make<BR>> > > more sense.<BR>> > ><BR>> > > We may also want to switch OpenSim.ini to an xml file if we want<BR>> more<BR>> > > nesting. Big OpenSim.ini files definitely seem overwhelming at this<BR>> > > point, though not too unweildly.<BR>> > ><BR>> > ><BR>> > hmm...personally, i hate XML config files. the OpenSim.ini style is<BR>> > much<BR>> > easier to use and less cluttered.<BR>> > <BR>> > dirk<BR>> > <BR>> > --<BR>> > dr dirk husemann ---- virtual worlds research ---- ibm zurich research<BR>> > lab<BR>> > SL: dr scofield ---- drscofield@xyzzyxyzzy.net ----<BR>> > http://xyzzyxyzzy.net/<BR>> > RL: hud@zurich.ibm.com - +41 44 724 8573 -<BR>> > http://www.zurich.ibm.com/~hud/<BR>> > <BR>> > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>