Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Build Identifier: 20090619-0625 I am creating an eclipse plugin where different users have different roles. I am able to define what the user is able to see with no problem. My problem is when they are not allowed to see a perspective because of their roles, they simply have to open the "open perspectives" dialog, then click the "show all" check box at the bottom, and then they can attempt to open that dialog. It then states that a certain activity must be enabled in order to open that perspective and asks if you would like to enable that activity. After they click yes, then the perspective is opened. There needs to be a way to disable the org.eclipse.ui.internal.activities.ws.EnablementDialog from loading and a message dialog should show up that simply says that you don't have the required activities to be able to show that perspective rather then allowing them to give themselves permission to show that perspective. It would be great to if the perspectives that were not enabled because of the activities could not be seen either. Reproducible: Always
Created attachment 149486 [details] The dialog that opens now
I'd consider adding a "don't show ask the user" preference for RCP apps. That would remove the pesky check boxes from the wizards and open dialogs. But we'd have to make sure it doesn't interfere with activity behaviour. PW
Have you considered using expression-based activities? They don't take part in the "trigger point" logic as normal activities do.
The only way I have been able to figure out to make it work now is to add another service source provider that tells the workspace if a perspective is enabled or not and then added an enabled when to an activity. Then I created an activityPatternBinding that binds the perspective to that enabled activity. Just adds a lot of extra logic to our system. I think that is what you meant Mr. Bokowski but am not 100% certain. It just seemed to me like something that should be able to be disabled so that a user couldn't automatically enable whatever activities that he liked.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
