| Summary: | EMenuService/MenuContributions - need equivalent for toolbars | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Paul Webster <pwebster> |
| Component: | UI | Assignee: | Paul Webster <pwebster> |
| Status: | RESOLVED FIXED | QA Contact: | Paul Webster <pwebster> |
| Severity: | normal | ||
| Priority: | P3 | CC: | bokowski, remy.suen |
| Version: | 1.0 | ||
| Target Milestone: | 1.0 RC0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 316802 | ||
| Bug Blocks: | 316299 | ||
|
Description
Paul Webster
Remy introducted MToolBarContributions. How do they work in an e4 app? When are they applied? PW (In reply to comment #1) > How do they work in an e4 app? For a part's toolbar, you'd define an MToolBarContribution with your parentId pointing at a part's id. For the trim, you'd use a TrimContribution pointing at a given MTrimBar. > When are they applied? Assuming the part has a toolbar, the contributions will be applied to the toolbar after the part's object has been instantiated. Trim contributions will be processed when the trim's widget has been instantiated. The exact timing of these may need to be reworked because of "timing" requirements for the compatibility layer. |