Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339933 - [cheatsheets] allow command browse to present non-Eclipse commands
Summary: [cheatsheets] allow command browse to present non-Eclipse commands
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 14:12 EDT by Scott Lewis CLA
Modified: 2019-11-08 04:36 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Lewis CLA 2011-03-14 14:12:04 EDT
Currently, the simple cheatsheet editor allows commands to be associated with cheatsheet items, to support invoking selected commands at cheatsheet runtime.

The simple cheatsheet editor has a browse button that allows the editor user to select commands (and their associated arguments) to invoke for a given cheatsheet item.

However, the list of command items that are brought up by use of the Browse button seems to only include commands that are running within Eclipse.  For people developing cheatsheets for RCP applications, for example, this doesn't present an appropriate list of commands for cheatsheet development...as the Eclipse commands are not appropriate for the RCP app, and the RCP app's own/new commands do not appear.

Ideally, the command Browse would search both the target platform bundles, and/or any commands declared in the workspace (in addition).
Comment 1 Lars Vogel CLA 2019-11-08 04:36:54 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant please remove the stalebug whiteboard tag.