It would be nice to have the download/upload (when working on a remote server) actions in the tab of an open file in the editor.
If I search for a phrase in my whole project and open a file, I don't have the possibility to upload/download the file directly. I do have to open the location in the tree and use download/upload there.
Alternatively the location of the file in the tree could open if I click on a search result.
This feature would allow for quick uploading of files without having to locate the file in the directory/project tree. This is super useful when working with large scale projects.
*** Bug 195105 has been marked as a duplicate of this bug. ***
What kind of files are you talking about? PHP project type has FTP support and C/C++ has also remote filesystems support AFAIK.
The FTP works perfectly from the file tree. The request is to have the upload option be available from the tab context menu of the the file you're working in. I have 4 projects that I may be working in simultaneously with literally thousands of files in total. If I want to upload the file that I just saved, I have to go to the file tree and scroll around until I find that exact file in the correct project to upload it. It would save minutes a day to just go to the tab (where the active file name is displayed), right click, hit upload.
I see. Are you aware of "Select in Projects" action in Editor's popup menu? I think this is exactly what you are looking for. Unfortunately, we cannot add all actions into that generic contextual menu which make sense, because it would make the menu 3 meters long and FTP is not something 90% of NetBeans users need.
This could be done only for certain file types probably so once again:
What kind of files are you talking about? :)
I'm a front-end dev; mostly php and css files.
And actually... no.... I hadn't noticed the select in project option :$ That should make life easier. I'll take some comfort in not being the only one who hadn't figured that out!
Don't worry. You are surely not the only one who overlooked that action. Thanks for more details. Now I can reassign this issue to PHP for further evaluation.