>[ On Friday, February 18, 2000 at 17:38:32 (CST), Win32 M$ wrote: ]
>> Subject: About buttons....
>>
>> There is few more, but I think that will make the point. So, in fact, the
>> tool user would rather setup the options he wants to use, and he can forget
>> about all the troubles with Ver. Cntrl. The different approach is for the
>> tool maker - his job is to make a tool smart enought to do the right things
>> when the button is pressed. We are a tool makers in this forum, and we
>> should have some concern for the "users". We (toolmakers) know the mechanics
>> behind the tool, and we can use it even if it's broken or
>> difficult/complicated. But we should take care to make a life for the
>> "users" easier.
>
>Hmm.... perhaps you should take a long hard look at some other tools,
>such as Aegis and perhaps some commercial or semi-commercial tools too.
>
>> My point is that tools users will use the tools in a "smart" way, not the
>> "hard" way. Hard way is in use only in the special/emergency cases. It's a
>> shame that CVS is not integrating via SCC API or COM. There in an attempt to
>> do that thought, but so far it is stuck.
>
>You're in the wrong universe. There are no such APIs here.
Stuff and nonsense.
For starters, .cvsrc allows you to customize the behavior of the cvs
commands under *nix so that they have the desired default behavior.
Beyond that, there are a number of open source graphical front ends
to cvs, including WinCVS, jCVS, WebCVS, MacCVS, MacCVS Client and
MacCVS Pro. WinCVS, MacCVS Pro and MacCVS have integration of the
type described into the CodeWarrior environment under both Windows
and Macintosh.
I wrote the aforementioned MacCVS integration tool and I read this
list, so please don't presume to speak for me when you make
statements like "There are no such APIs here." There are such APIs
here provided by folks who are more interested in promoting cvs than
worshipping it. I also know for a fact that Alex Paterneau (WinCVS)
and Alberto Barbati (abCVS) read this list. The post you just
harshed on even mentions the effort to integrate cvs into MS
Developer Studio, which is discussed on this list from time to time.
If you can't say something useful, just shut up. And if you can't
shut up, at least have the decency to only speak for yourself and not
the entire community.
