| Summary: | Missing documentation for extension points | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Tod Creasey <Tod_Creasey> |
| Component: | Doc | Assignee: | Nick Edgar <n.a.edgar> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P1 | CC: | eduardo_pereira, Kevin_Haaland, n.a.edgar, Randy_Giffen, susan_franklin |
| Version: | 2.0 | ||
| Target Milestone: | 2.0 F4 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Tod Creasey
The doc for markerResolution is named markerResolutions.html (with an s) The HTML title is wrong also. The title and file name should be switched to markerResolution Randy, could you please fix up the markerResolution doc? Released fixes to marker resolution doc Released docs for acceleratorSets, aceleratorConfigurations, acceleratorScopes, actionDefinitions and startup. contributorClass is still needed and the editor doc describing its use looks OK editors => extendedType - Not reference anywhere in the code. I think this is some left over experimental code. Can we remove it? viewActions/editorActions => definitionId - Not a supported attribute yet. Maybe in the future when key binding is more "real". viewActions/editorActions => description - Not a supported element. We do not show descriptions for these actions in the UI (but we do for Action Sets, which is why it has a decription element) viewActions/editorActions => retarget/allowLabelUpdate - Not a supported attribute. These attributes make no sense for viewActions. For editorActions, it would, but the better way is to use action set part associations instead. editors => icon - Is in the document already. These should all be fixed up in the extension point doc. If an attribute applies in some contexts but not others, that should be stated. cc'ing KH. Just to clarify my comment above. The extension point doc is correct in that it does not include these attributes. Some attributes exist in the code as constants but are either not reference anywhere in the code or only used by specific readers (i.e the abstract actions reader has the description element contants but only the action set reader does anything with it). So the documentation is correct. Could you please capture the required code fixups in a separate PR? All needed changes to the documentation were done. |