Bug 544961 - Navigate > Go To > Resource: Dedicated Go To > Project action
Summary: Navigate > Go To > Resource: Dedicated Go To > Project action
Status: CLOSED DUPLICATE of bug 544952
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-01 12:12 EST by Max Bureck CLA
Modified: 2019-03-03 11: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 Max Bureck CLA 2019-03-01 12:12:45 EST
As originally proposed in Bug 517392, an action to navigate to projects (not other type of resources) would be very helpful when navigating through huge workspaces. This could be located under the "Navigation > Go To" main menu entry.

A quick look in the source code revealed that it should be fairly simple to add a similar action as the GotoResourceAction, since it would only differ in a call to the GotoResourceDialog constructor with a different typesMask parameter.

Alternatively, an implementation could be built on top of the outcome of Bug 544952 (provided this bug is accepted and implemented) by setting the proposed resource type filter to "projects" on start of the dialog.

Another related issue is Bug 544957, which I guess would cause bigger refactorings to the "Navigate to Resource" dialog. The work on that issue and this one should probably be coordinated to avoid problems.

It can be discussed if a dedicated action makes sense, especially if Bug 544952 ends up being implemented. In the teams I work in, I see a lot of people inefficiently navigating to projects in huge workspaces. A quick dedicated action   for navigation to projects that can have an own key-binding would be a great help.
Comment 1 Dani Megert CLA 2019-03-03 11:22:20 EST
I think using a filter is more flexible.

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