Community
Participate
Working Groups
I'd like to suggest some improvements for Open Type and Open Resource dialogs. First of all, when you typing a pattern and then push "Up" or "Down" key the focus is moved out of mask entry field. I think that it is a good idea to keep it at entryfield. Another improvement could be about navigation approach. Comparing with the IDEA user experience, Eclipse UI for selection a type requires few more "Tab"'s in several cases. One of the possible solutions could be to move the information from "Qualifier" pane into tree-based view within "Matching Types" panel.
moving to platform. That the 'down' goes to the first match is a intended feature. I realize that it might go to the second match already. Also pressing 'Up' on the top match should give focus to the text field again.
By the way, it might be worth to use an UI similar to Ctrl-O Quick Outline in Java editor.
The selection issue is Bug 52709.
Tod, it is not related to the enhancement I'm suggesting. The problem I have is that if you type "stri" then push "Down" couple times, and then type the rest "ng", that second typing is ignored because focus moved into list. Actually I still truing to find a best navigation. The thing I really missing is the possibility to push "Right" on the entry field to pickup the next character from the selected item from the list. Eg. type, type, type, "Right", "Rigth", type... This mayme not so critical for Open type, but I hit this quite often for the code completion popup list.
Any chance to get this feature implemented in 3.1 release?
Eugene - what are your thoughts about the current open type dialog? We are looking (in bug #94382) at abstracting many of the improvements made in the open type dialog and moving to open resource. I don't plan any major functional enhancements beyond what open type does now, but may have cycles to look at specific issues.
(In reply to comment #6) > Eugene - what are your thoughts about the current open type dialog? We are > looking (in bug #94382) at abstracting many of the improvements made in the > open type dialog and moving to open resource. I don't plan any major > functional enhancements beyond what open type does now, but may have cycles to > look at specific issues. I think that ussue about moving focus from entry field on Up/Down keys is still makes sence to resolve. Another thing I'd like to suggest (it was mentioned in other places, probably inenhancement requests for Ctrl-O and Ctrl-T popups in Java editor as well as in comment #4 here) is to allow to use Right key to pickup next characters from the currently selected line. For example if we need to select FileReader, we can type "f", that dialog will show FileInputStream and FileReader, then user can push Right key 3 times and then type "r".
moving Open Resource related bugs to Szymon. Szymon, please move between you and Krystof as needed. Let me know if you have any questions. These are all the bugs I had related to OpenResource.
Do we want to have this functionality in our new OpenType/Resource dialogs? I'm marking it for 3.4 because it can be done still, but as i can see people are not interested in this feature any more. I will discuss it with Krzysztof and we will investigate whether this feature should be introduced or not.
Also I'd expect that if you type "file" and then single click on "FileChooserUI" it would appear in the text entry box, so you could continue typing and deleting and go to "FileChooserDetailViewIcon".
Krzysztof left the team some time ago. I'm removing the target milestone.
Reassigning to Susan.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
I agree with the suggestion of Up/Down removing focus from filter text field. Indeed, it sometimes happen that you make a typo in your filter, don't notice it, then use the arrows to start looking for a specific type, and when you notice you made a typo. you have to back-tab or click in the text field to fix it. It's one click too much.
Apparently the FilteredTree has a similar behaviour. In order to guarantee consistency, we should make sure that FilteredItemsSelectionDialog and FilteredTree have the same behaviour. So if we go for updating one, we also need to update the other one.
