Community
Participate
Working Groups
I usually open up java files for editing or just browsing in my favorite java IDE such as jdk source files or other random java files that I may come across. I don't necessarily want to compile them or even add them to my project, just look at them. As far as I know, this isn't possible to do in eclipse and it forces me to use notepad which has no color coding or quick access to methods (Outline). The only option is to import the file into the project and delete it after I'm finished looking at it.
Moving to UI for consideration. It's possible to open a read-only editor on a non-workspace input so this is feasible. David, as an alternative it is quite easy to copy files into eclipse using drag and drop or copy/paste from your window manager. You can then view the file and dispose of it when you're finished with it.
Why limit to a read-only editor? Why not drag'n'drop any text file into eclipse and edit it? There is life beside the project and very often you have to edit a text file that is not in my eclipse project (System files, Mozilla user prefs, html pages, anything). Why should you keep another editor (even if you like jedit ;-) ? For me it is important to be able to drop a file from explorer to an editor, be it open or in the task bar. Quite often I use send-to editor from within a file open dialog.
I agree. You should be able to read and write files that aren't in your project. I'd like to use eclipse as an editor for files that aren't in my project.
There is a lot of relevant discussion to this one on 4922 and 6664. Basically if we could edit a file (text, java, xml, etc) that lives outside of a project many good things would happen. We could get a "file open" command under the "File" menu and it would be possible to open a file by double clicking it under Windows, or we could open a file using the command line. All of this obviously requires that ability to use an editor with a file that does not belong to a project. If that means the editor is not as full featured as it is with a project file, then that is fine, as long as some of the features are there, such as syntax coloring, etc.
In addition to the previously mentioned methods to open a non-project file, I would like to see Drag n'Drop added as well. I commonly open files by dragging them onto my editor.
See also Bug 2869. It seems to be asking for a programmatic way to open external files.
*** Bug 6637 has been marked as a duplicate of this bug. ***
Text team has done the work for File > Open External File.
Has been fixed a while ago.
*** Bug 13221 has been marked as a duplicate of this bug. ***
*** Bug 37935 has been marked as a duplicate of this bug. ***
I tried it under Windows with M8 and it does not work for files that should be opened by some plug-ins and external programs. I tried to open an XSD file. When it was associated with the extention point editor it opened, when it was associated with XMLBuddy it did not, nor when it was associated with an external editor (Stylus studio).
Thanks for the comment. Yes, somehow Open External File has been implemented so it doesn't work with third-party plug-in editors. Very unsatisfactory "resolution". Assuming it's too late to have this implemented in a compatible way, how about sharing with the rest of the world what has to be done to make this work?
It's not just with third-party plug-ins. I filed bug 58179.
Right. I added a comment to bug 58179 to note that the problem is not just with plugins that ship with Eclipse.
Perhaps the title of this bug should be changed to reflect what was fixed. I assume that is now Eclipse can open external text and java files. And keep it closed and send all people looking for general external file open ability to bug 58179.
