Bug 436702

Hi,

I have to say that what you suggested is very vague and I didn't understand it at least. What you seem to describe is not what the old quick open did, except for the focus part. The functionality of old and new quick open is same, only the view was changed, it still serves the same purpose and does the exact same thing. 

For recent files, we already have a menu entry.

Created attachment 138196 [details]
New look with not arranged columns and path prefixes missing

Created attachment 138198 [details]
Old look with arranged columns and full paths

Created attachment 138201 [details]
Suggested place where the old functionality could be

Full path is intentionally changed to start from project's base directory.

 > Suggested place where the old functionality could be

Do you mean where the project tool view is? That is way too narrow for such a thing and I am unsure if this is wanted even.

(In reply to Waqar Ahmed from comment #5)
> Full path is intentionally changed to start from project's base directory.
> 
>  > Suggested place where the old functionality could be
> 
> Do you mean where the project tool view is? That is way too narrow for such
> a thing and I am unsure if this is wanted even.

A possibility would be to have the old two column variant as option.
But then somebody must step up to implement that.
I am personally happy with the more compact new variant that is more like what other editors provide for this purpose.

Hi,
I appended three images for the better demonstration of what I meant.

Focus behavior isn't the only thing that changed in the way of displaying files in current Quick Open functionality but f.e. also the way of displaying the paths. Other thing that changed is sorting - in old view all items are sorted by path and in new I can't see any sort key, neither can I see paths aligned under each other, so now, manual searching through the list of unsorted files, imho, doesn't make sense and is harder (please see New look*.png and Old look*.png files).

In a vast project, it could be hard to orientate in paths without prefixes, but I don't mean to criticize the new look and arrangement of current Quick Open, closing when losing focus, etc. My point is, whether it would be possible to preserve the tab-like look and feel either in configuration or as a new panel in Tool View (please see Suggested place*.png file). The latter variant enables to have really Quick open as it is in current version and also have some convenient way of displaying recent/opened files and files from current directories as it was before. 

I personally consider both distinct old and new Quick Open as different functionalities that can be further developed separately as a different means to conveniently open files (The look and feel matters often the most, even though it is just opening files). Lately I have been using fsearch more often as a kind-of-replacement for old Quick Open functionality.

I understand that kate has menu entry for recent files. 

PS. I uploaded images first. As an answer: Yes. Tool-view is narrow in sent Suggested-place picture, but it can be resized to half-to-half with document etc.

> manual searching through the list of unsorted files, imho, doesn't make sense and is harder

Because this is not meant to do what you want. Quick open is not meant for browsing files. The usage should be
- Open quick open 
- type a few letters to filter the list to get to the file you want and press enter

That's it. That's all it is meant for and nothing more. 

There's one additional thing in there, if you have some files open, they will always be at the top of the list when quick-open opens.

> In a vast project, it could be hard to orientate in paths without prefixes

That I believe is not true. Here's why:

You have a project in /home/user/projects/Kate with 100000 files. What gets stripped: "/home/user/projects". That is stripped for all files because it is common among them. Nothing else will be stripped. This results in reduced noise and I believe easier to read path because you have removed the redundant information. 

Again, this is not a file browser. The paths are useful if you have files with similar names, type "Cmake", it will show you a lot of different cmake files with different paths so that you can select the one you want. 

You can additionally do filtering by path if you remember the path. "add/cmk" will give you files from addons/ in kate project.