184 lines
3.2 KiB
HTML
184 lines
3.2 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Using GUI Tools</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="CVS Best Practices"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Focus Areas"
|
|
HREF="section1-focusareas.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Developer Sandbox"
|
|
HREF="section1-devsandbox.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>CVS Best Practices</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="section1-focusareas.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="section1-devsandbox.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="section1-guitools"
|
|
></A
|
|
>3. Using <SPAN
|
|
CLASS="acronym"
|
|
>GUI</SPAN
|
|
> Tools</H1
|
|
><P
|
|
>The traditional interface available for CVS is the command-line client.
|
|
There has also been a slew of GUI client applications that can
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"talk"</SPAN
|
|
> to a CVS server. These GUI clients provide a
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"point and click"</SPAN
|
|
> interface to the CVS repository.
|
|
</P
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="section2-useguiclient"
|
|
></A
|
|
>3.1. Use GUI CVS client</H2
|
|
><P
|
|
> This paper recommends using such GUI clients during the initial
|
|
deployment of CVS in an organization.</P
|
|
><P
|
|
>Developers typically use integrated development environments that have
|
|
the CM tools integrated into them. These tools minimize the learning for the
|
|
developers about the intricacies of CVS usage and instead allow them to be
|
|
productive from day one. Developers who are accustomed to other CM tools will
|
|
find the CVS command-line interface daunting. The adoption and usage of
|
|
CVS can be improved by using GUI tools for CVS clients. </P
|
|
><P
|
|
> GUI tools for CVS are available at <A
|
|
HREF="http://cvsgui.sourceforge.net/"
|
|
TARGET="_top"
|
|
>http://cvsgui.sourceforge.net/</A
|
|
>.
|
|
GUI interfaces are available for most of the popular platforms (Windows, Mac
|
|
and Linux). In addition, on the Windows platform there is an
|
|
<SPAN
|
|
CLASS="acronym"
|
|
>SCC</SPAN
|
|
> extension that allows integration of CVS as the
|
|
configuration control tool with popular IDE.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="section1-focusareas.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="section1-devsandbox.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Focus Areas</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Developer Sandbox</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |