Community
Participate
Working Groups
As of Eclipse 3.2M5, you can define a capabilities category, but you cannot define subcategories. I think that could be helpful and help make capabilities more customizable. In the main Capability preference page, you could list all the capability categories & subcategories. And when you hit Advanced.. you'll see all the specific capabilities. For example: (main page) Development -Web Development Team (Advanced..) Development -Java Development Capability -Web Development --HTML Development Capability --JSP Development Capability --JSF Development Capability Team -CVS Support Capability
Created attachment 35928 [details] Visualization of capabilities dialog with subcategories Good idea Amy. This is what I'm thinking wrt displaying subcategories in the capabilities dialog.
We avoiding doing this initially because the intention was to encourage people to use coarser grained capabilities and to discourage forcing users to dig deep into a hierarchy to get what they are after
Subcategories wouldn't really force users to dig deep into the hierarchy if they didn't want to. They could just check categories at a higher level and pick everything up. The subcategories will allow more customization for users and for other products if they want to turn some specific capabilities on and some capabilities off. (especially products that build on top of another)
i think the preference page should also show activity bindings as a tree. especially in the case, the bound activity has no category binding. this would look like the attached screenshot for subcategories. subcategories should be displayed as a folder, not as a categorie as shown in the screenshot. but this would be a very nice feature.
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.
