Re: GUI client that checks out 1 file?

[Todd Denniston]

Phil R Lawrence wrote:
> 
<SNIP>
> Command Line <> GUI.  My department wants a GUI that allows graphical
> browsing of the repository tree and the ability to check out individual
> files.  The ability to shell out and type commands by hand will
> underwhelm those whom I'm trying to convert to CVS.
> 
> Any other ideas?
> Phil
Phil,
Why do they want to check out individual files? (this might help us come up
with a better answer for you)
If you are looking for the users to know they are the only ones editing the
file try the cvs watch command, or for something closer to locks see Noel Yap's
RCVS patches.

The standard mode of operation, what cvs and its clients, expect is that the
developer will checkout either a directory structure or part of a directory
structure, each of which can be defined as a modules in the CVSROOT/modules
file.  Even when you checkout a single file with CVS it makes the directory
structure up to the file.  

I suppose that you could either put each file in it's own directory or setup
the modules file to point to a single file for each module, but to me and
probably others the question is WHY,  CVS was meant to let multiple developers
work on multiple files at one time.
http://www.cvshome.org/docs/manual/cvs_10.html#SEC83

-- 
I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb.  Thank you.
        -- Vance Petree, Virginia Power