Community
Participate
Working Groups
Why is TextActionHandler duplicated in org.eclipse.ui.navigator?
TextActionHandler exists in the IDE, which the base CN framework can't depend on. See also bug 124512. Does CN's copy of TextActionHandler need to be exposed as API though?
Yes, Bug 124512 covers what I'm thinking of: a separate plug-in.
The TextActionHandler in CN has a few minor enhancements (such as the Accelerator action text in the menu item (upcoming)) and some slight changes around when fill action bars is invoked (the CN must do this on selection change instead of just view activation). The version in this layer is not exposed as API and there are not intentions of doing so. I am open to changing where the TextActionHandler used by the CN comes from, with the minor enhancements made taken into account. Closing as WONTFIX for now. I suggest the discussion be held again in the next release in the context of bug 124512.