Summary: | [Contributions] Multiple Parents for MenuContribution item | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Marco Descher <marco> | ||||
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
Status: | REOPENED --- | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | Lars.Vogel, nobody | ||||
Version: | 4.1 | ||||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Marco Descher
2012-12-20 03:41:18 EST
The pattern for using MenuContributions as they are now is to group your content in one MenuContribution and insert the MMenu with the same id in your 2 locations. It doesn't work between popup and regular menu, however, as those are different schemes. One of the things I'm considering (although I doubt it will be in 4.3) is to allow model fragments to 1) be more dynamic in nature and 2) specify them using XPath. Then specifying specific locations or multiple parent IDs would be possible. PW Paul, thank you, I understand. This however forces me to introduce menus in the original model instead of linking to already existing menu items. I do not understand the approach you mention in 1 or 2, but if you go for a specific way, tell me if i can help! Created attachment 224969 [details]
emf xpath integration
Part 1 would be to look at model fragment processing. For the existing model, apply fragments at all locations that match their insertion point. Then for any new additions to the model, be able to evaluate them as well.
Part 2 would be to allow insertion points expressed as XPath. See this project set file for the 2 bundles that supply EMF-XPath integration. XPath would be able to specify insertion points more precisely.
PW
Does this still stand as an enhancement request (Requiring the MC to have multiple parents)? I'm supposing no but feel free to repoen. For consideration with bug 324954 PW |