Community
Participate
Working Groups
The CNF should allow a plug-in to contribute to the navigator declaratively without the need to activate the bundle. This can be done by having a new extension point in which the element has label and icon. The element also needs to contain a <triggerPoint> element. A node will then appear as a child of all trigger point nodes. Only if the node is activated (expanded to see children, or an action executed or something) is the plug-in activated. This is an important part of the Eclipse design that speeds up the initial loading of the workbench. I already have code in our application that does this, but it seems this would be such a common requirement that it should be in the framework. I would be happy to submit a patch, though I would have to work on my code a bit to generalize it. We would also have to decide how such nodes could be specified at trigger points. Note that this is a different issue from bug 130221. However, solving this may help the problem in bug 130221 because fewer plug-ins may need activating when a node is expanded (only if the child objects are provided programatically would activation be needed).
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.
