[RFC] Workingstyle of different VCS systems

[Andreas Pakulat]

On 12.04.07 23:11:16, Andras Mantia wrote:
> On Thursday 12 April 2007, Matthew Woehlke wrote:
> > Andras Mantia wrote:
> > >> log - Show a complete history for a given local resource or VCS
> > >
> > > I don't see why we need this in the interface, it should be enough
> > > to have in the GUI.
> >
> > I guess the objective is to not need a separate GUI 99% of the time.
> 
> Separate GUI? It will be provided by the plugin.

You seem to have missed some mails in the thread. We want to provide
some widgets that can be shared among vcs plugins, like a  logviewer a
diff-tool and a merge tool for example. That way we have a unified GUI
for all these things, we reduce code duplication and take some burden
from plugin developers.

> > Anyway since the ideal is to be able to write an abstract GUI using
> > these interfaces, we still need it in the interface. :-)
> 
> Do we want such a GUI? I mean, will the plugins only do backend stuff 
> and not plug their actions into the user interface and instead we have 
> another plugin for the GUI? It doesn't really make sense because of the 
> differences between the VCS variants.

No, what we want is some widgets that can be used by the VCS plugins and
thus share some code. CVS and SVN can share log, diff and merge widgets
at least and I think perforce can do with those too.

> > Hmm, be sure to add your weight to the discussion going on in
> > kwrite-devel on this topic, then (you can CC here, I've been doing so
> > on some of the posts but most respondents aren't). I didn't mention
> > an onOpen signal as I didn't know of a need for one.
> 
> This has little to do with kwrite-devel (and KTextEditor). The framework 
> *knows* when a file is opened, right? Possibly knows also when it is 
> closed or saved. It is the KDevelop platform which needs to emit the 
> signals at the correct time.

I'm not sure the framework knows when the user pressed save, but if we
do than thats right.

-- 
Chicken Little only has to be right once.