|
|
|
"In other words, full permissions are needed far more often than restricted permissions."
That probably depends on what you're bulk uploading, and what you intend to do with it. My preference would be for the user to be able to set what permissions they want applied to the upload. Implemented user-settable default permissions for all upload types (see screen shot) using patch code from Catherine Pfeffer.
Thanks Catherine! You're welcome, Coco.
From what I can see in the screenshot, the new settings dialog is called from the "File => Upload" menu. That makes sense, because these choices currently only apply to uploaded files. But on the long run, I think it should move somewhere else in the User Interface, because these choices will apply to other things than just uploads: in-world creations and in-inventory creations. But it's a very good start. Thanks Coco for your pushing this forward. Don't hesitate to recontact me for the next steps, I'd like to be useful. Catherine,
We're in full agreement about the future of this feature. Once we can apply default permissions to all new content, the UI should move to the preferences panel. I'm all about doing thins one piece at a time since even medium sized changes can easily become too big for us to digest. Patches can prove that a problem is tractable and help guide our solution whereas without them, the doubt will often cause us to work on other issues that appear more tractable. Your work was very helpful on this one and should save a lot of time and pain experienced by some of our more prolific builders and will result in making the world larger and richer. Thanks again, There are still a few things that could be made better in the current implementation.
As this issue is already well on track for delivery (in version 1.23, normally), I'm opening a new issue This seems like a great feature. I own a texture store (3D Concepts) and it's a horrible boring task to upload thousands of textures at a time to spend yet a nightmarish untold amount of hours manually selecting the permissions for each texture. Furthermore, while you are at it, would be nice if textures could be used to build with, without having to make them full perm. Just about every content provider in SL has a means to protect their work other than the one who provides textures.
I would love to help test this feature. I have about 5000 textures I need to upload now. I am already resenting it. Have finished a few thousand and am not looking forward to the remaining 5. Vryl: I'm glad that this will be a big help to you. In the meantime, you'll be able to use the release candidate viewers once that starts for 1.23 if you're willing to put up with beta quality. Even before that, there might be alternative viewers built on our open source which will include this feature. Just note that it will only work once the corresponding server-side part has been deployed, and that's on another release schedule altogether.
As a last resort, it's possible to speed up the process of one-at-a-time permissions changes. It's still painful but I've found that if you edit the permissions of a range of inventory items at once, they open as tabs so it's possible to quickly click a check box and then hit ctrl-w to close that tab. You can rip through a big list quickly if you only need to check a single box in each one. If you need to click more than one, it is probably faster to make multiple passes through, toggling one property at a time. Clearly an awful solution but better than nothing. Hello there! I'm the one who initially started this Jira, and I want to say Thank you SO much for working on this now. As with Vryl Valkyrie, I work alot with textures, I make over 10 magazines here in SL, each of them around 100-200 pages, every month, so it gets tedious to change the permissions on each texture manually. I know other content creators who deal with many textures, and will love this feature once it's implimented.
Once again, Thank you from all my heart! Kisses Tested this feature out in viewer 1.23.0.117724 (public nightly), it works great!
Yes, but unfortunately this is only a small part of a bigger picture, see VWR-8049, which seems to be stuck now that Coco has left the Lab.
Heres to the hope that it stays in. Andrew apparently likes it, and said its basically good to go.
Fixed in 1.23.4, released on 06/15/2009.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Sub-task
Resolved
Normal
Please hurry with this fix soon. Thanks for all your work.
I believe it is way easier to go in to restrict the few textfile/pictures I need to make no-copy or no-transfer than it is to go into ALL of them to make them full permissions.
In other words, full permissions are needed far more often than restricted permissions.