Bug 539065 - [Req] Unify UI between different uses of "Refactor > Move"
Summary: [Req] Unify UI between different uses of "Refactor > Move"
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-14 05:42 EDT by Luke Hutchison CLA
Modified: 2018-09-14 05:42 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 Hutchison CLA 2018-09-14 05:42:19 EDT
Given this code:

    public static class A {
        public static final int fieldA = 0;
    }

    public static class B {
        public final int fieldB = 0;
    }

Using "Refactor > Move" to move fieldB to class A gives a nice hierarchical list of classes that you can use to select the destination class. (The window title is "Textual move".) However, there are some downsides to this: if a class is hidden from the tree view because its package is "folded", then typing into the treeview (to search for a class name) cannot find the class until you manually click on the package name to un-fold the package.

Using "Refactor > Move" to move fieldA to class B gives a much terser dialog ("Move static members") that does not show a tree view, but rather a text field. You have to type the fully-qualified class name of the destination class into the box. Ctrl-Space does bring up autocomplete options, which is helpful.

It would be great if both of these views were combined, so that every use of "Refactor > Move" has both a tree view and a text input box, to allow move destinations to be selected using either mechanism.