project tree watcher interface plan

[Andreas Pakulat]

On 05.06.07 14:59:41, dukju ahn wrote:
> 2007/6/5, Andreas Pakulat <apaku at gmx.de>:
> > On 05.06.07 12:31:01, dukju ahn wrote:
> > > 2007/6/5, Matt Rogers <mattr at kde.org>:
> > > > On Tuesday 05 June 2007 00:24, dukju ahn wrote:
> > > > > > Why does each build manager need its own file system watcher?
> > > > >
> > > > > Because when filesystem are changed, appropriate actions should
> > > > > be taken by project manager again. For ex, if new directory which
> > > > > contains Makefile is copied, the manager should parse() it again.
> > > > > So each manager just reimplement the virtual method.
> > > > >
> > > >
> > > > You misunderstand. I ask why each manager requires it's own file watcher
> > > > class, when it's not needed. Handling these FS notifications can be done in a
> > > > build manager specific way with just signals and slots , or by having the
> > > > build manager implement an interface. Or even better, just have the build
> > > > manager do its own thing with regard to file system watching.
> > >
> > > What is build manager you mentioned? Is it different from project manager?
> >
> > Yes.
> 
> > > I'm confused by the terms.
> >
> > Then please look at our API's. The Build Manager is the component that
> > manages the buildsystem files of the projects. The project manager is an
> > integral part of the shell and manages the various projects (it doesn't
> > know about buildsystems and so on).
> 
> So Build Manager refers to IBuildSystemManager subclasses and project
> manager consists of ProjectController and something like that. Am I right?

Exactly. Also I normally don't talk about project manager, only project
controller to help not confuse these things. Additionally to build
manager we also have an project-file-manager interface, when there's no
buildsystem.

Andreas

-- 
You need no longer worry about the future.  This time tomorrow you'll be dead.