Jenna Felton
Sometimes (and sometimes often) you want the user to create a structure of folders and sub folders when opening a product box. This feature request describes how it can be realized.
First when opening a box there will be additional option "open all" in the context menu which triggers this feature. Second to create a proper folder structure, the creator must prepare the product box for this, by following the rules how the servers will unpack the product box:
  1. The product box is a link set where each prim holds the content that will be in a certain folder.
  2. The content of the root prim is unpacked into a new folder with the same name. The description of the root prim is ignored. This new folder is the root folder of the unpacked structure.
  3. If a child prim has no content or no name or no description (or the standard "no description" as description) it is ignored in the process.
  4. When a child prim has content, a new sub-folder with the same name is created and receives the content of the child prim. The name of the sub-folder is the name of the child prim. The description of the child prim names the parent folder of the created sub-folder.
  • When there is no folder with this name, the sub-folder is created inside the root folder.
  • When there are more then one folder with this name, any of them is used.
  • Alternatively when multiple child prims have the same name and the same description, their content can be merged into one sub-folder.
For example we want unpack into such a folder structure:
📁 Teleporter System
📁 applications
📁 walcable
📁 sitable
📁 touchable
📁 examples
📁 misc
To do so we create a set of 7 prims (each with content):
  • The root prim will have the name "Teleporter System" and any description.
  • The child prims "applications", "examples", "misc" will have "root" or "~" as description (any name not listed here) to place the folders inside the root.
  • The child prims "walcable", "sitable" and "touchable" will have "applications" as description to place their folders inside this folder.
Done. Now the server will be able to unpack the whole folder structure. Additionally it will be also great to have a way for scripts to unpack into a folder structure.
For this there could be a new command
llUnpackLinkset(key target, string name, integer options)
which will (if the recipient accepted) give the folder structure as if they opened the product box in the way above. Target is the recipient to receive the content, name is used to give the root folder a different name. Options would control if no-copy items should be included in the given content and if the script itself should be excluded.
The function would, like
llGiveInventoryList
give the content only if the target is present. But unlike this function also be able to give no-copy items in folders.
Edit: Also it can be useful sometimes to create empty folders in the process. To achieve this, we can use unsaved notecards (which having the null asset key) as the only folder content, the notecards will be not given but folders created.