Feature Requests

  • Search existing ideas before submitting
  • Use support.secondlife.com for customer support issues
  • Keep posts on-topic
Thank you for your ideas!
Discussion: Improving Inventory Organization
Today's SUG (Nov 12) was dominated mainly by a discussion about the upcoming llGiveAgentInventory function, which allows creators to specify a path name relative to the root directory for new items to be received at. This Canny post is meant to provide a place to discuss the subject further. The key takeaway the Lindens need from this is that many users are HIGHLY opinionated about how they organize their inventory, and they'll be dissatisfied with any solution that requires them to depend on creators to know where things belong; otherwise it's like leaving everything you've ever bought in the packaging, with the receipts, etc. Problem 1 : Finding automatically-placed folders Automatically-placed folders will get buried. Is there a way to prevent this from being annoying? - Option 1: Allow a history view of recently-received items. (My suggestion.) Firestorm already has this, but its organization is as a filter over the whole inventory hierarchy. It would be better as a list of the basenames of recently-received folders provided by llGAI(). - Option 2: A mandatory container folder for items received via llGAI(). Move the target for newly-received marketplace items into a subdirectory, e.g. |Received Items|Marketplace, and put llGAI() items in sibling like |Received Items|In-World. This would also be an opportunity to relocate inventory items obtained through other means like buying objects, llGiveInventory(), llGiveInventoryList(), etc. The |Objects system folder has been doing double duty by accumulating these items and stuff the user has picked up manually. I don't like having my creations mixed in with my purchases, and I think a lot of other residents feel the same way. - Option 3: Allow a "Save As" style dialog box for users to choose where to put stuff when receiving items. (Nyx Onyx's suggestion.) The path provided to llGAI() becomes a default recommendation, not a reliable outcome. This also solves Problem 2... Problem 2 : Users disagree with creators over organization structure - Option 1: Iexo Bethune suggested a forwarding mechanism: if a user moves an intermediate folder (e.g. "|Clothing|Fashionista Fashions") to a new location (e.g. "|Clothing|Maitreya Clothes|Fashionista Fashions") then it would be neat if the viewer could remember this as a path rewrite rule, and redirect stuff in the future. This was misunderstood by the Lindens present as a request for folder symlinks, which would probably not be what Iexo wanted (as it would cause more clutter, not less.) Of course, there are challenges with this strategy, at least in the example given—What if Fashionista Fashions makes clothes that aren't for Maitreya? Additionally these rewrite rules would need a whole UI to manage them or they'd silently accumulate... which is not great. - Option 2: Tagging. Several people mentioned this, and it is already discussed somewhat on another Canny issue, here: https://feedback.secondlife.com/feature-requests/p/add-custom-tags-to-inventory-items - doing it properly would mean abandoning or downplaying the current hierarchical inventory organization structure in favor of non-disjoint item sets. This would solve the problems with Option 1, since now the creator name would be just another tag to apply to an item. For a bonus round, tags for marketplace categories could be added, automating some of the more common uses. - Option 3: The "Save As" dialog again, as proposed by Nyx Onyx. This way the user always knows where things went. However it could be annoying if the user has just received a huge collection of new items and must decide where to save each one.
0
InvNix: Inventory Shell/Bash
A simple scripting system within a users inventory for better inventory management. Nb. just for a person's own inventory NOT for anything else. LUA scripting might provide some/all of these functionalities, if so then this could be a checklist for LUA implementation features? Main Aspect: To have inventory "shell scripts". These would be a new inventory type that allowed inventory manipulation. Triggered through specific events to cause various actions to happen. ### Script Variables: Variables available to the script.. * Path - (String) folder location. * Folder Contents - (list/array/object) list of folders contents. * Date/Time - (string/number) either a timestamp or unix timecode.. * etc.... ### Triggers: Potential examples. * Manual triggering - Right click context menu "Run" Command. * Called - Called from other inventory shell scripts. * Timed triggers - whilst online the viewer could have a crontab like system. * Change detection - fired on changes within folder. ### Actions: Potential examples, I am obviously drawing from *nix shell commands here. * mv/cp - Move or copy item. e.g. mv "New Object" "New Object {date}" rename the item "New Object" to "New Object 2024/11/13" * touch - create a new object. e.g. touch -nc "Foldercontents" Make a new notecard called "Foldercontents" * mkdir - create a directory e.g. mkdir "SNH Halloween 24" * rm/rmdir - remove/remove folder.. * ls/tree - List folder contents. * >/>>/| - chaining/piping * cat - Get details of an object e.g. ``` json { "name": "new notecard", "type": "notecard", "contents": "This is a test notecard", "created": "(timestamp)", etc. ``` * extract/compress - Object/groups as zip/rar/etc. allow for the extraction or compressing of a item/list of items into an archive object. * booleans/loops - for the doing of stuff. ### Terminal As an additional idea, You could have a terminal window attached to the inventory to allow for command line access to the inventories. ### Alternatives to Inv Scripts Rather than having and entirely new inventory type this might work if: * Executable Notecards - Notecards could be used as the scripts if they had a specific flag or naming system.. e.g. "./foldersort" * Additional variant to scripts - Scripts already can be switched between lsl and mono.. could there be a 3rd type for "inv Shell"? ### Why this system There are three main reasons that I have suggested this particular method to achieve this: * Familiarity - For those of a more geeky nature, near fluency is already there. They getting to start at a near sprint. Battle Hardened - Why reinvent the wheel? nix cli is very very well tested so why not borrow from it. * Education - This could help a great many in terms of dipping their toes into CLI usage. * Additionally : - By mirroring the *nix systems there is a huge head start in docu. - Likewise the potential shell scripts that people would have access to that with minor tweaks should work again would be massive. - Ai Support/training. A lot of people are likely to just ask chatgpt for scripts. Closer to *nix we get the better in terms of training LLM. ### Future possibilities * At the current community meets there is a lot of discussion over the implementation of a giveinventory function that would goto a specific folder. The best solution for this would obviously be different for each creator and each customer. There is not going to be one solution. The best solution is going to be one that is customizable. * There would be numerous other things I'd love to see as well. -For example external sources: + obviously text files, feeds etc. would be an easy first. (wget Or curl > nc) + If shellscripts were notecard based then you could grab external files to increase functionality. + Alternate method of file uploads with wget for textures, ani, sounds, mesh etc. (wget) + API Access (Curl) + version control (git) - And Image Resize!! + ability to assign thumbs. ### Conclusions I know, not the smallest of requests.. as long as I've played Sl inventories have been a "mines worse that yours." discussion point. Automation for item givers is improving yet there is little improvement to users capabilities to sort. New windows and image thumbs kind of cancel each other out.
4
Load More