While working in a Workspace or Project, it would be very convienient if we can:
1. right click on the mouse on the file name tabs, and choose "rename file"
2. This would then rename the file, associate the new file name with the current workspace and/or project
if the old file name previously existed in that workspace or project.
3. It would then delete the old file from the file system and disassocate
it from the associated workspace and/or project.
I figured this would make re-organizing your files in your projects very easy.
Right now, I have to do everything multiple steps the long way, and sometimes I forget.
This way, I don't!
I support the basic idea, but I would like to leave the implementation details open.
I can see how that could be useful if the files are not under source control.
If the files are under source control then it gets trickier. Some source control managements systems ("SCM"s) don't support rename. And in most SCM systems that do support rename, it is important for the underlying rename operation to be done by the SCM software. Also, some SCMs have special additional semantics regarding rename.
I don't think SE's current version control integration supports rename operations.
It sounds like an interesting idea, but it might be a bit complicated to do a good job of implementing such a feature.
The story is even more complicated. As C++ developer you often have a class
MyClass in the files
MyClass.h and
MyClass.cpp.
Apart from the
class name also the corresponding
file names may be referenced by
1. project files of SlickEdit (*.vpj) of current workspace file (vpw).
2.
associated project files of another IDE such as Visual Studio (*.vcproj)
3. a version control system
4. #include directives in the files of the current workspace
5. 'include guard' in MyClass.h (for example #ifndef INCLUDE_MyClass_H)
6. ...
A perfect
class renaming (as part of refactoring) would synchronize all mentioned references. But probably this is asked for too much in one step.
Point 2 is crucial. If a vpj file is
associated with the project file of another IDE then renaming files of the project is the job of the other IDE (as well as deleting and adding).
Otherwise it would certainly be a step in the right direction if SlickEdit could rename a file with automatic adjustment of the corresponding references in the vpj files of the current vpw file (regardless of point 3, ...).