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

Bug 51003

Summary: [launch][menu] Make launch favorites be buttons on the toolbar
Product: [Eclipse Project] Platform Reporter: Ed Burnette <ed.burnette>
Component: DebugAssignee: Platform-Debug-Inbox <platform-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: ben_hutchison, filipe, mkomor, mooreb, n.a.edgar, nicholls, pawel.1.piech, remy.suen, timmak
Version: 3.0Keywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
Custom Toolbar implementation none

Description Ed Burnette CLA 2004-01-30 17:30:40 EST
Currently when you mark a launch configuration as a "favorite", whether it's 
for Run, Debug, or External Tools, all it does is add the item to the top of 
the submenu. For example if I make an external tool config called "Test", mark 
it as favorite, then select the little down-arrow next to the External Tools 
toolbar button, I see "Test" in the list. If I select that menu item then it 
runs the Test program.

In my opinion, this doesn't add a whole lot of functionality because recently 
executed programs are already added to that menu without having to mark them 
as favorites. The only advantage is that it pins them to the top portion of 
the menu.

The current scheme is particularly troublesome when you're alternating between 
two programs. For example I often want to run a client and a server program, 
or two different client programs. Then I make some adjustment, terminate the 
programs, and want to run them again. With the current code (as of 3.0m6) I 
have to do a lot of repetitive menu navigating - click-drag-click, over and 
over again.

What I really would rather see is to have a new toolbar button appear for each 
favorite, perhaps to the right of the External Tools (or Run or Debug) button. 
It could have a generic icon with a tooltip that says "Test", or maybe it 
could be a customizable icon or even a plain text button. Regardless of how it 
looks, the important thing is that when you single-click that toolbar button 
then it runs the Test program.

With this new functionality, you would just have to click once on each 
favorite program you want to launch. When you have to do this a hundred times 
a day, having this feature would really reduce the repetitive motion currently 
needed and make it less error prone.
Comment 1 Nick Edgar CLA 2004-02-04 11:57:46 EST
This is a Debug feature request that will require new Workbench support.
Moving to Debug for comment.  Perhaps Chris could consider this as part of his 
investigations into dynamic menus;.
Comment 2 Darin Wright CLA 2004-02-05 11:01:59 EST
Notes:

* the favorites support is modelled after IE's favorites - i.e. you can decide 
what appears in the menu, and in what order
* we have anohter feature request to add key bindings to launch configs, which 
will also enhance the use of favorites
Comment 3 Ed Burnette CLA 2004-02-05 12:23:42 EST
I've used a system that just had the key bindings (TextPad external tools) and 
it is somewhat useful but not terribly. The ability to easily add a button on 
the toolbar (whether you continue to call it favorites or whatever) would be 
much better.
Comment 4 Darin Wright CLA 2004-02-08 17:21:58 EST
Currently deferred.
Comment 5 Mary Komor CLA 2005-01-24 14:47:49 EST
We've had customers who have requested for this feature as well. 
Comment 6 Darin Wright CLA 2005-06-03 09:01:13 EDT
*** Bug 98238 has been marked as a duplicate of this bug. ***
Comment 7 Darin Wright CLA 2006-03-06 13:08:16 EST
*** Bug 80447 has been marked as a duplicate of this bug. ***
Comment 8 Darin Wright CLA 2006-03-06 13:10:21 EST
*** Bug 127803 has been marked as a duplicate of this bug. ***
Comment 9 Darin Wright CLA 2006-03-06 13:10:51 EST
See bug 127803 for contributed patch/implementation.
Comment 10 Tim Mak CLA 2006-03-10 11:53:39 EST
I have created a patch which implements the feature described by this bug.  It allows a user to define their own icon for a launch configuration, and to add these launch configurations to the Toolbar area.

This patch was created against the CVS repository on March 10th, 2006.

THe patch affects 4 plug-ins:

org.eclipse.debug.core
org.eclipse.debug.ui
org.eclipse.ui.externaltools
org.eclipse.ant.ui

The latter two plug-ins are only affected due to a refactoring of 2 classes, to avoid circular dependencies.  The bulk of the changes occur in debug.ui, with a few small changes to debug.core.

While implementing this feature I ran into a separate bug regarding launch configurations and putting them on the favourites list.  I have opened a separate bug for this.  Please see Bug 131346.

This patch provides the following:

- Alters the tab group viewer to allow the specification of a user defined icon for each launch configuration (with dynamic variable support)
- Leverages the existing framework used to manage the launch configuration Favourites list, and adds the ability to show these configurations on the toolbar
- Toolbar buttons can be repositioned by re-ordering the favourites list
- When a launch action is invoked from the toolbar, the launch mode is retrieved by querying for the launchGroup from the launch history (again, using the existing framework that the Favourites list uses)
- An action was added to the external tools drop down menu to switch the toolbar on and off
- The delegatingModelPresentation (label provider) now gives precedence to user specified icons, before attempting to retrieve the default images.

I am submitting this patch in hopes that this implementation will make it in to the next Eclipse release.
Comment 11 Tim Mak CLA 2006-03-10 11:55:00 EST
Created attachment 36064 [details]
Custom Toolbar implementation

Patch for what I described above.
Comment 12 Denis Roy CLA 2009-08-30 02:17:35 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.
Comment 13 BenH CLA 2010-12-18 01:22:08 EST
Deaf to your users. A bureaucratic, corporate parody of the "open" source you claimed to be. Please don't go that way, Eclipse.

Heres a much requested feature. 6 years old. 3 duplicate reports. 2 contributed patches. Simple and useful. 

To what end? "Status: RESOLVED WONTFIX"

Sadly, this is no isolated incident, the Eclipse bug database has several of these sorry stories, each with queues of frustrated users piling up behind blocked tickets. Eg, some of the infamous ones:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=36939
https://bugs.eclipse.org/bugs/show_bug.cgi?id=35779

..although unlike those other two, this one is not particularly difficult or controversial to fix.
Comment 14 Remy Suen CLA 2010-12-18 08:22:21 EST
(In reply to comment #13)
> Heres a much requested feature. 6 years old. 3 duplicate reports. 2 contributed
> patches. Simple and useful. 
> 
> To what end? "Status: RESOLVED WONTFIX"

In the Debug team's defense, the bug was originally set to RESOLVED/LATER (which I admit is not exactly "ideal").
https://bugs.eclipse.org/bugs/show_activity.cgi?id=51003

Those resolution states no longer became valid so the webmaster performed a mass conversion of all bugs previously in either of those two states (see comment 12 above yours and the history that was previously linked which shows Denis changed it from LATER to WONTFIX).

I am going to reopen this bug on the grounds that there are still people that consider this important based on comment 13.
Comment 15 Pawel Piech CLA 2011-06-03 12:07:01 EDT
The attached patch does a lot more than the title of this bug.  Any interest in implementing this feature using the command framework?
Comment 16 Curtis Windatt CLA 2012-11-20 11:15:24 EST
Comment on attachment 36064 [details]
Custom Toolbar implementation

Marking the patch as obsolete as it has many conflicts with the current debug code and includes changes that are unrelated to this bug.
Comment 17 Lars Vogel CLA 2019-11-27 07:18:17 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.