Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352279 - [launch] Flexible debug favourites
Summary: [launch] Flexible debug favourites
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-16 21:59 EDT by Brock Janiczak CLA
Modified: 2019-11-14 03:22 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 Brock Janiczak CLA 2011-07-16 21:59:04 EDT
Build Identifier: 20110615-0604

It would be nice if we could have a flexible way of organizing launch configurations in the launch configuration menu.  Having a single list only works when you have very few favourites (less than about 10).

My proposal is to allow the user to build up a structured favourites list where a launch configuration can belong to one or more groups.  Similar to the favourites list in web browsers.  Adding the concept of tags to launches and displaying those tags as folders might also be an option

It should be possible to add API to AbstractLaunchHistoryAction that won't break clients that already extend it by adding an API that returns the new structured favourites while leaving an API that returns a flat list (which will no longer be used by the fillMenu method)

I could probably make time to help implement this feature if needed.

Reproducible: Always
Comment 1 Lars Vogel CLA 2019-11-14 03:22:45 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.