Re: Re: "Retrieve Revision as..." default file name

Am 15.12.2003 um 13:10 schrieb kaczoroj:

> Jens,
>
>> Compare the file names when doing a "Retrieve Revision as..."
>> from graph view or when doing a "View Selection" from graph view:
>> In the first case, you'll get "foo.cpp.#1.3.45", whereas in
>> the second case, you get the much more useful name
>> "foo_view_1.3.45_2.cpp".
>
> The difference is that for the view the file is created in the temp
> directory and it gets deleted at the exit, while the retrieve
> operation places the copy of the file in the same location as original
> file.
>
> To prevent overwriting the working file we have to change the name and
> we've chosen to follow files naming convention similiar to the CVS
> backup files (.# prefix - created during merge) but as a suffix and
> followed by the revision number so you can tell what it is.
>
>> I think the "Retrieve Revision as..." command should also provide
>> a name in a form similar to the "View Selection" case (exluding
>> the word "view" or course). That would be more consistent, but
>> at the very least, the command should preserve the extension.
>
> I am not sure about the preserving of the extension as I am sure Java
> folks will run into troubles (Java compilers are often picking up any
> files they can find on their way) but I have no objections to changes
> in naming convention in general.
>
> Basically the retrieved file should look different from the files
> normally used by people so they will not start working on these by
> mistake (hence the .# comes in handy as it's the CVS convention) and
> it should have the revision number embedded into the name and the
> files' original name to easily see where they come from. I am not sure
> whether moving currently used suffix to the front will affect normal
> CVS operation but it probably shouldn't.
>
> So the effect would be something like that:
> .#1.3.45.foo.cpp

That will make the file invisible on Unix-flavored operating systems, 
where files starting with a 'dot' are considered 'hidden', i.e. only 
visible if the user chooses to see all the clutter.

I agree that the #.revision naming scheme makes the file distinct from 
regular working files, so that's probably good to have...
I'd suggest a naming scheme like

<ORIGINAL_NAME> .# <REVISION> . <ORIGINAL_EXTENSION>

If Java folks have problems with this, they can always point the file 
browser to a different location in the "Retrieve Revision as..." 
command...?
Having the name first will also make sure the files are sorted by their 
'real' name in the file browser, which IMHO is what you'd usually want.

To make things [over-?] perfect, this could be a configurable option 
where we could specify three placeholders for ORIGINAL_NAME, REVISION 
and ORIGINAL_EXTENSION. (Might be a bit overkill to have a pref for 
this, though...)
Or maybe a simpler option that allows to choose between 
"foo.#.rev.extension" and "foo.extension.#.revision" would be 
sufficient (should be a per-sandbox setting)?

</jum>


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/NhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/