[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PROPOSAL] cvs support in KDE (long)
From:       Christian Loose <christian.loose () hamburg ! de>
Date:       2003-01-19 17:35:16
[Download RAW message or body]

Am Freitag, 17. Januar 2003 19:19 schrieb Christian Loose:
> Am Freitag, 17. Januar 2003 13:54 schrieb Andras Mantia:
> > On 2003. January 17., Friday 14:15, Christian Loose wrote:
[snip]
>
> The CVS DCOP service consists of the following three parts:
>
> 1. CvsService - The main interface to the functionality of the CVS command
> line client. There is one method for each CVS command, e.g. add, checkout,
> commit, etc... The methods assemble the command line arguments, create a
> CvsJob and return a DCOPRef to the job. There is one instance of this
> service for each application instance.
>
> 2. Repository - This DCOPObject manages the configuration data of the
> current CVS repository like CVS_RSH or the compression level. The data is
> automatically updated when other service instances change it.
>
> 3. CvsJob - This class represents a cvs job. You can execute and cancel it,
> and you can retrieve the output of the CVS client by connecting to the
> proper DCOP signals. There are two types of jobs. First the non-concurrent
> job which has to run alone like update or import. Second the jobs which can
> run concurrently like log or annotate.
>
> Note: The DCOP service doesn't offer a GUI!
>
> Improvements, ideas, corrections are very welcome! Also do you think that a
> DCOP service is a good way to offer this functionality?
>
> Christian

*bump* :-)

Nobody has any opinions on this or different ideas? Or is everybody going 
through the sources of the cvsservice?

[prev in list] [next in list] [prev in thread] [next in thread]