[Opensim-dev] Estates Estates everywhere and nowhere to save

[Adam Frisby]

These should be moved to the region.xml file.

I'd actually like to change that file to an INI, as I think it's easier 
to hand-edit and customise, plus we can reuse nini again. Ming -- could 
you add that to your TODO?

Regards,

Adam

Teravus Ovares wrote:
> Hey all
>  
> Going through and looking at the estate/region stuff we've currently got 
> in place..  there's a fundimental difference from the client 
> orgainization of 'estate and region'.  Because of that there's also a 
> severe lack of functionality.
>  
> Currently, we've got one EstateSettings.xml file with 'set' values for 
> all regions in our instance.
> In addition, a few options are configurable per region in their 
> respective region.xml files.
>  
> Estates are logical organizational units that have a one to many 
> relationship with regions.
> There are many regions to one estate and every region is in an estate.
>  
> Organizing it this way allows for a simple way to make configuration 
> changes on all of the simulators you run (including regions on separate 
> OpenSimulator Instances)
>  
> It also allows you to section off certain portions of your 
> map. (ParentEstate)
>  
> Currently there's some real Old Crusty code surrounding the 
> EstateSettings.xml file.  You *can* save to EstateSettings.xml, but it's 
> really ugly..    and you currently 'can't' save to your RegionInfo.xml 
> files(so nothing persists).
>  
> It's been proposed to put this information in a database and/or have it 
> be asked when the sim loads for the first time.
>  
> As far as Region vs Estate responsibility/relationship, what's the 
> community concensus?
>  
> If you change an estate setting, should it override a region level 
> setting?  (LLGrid does, do we want to?)
>  
> Bear in mind that we've got cross over occasionally on the values.
>  
> Some of the Nouns involved are;
> BillableFactor
> EstateID
> MaxAgents
> ObjectBonusFactor
> ParentEstateID
> PricePerMeter
> RedirectGridX
> RedirectGridY
> RegionFlags
> SimAccess
> SunHour
> TerrainLowerLimit
> TerrainRaiseLimit
> UseEstateSun
> WaterHeight
> SimName
> TerrainTextures (base1,base2,base3,base4)
> Maturity
> Maximum agents
> Covenants
> Estate managers
> Estate Owners
> UsedFixedSun
> when to use the various terrain base textures
> Estate level Banlists
> Estate level allow lists
> EstateID
> ParentEstateID
> BlockFly
> AllowDamage
> Restrict Pushing
> AllowLandResell
> AllowParcelJoin/Divide
> Telehub settings
> Disable scripts/Collisions/Physics
> Sandbox Region
>  
> Public Access
> AllowDirect Teleport
>  
> Eventually, Allowed Groups
> (<Add more nouns here>)
>  
> If we're using the LL grid as an example, then the following examples exist;
> http://wiki.secondlife.com/wiki/Estate_Visibility_Functional_Spec
> http://wiki.secondlife.com/wiki/Estate_Land_Sales_Functional_Spec
> http://wiki.secondlife.com/wiki/Estate_Manager
> https://wiki.secondlife.com/wiki/Estate_Menu
>  
> I look forward to your response.
>  
> Best Regards
> 
> Tera
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev