Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 28885

Summary:	launchShortcut extension point precludes reuse
Product:	[Eclipse Project] Platform	Reporter:	Jared Burns <jared_burns>
Component:	Debug	Assignee:	Platform-Debug-Inbox <platform-debug-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	2.1
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Jared Burns

2002-12-27 11:32:34 EST

Launch shortcuts specify which perspectives they'll appear in. This limits
the shortcuts' availability to perspectives that the shortcut author knows
about. This isn't friendly in terms of extensibility.

The current support implicitly handles the case where a vendor wants to
exclude function from other plug-ins but it doesn't handle the case where a
vendor wants to include that function. If a plug-in is written that
contributes a perspective and a launch shortcut, the launch shortcuts cannot
appear there even if it would make sense to have them.

Instead of handling one case implicitly, could we enable both cases
explicitly? We could either allow plug-ins to specify whether they want to
include all 3rd-party shortcuts or none. Alternatively, we could allow
plug-ins to include and exclude shortcuts on a per-item basis (but this
would also not be extensibility-friendly).

Comment 1 Jared Burns

2002-12-29 11:58:56 EST

The way the Run As menu works now is that if you're in a perspective for which
a "Launch Shortcut" (one of the things that appears under "Run As...") has been
registered, the Run As menu will only show shortcuts that are registered for
that perspective. If no shortcuts are registered for that perspective, the Run
As menu will show all shortcuts.

For the user, this creates a confusing and inconsistent experience as the
launch shortcuts appear in some perspectives but not others in an unpredictable
pattern.

Comment 2 Andreas Guther

2002-12-29 14:28:17 EST

I think it would be helpful if the end-user could configure the run-as
menu entries under the running man icon via the Customize Perspective
view.  That would allow the implementor of a perspective to set the 
default run-as entries as well as letting the end-user later decide 
how the perspective fits to his preferences.

Comment 3 Darin Wright

2003-01-02 08:55:45 EST

The intent here is a Jared has stated (discovered?). When in a perspective that 
decalares no shortcuts, they all appear (as in the resource perspective). When 
in a perspective for which shortcuts are defined, only those defined appear. 
Thus, when in the "java perspective", only relevant shortcuts appear. 

This does have a problem - if a new (relevant) perspective is added, that the 
shortcut "contributor" is not aware of, the shortcut may not appear in that 
perspective.

Comment 4 Darin Wright

2003-05-15 16:06:31 EDT

Investigate for 3.0

Comment 5 Darin Wright

2004-03-01 17:18:10 EST

Deferred - hopefully less of an issue with context menu launching.

Comment 6 Darin Wright

2004-07-29 16:17:44 EDT

marking as a dup of newer bug 55804, since it contains a newer discussion.

Comment 7 Darin Wright

2004-07-29 16:17:54 EDT


*** This bug has been marked as a duplicate of 55804 ***