Summary: | [IDE] File "save as" should auto-suggest name and folder based on package name in file | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Ken Silveman <kensilverman> |
Component: | IDE | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | daniel_megert |
Version: | 3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Ken Silveman
2005-06-30 20:03:42 EDT
The untitled text document is created by Platform Text and at that level we don't know anything about Java, C++ or any other project type and its expected setup or structure for its files. There would have to be something like a 'saveAsParticipant' extension point where clients could plug-in code that is run when a file is saved under a different/new content type, e.g. - switch to the correct editor - create the correct project structure and/or build path ... Note: you could use the New Class wizard to create the class. I think that at a minimum we should offer to save the file as "Untitled1" or some name that just allows the user to quickly save it to something. Well, Having a java plug-in created by your team and shipped automatically with the Eclipse executable would be very good (as well as other plug-ins for other languages.) It should simply look at the line "package a.b.c" and then create the directory structure and then suggest adding the file with the same class name. There should be a Default plug-in selector on the menu so a user could easily change default plug-ins provided by your team - and added to by the user if desired. In fact, a set of plug-ins should be loadable based on the user selcting a radio button: "java", "c++" or etc... Then a whole set of default plug-ins may be loaded and swapped with others at the touch of a radio button, each mapping to a set of plug-ins where each set are in sub-directories that map to what button is selected. (In reply to comment #1) > The untitled text document is created by Platform Text and at that level we > don't know anything about Java, C++ or any other project type and its expected > setup or structure for its files. > There would have to be something like a 'saveAsParticipant' extension point > where clients could plug-in code that is run when a file is saved under a > different/new content type, e.g. > - switch to the correct editor > - create the correct project structure and/or build path > ... > Note: you could use the New Class wizard to create the class. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |