| Summary: | add editor context menu contributions for PDT editors | ||
|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Scott Lewis <slewis> |
| Component: | ecf.ui | Assignee: | ecf.core-inbox <ecf.core-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | jeffmlevy, remy.suen |
| Version: | 1.2.0 | Keywords: | helpwanted |
| Target Milestone: | 2.0.0M7 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Scott Lewis
Is there an associated reference bug to this or something? > Is there an associated reference bug to this or something?
No, it should have been entered as enhancement.
It seems that the PDT php editor actually uses the context from the WTP StructuredTextEditor. If I added markup like the following to our example collab application:
<!-- php editor -->
<extension
point="org.eclipse.ui.menus">
<menuContribution
locationURI="popup:org.eclipse.wst.sse.ui.StructuredTextEditor.EditorContext?after=additions">
<dynamic
class="org.eclipse.ecf.internal.example.collab.EditorCompoundContributionItem"
id="org.eclipse.ecf.example.collab.structuredtexteditorcontribution">
</dynamic>
</menuContribution>
</extension>
Note the locationURI. This specifies the StructuredTextEditor.EditorContext for this contribution.
With this markup the ECF menu contribution *does* appear in PDT's php editor context menu. The nice thing about this, is that if other editors based upon wst's StructuredTextEditor are present, then they will also show these menu contributions and be able to use them! So this should make a number of other editors (all those that use or extend wst StructuredTextEditorContext) without further additions.
I've committed this addition to HEAD, and this will be in the 4/24/2008 daily build for testing.
Resolving as wontfix due to resources. If contributor or committer resources become available then please reopen. |