Community
Participate
Working Groups
Build ID: 3.4 Steps To Reproduce: I have a customer that was looking to remove certain perspectives from view, for security reasons as well as business reasons. They tried disabling the capabilities in the preferences, but it didn't really get rid of the ability to see perspectives. We found the only way to do so would be to delete associated plugins, but this would not be a supported action. They've asked that I submit an RFE for this functionality, because it would be a way to improve their role groups and manage their teams, because they could specify functionality based on their team role. Specifically, the perspectives they were looking to disable or not allow were CVS and Data Tools More information:
One way would be to remove the definitions from the plugin.xml using the Adapter Hooks API. http://wiki.eclipse.org/Product_Customization can remove specific extensions using XSLT as of eclipse 3.3 once set up for a given product (and is per product, so a different product could run from the same bundle repository with the original code). Also, in 3.4 activities/capabilities that support core expressions were added. The advantage of core expression activities is that removing a perspective contribution using them would remove it from the perspective registry as well as the appropriate dialogs. Thes options are both available in the 3.4 based eclipse, and it sounds like either would provide the functionality they are looking for. PW
Assigning to [Perspectives] to get it out of inbox but its really more about UI reduction. Also something to think about for 4.0.
It sounds like one of the two candidates would work for you, either using an ISourceProvider to provide the team roles to the IEvaluationService and the core expression activities or using the product customization hook with that product (with product customization, a restart is required to change what is filtered). If either of these don't work let me know (RE-OPEN) and we'll try and figure out why. PW
Paul, does the second (core expressions) approach also remove it from 'Quick Access' ?
(In reply to comment #4) > Paul, does the second (core expressions) approach also remove it from 'Quick > Access' ? Yes, core expression activities remove it from the perspective registry completely. PW
