Community
Participate
Working Groups
It's currently only possible to add to the status line from editors, views, and the application's action bar advisor. It should be possible to add to the status line independently from views and editors, and without having to hardwire the contribution into the advisor. The way action sets can add to the menus and toolbars provides a good model. In fact, piggy-backing on the action set mechanism would afford a fair bit of flexibility, since action sets can be associated with perspectives and parts, filtered by activities, etc.
*** Bug 47849 has been marked as a duplicate of this bug. ***
(The RCP tag is there because RCP apps tend to push on this more than the IDE use cases, though bug 47849 is a good example from the IDE stack.) I know improvements here are being considered under the new commands support, so piggybacking on action sets may not be the best choice, but whatever we do, we shold allow the same kind of flexibility as action sets have.
Is there a workaround at this point?
One workaround would be for the app to roll its own extension point, and manage contributions from the workbench advisor. Classes on the extension point could implement something like: interface IStatusLineContributor { void fillStatusLine(IStatusLineManager); } The advisor could create a SubActionBars for each contributor, which wrappers the main action bars. activate() / deactivate() on the SubActionBars instance can then be used to show/hide the contributions depending on context. This approach means that all contributing plugins will be activated eagerly though, but that's probably necessary in the case of status line contributions. They're more likely to be creating interesting controls, rather than just actions that that can be described declaratively then activated for real later.
Is this covered by bug 36968 ?
Moving Dougs bugs
Assigning to component owner PW
This item has been fixed/superceded by the menu contribution mechanism - bug 154130 Menu contributions allow controls to be contributed to trim and the status line. PW
The bug referenced in comment #9 (bug 154130) is not fixed and also not scheduled to be fixed. You spoke with authority that work has been done to address this - was it simply the wrong bug number?
(In reply to comment #10) > The bug referenced in comment #9 (bug 154130) is not fixed and also not > scheduled to be fixed. You spoke with authority that work has been done to > address this - was it simply the wrong bug number? Sorry, Ian, that bug (despite some of the rambling and randmo patches) the plan item for the menu contribution work (I know, not obvious). It includes the new menus API as well as the work done in the org.eclipse.ui.menus extension point. It covers the work that would allow an arbitrary control to be added to the status line that would not be tied to a view or editor. There is more information available at http://wiki.eclipse.org/Menu_Contributions PW
