Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 176440 - Add optional description attribute to launch shortcuts
Summary: Add optional description attribute to launch shortcuts
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 3.3 M6   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 74480
  Show dependency tree
 
Reported: 2007-03-05 20:15 EST by Darin Wright CLA
Modified: 2007-03-19 09:59 EDT (History)
0 users

See Also:


Attachments
patch (14.40 KB, patch)
2007-03-13 12:51 EDT, Michael Rennie CLA
no flags Details | Diff
patch (14.66 KB, patch)
2007-03-13 13:50 EDT, Darin Wright CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2007-03-05 20:15:54 EST
To support "simplified launching for novice users" (bug 74480), we would like to add an optional attribute to launch shortcut extensions. The new attribute is a "description" attribute that would be displayed in a selection dialog when the users launches a resource for the first time and the user must choose from available launch shortcuts for the resource.

The description field would provide users with more information about the "way" they can select to launch a resource. For example, the description for a "Java Application" would be something like "Launches a Java virtual machine locally on the selected main type".

We should allow for messages specialized for the selected launch mode - so we could have specialized messages for debug vs. run - i.e. "Launches a Java virtual machine locally on the selected main type with support for debugging".
Comment 1 Darin Wright CLA 2007-03-05 20:18:48 EST
Mike, it feels like the message should actually be tied to the launch delegate that would be invoked from the shortcut... for example, if the launch shortcut maps to the "Java Application" configuration type, we could ask the preferred launch delegate for its description? (not sure what we do if there are multiple configuration types for a launch shortcut).

However, this way the message is specialized per launch mode and for the tooling that is "selected/preferred" for that configuration type.
Comment 2 Michael Rennie CLA 2007-03-13 12:51:12 EDT
Created attachment 60690 [details]
patch

This patch adds in the new fuctionality of providing descriptions for launchshortcuts. Contributors can now (optionally) provide a description for their launch shortcut contribution generally, or for specific modes only.

This patch introduces new API to the launchShortcuts extension point and will require PMC approval
Comment 3 Darin Wright CLA 2007-03-13 13:32:57 EDT
Clarification - we decided to add the description field to the launch shortcut, allowing for mode specific descriptions. This is more flexible than relying on the existing launch delegate description as there could be more than one launch shortcut using the same underlying delegate (for example, Ant has two shortcuts but both use the same underlying delegate).
Comment 4 Darin Wright CLA 2007-03-13 13:50:40 EDT
Created attachment 60703 [details]
patch

slight change to schema descriptions
Comment 5 Mike Wilson CLA 2007-03-13 14:57:35 EDT
+1
Comment 6 Michael Rennie CLA 2007-03-13 16:02:19 EDT
released patch with some JUnit tests as well
Comment 7 Michael Rennie CLA 2007-03-13 16:02:35 EDT
please verify Darin W
Comment 8 Darin Wright CLA 2007-03-19 09:59:31 EDT
Verified.