-CaseCode individual files #742
Description
Something I ran into today is a need to use -CaseCode in a limited fashion. By and large my applications do not need case-coding, but once in a rare while I need to add it to a specific name. But I don't really want to see all of my hundreds to thousands of file names all have case-coding on them in the directory. Therefore, I'd like to see implemented a way to use -CaseCode on individual names upon demand.
My first idea is to add -CaseCode as an option to ]Link.Add. That way I can specify a single name (or more likely two) that need case-coding because of a conflict, without performing it on every name in the workspace. Since ]Link can already handle the situation where this already exists, all I need is a method for creating the situation in the first place. If I use something like ]Link.Add xxx XXX -CaseCode then I can specify where I want this to take place. The problem with this is if I already have one of the names in use without case-coding then I need to be able to change the storage mechanism for that one name before creating the second name. Then I'd need to do it again on the second name so that both names end up with case-coded file names for better clarity. Of course, ]Link.Add would have to know that it was renaming an existing file and handle that automatically.
My second idea, mostly for initial storage of existing code, is to make -CaseCode smarter on ]Link.Create. If it provided me a way to indicate that not all files needed such coding then it could automatically detect when there was a case conflict already existing in the workspace being stored and automatically use the case-coding nomenclature on just those files instead of everything in the workspace. That leaves virtually all my file names much more readable to the human eye with minimal effort.