aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Framework/DAMap.cs (unfollow)
Commit message (Collapse)AuthorFilesLines
2017-01-05Massive tab and trailing space cleanupMelanie Thielker1-20/+20
2013-07-08minor: remove now unused migration-hack bool from DAMapJustin Clark-Casey (justincc)1-4/+0
2013-06-29Remove hack to migrate previous experimental-level os materials data.Justin Clark-Casey (justincc)1-9/+0
This didn't seem to be working anyway and it's better not to have such hacks in the code for experimental stuff.
2013-06-27add method docs for DAMap.GetStore() and DAMap.SetStore()dahlia1-0/+12
2013-06-27Make the concept of namespaces explicit in dynamic attributesJustin Clark-Casey (justincc)1-122/+178
This is in order to reduce the likelihood of naming clashes, make it easier to filter in/out attributes, ensure uniformity, etc. All dynattrs in the opensim distro itself or likely future ones should be in the "OpenSim" namespace. This does alter the underlying dynattrs data structure. All data in previous structures may not be available, though old structures should not cause errors. This is done without notice since this feature has been explicitly labelled as experimental, subject to change and has not been in a release. However, existing materials data is being preserved by moving it to the "Materials" store in the "OpenSim" namespace.
2013-03-13Add prototype dynamic objects map for scene object partsJustin Clark-Casey (justincc)1-1/+1
This allows region modules to add dynamic objects to SOPs rather than having to continually push and pull OSD dynamic attributes. This is to explore the original MOAP use case for dynamic attributes where it could be very awkward and possibly time-consuming to keep reconstructing MediaEntrys from stored DynamicAttributes. This commit adds a DOExampleModule to demonstrate/evolve this code. Dynamic objects involve no storage or persistence changes - the 'backing store' for any data that does need to be saved will remain the DAMap. DOExampleModule in this commit only attaches a fresh dynamic object. Actually constructing this from stored dynamic attributes and handling persistence is left for later. These changes should affect no existing functionality, though it may or may not reveal necessary changes in DAMap down the road.
2013-02-06Enables script access to the per object dynamic attributes through the JsonStoreMic Bowman1-0/+8
script functions. Adds JsonAttachObjectStore to associate a store identifier with an object (scripts can only access the store in their host object, this could be extended but isn't necessary for now). Note this opens a method to the DAMap OSDMap. This will be removed later, but greatly simplifies the code for now. The JsonStore and these scripts are disabled by default.
2013-02-07minor: add method doc to DAMap.ValidateKey()Justin Clark-Casey (justincc)1-0/+4
2013-02-07Add key length validation to DAMap.Add(KeyValuePair<string, OSDMap> kvp) to ↵Justin Clark-Casey (justincc)1-1/+2
match Add(string key, OSDMap store)
2013-01-25Added DynAttrs to the serialized XML format of prims. When copying prims, ↵Oren Hurvitz1-2/+24
use deep copy for DynAttrs.
2013-01-25Changed DAMap to be the container of "data stores", which are OSDMaps. Store ↵Oren Hurvitz1-20/+84
names must have at least 4 characters.
2013-01-25Lock DAMap rather than encapsulated OSDMapJustin Clark-Casey (justincc)1-17/+18
This allows external lockers to preserve atomicity of dynamic attribute changes
2013-01-25Encapsulate an OSDMap in DAMap (was DynAttrsOSDMap) rather than inheriting ↵Justin Clark-Casey (justincc)1-0/+173
from it This is the easier way to give us control over locking, rather than asking that OSDMap IDictionary methods be virtual