Re: VCS interfaces draft

> > I'd say lib/interfaces
> Uhm, you sure? Until now it doesn't contain any
extension interfaces, so
> I guess its rather plugins/vcs/interfaces (and later
have vcs/cvs and
> vcs/svn with the 2 default implementations).
Yeah, you're right.

> > Speaking about version control,  what is the
future of
> > KDevVCSIntegrator's that were used by appwizard in
kdev3 to create
> > projects in repositories?
>
> I think it should use the extensions interfaces to get
a list of plugins
> for vcs ext iface and then use their import method. So
some
> vcsintegrator class that encapsulates is not needed, we
have extension
> interfaces for that.

Well, once we have import() in IVersionControl, we don't
need integrators.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 23.03.07 01:02:52, Alexander Dymo wrote:
> > > Speaking about version control,  what is the
future of
> > > KDevVCSIntegrator's that were used by
appwizard in kdev3 to create
> > > projects in repositories?
> >
> > I think it should use the extensions interfaces to
get a list of plugins
> > for vcs ext iface and then use their import
method. So some
> > vcsintegrator class that encapsulates is not
needed, we have extension
> > interfaces for that.
> 
> Well, once we have import() in IVersionControl, we
don't need integrators.

Yeah, and not only appwizard needs this, think a local
project that
needs to be imported into version control (also called
team->share
project in eclipse).

Andreas

-- 
The time is right to make new friends.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel