• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-2594
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Kagehi Kohn
Votes: 8
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Extended options for setting permissions.

Created: 30/Jun/08 09:38 PM   Updated: 30/May/09 09:36 PM
Return to search
Component/s: Permissions
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates


 Description  « Hide
Having read some posts on the original Jira for "resize only", I realized that as good as it was, it is missing things. One solution to the issues brought up would be to have the existing setting for "no modify" have the effect of turning on/off a full set of flags. But, you could have a separate pane for the object, "advanced permissions". In that, allow the users to specify *precisely* which ones you want to allow, and which ones you do not. I.e., if you need it to be rotate, scale and move, but not allow texture, color, etc., then you "pick" specifically which things you "can" do. Make allowing someone to edit sub items as one of those options, so if you don't want someone making "any" changes to the overall design, they can only edit the entire link set. If you want to allow it, then specify that you can pick "edit linked objects" when changing things, but where the sub-objects own permissions "override" the global ones for the entire link set. I.e., selecting the entire object, then changing a permission, will not "change" the sub-prim's, if its anything other than "allow modify". This is a safety, so that you have to manually configure such an object. (Alternatively, you could have the client "ask" if you want the setting(s) to change for all objects in the link set, so you could still set them for every object, except the one that you created specific rules for.

Since these would be flags, its unlikely that it would add more than a single integer value to the existing data needed for a prim.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Kagehi Kohn added a comment - 30/Jun/08 09:50 PM
This issue extends the idea in SVC-468, and hopefully addresses a few things that where overlooked by the original.