Talk:Inventory
From OpenSimulator
m (Add para break as in original Ubit notes) |
m (typo) |
||
Line 3: | Line 3: | ||
Inventory was supposed to be somewhat flexible, closer to what we see in most filesystems. Sadly viewers drift into game like inventories, expecting more rigid structure and rigid use rather that just optional "preferred" structure. While some of thiese changes are acceptable, others are not, since they will break on older opensimulator versions and worse will break with inventory backup files | Inventory was supposed to be somewhat flexible, closer to what we see in most filesystems. Sadly viewers drift into game like inventories, expecting more rigid structure and rigid use rather that just optional "preferred" structure. While some of thiese changes are acceptable, others are not, since they will break on older opensimulator versions and worse will break with inventory backup files | ||
− | Recent viewers are | + | Recent viewers are incorporating code to try enforce such game like restrictions. Viewers for opensimulator must stay compatible and fully functional with inventories that do, for example, have folders with same name and or type, anywhere on the inventory tree. Viewers should validate the integrity of the folders tree, namely parent/child relations, and verify lost Llnks. |
Revision as of 12:56, 14 May 2022
Ubit notes, 14-May-2022
Inventory was supposed to be somewhat flexible, closer to what we see in most filesystems. Sadly viewers drift into game like inventories, expecting more rigid structure and rigid use rather that just optional "preferred" structure. While some of thiese changes are acceptable, others are not, since they will break on older opensimulator versions and worse will break with inventory backup files
Recent viewers are incorporating code to try enforce such game like restrictions. Viewers for opensimulator must stay compatible and fully functional with inventories that do, for example, have folders with same name and or type, anywhere on the inventory tree. Viewers should validate the integrity of the folders tree, namely parent/child relations, and verify lost Llnks.