Bug 492275 - Feature/Enhancement Request: Navigation: Next/Previous Compilation Unit in Package Explorer
Summary: Feature/Enhancement Request: Navigation: Next/Previous Compilation Unit in ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-22 14:45 EDT by Luke deGruchy CLA
Modified: 2016-04-22 14:45 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke deGruchy CLA 2016-04-22 14:45:46 EDT
This is a feature/enhancement request.  I'm not sure if belongs in the IDE or UI category.

This issue requests functionality to navigate to the next or previous compilation unit relative to the currently opened compilation unit in the Package Explorer.   This may or may not require the "Link With Editor" button to be clicked.

So, for example, for package com.example, containing three class files:

A.java
B.java
C.java

And B.java currently open in an editor.

Triggering previous would open A.java in an existing editor tab if one exists, if not open a new open.   Conversely, triggering next would open C.java and either navigate to the existing tab or open a new one.

This functionality would be exposed via a sub-menu in the Navigate menu bar and as an available key binding for a keyboard shortcut under Window > Preferences > Keys.   If there's too much of a possibility of colliding with existing keyboard shortcuts, this can be left unset and the user may opt-in with their own custom keyboard shortcut and deal with any potential conflicts/collisions themselves.