project tree watcher interface plan

dukju ahn dukjuahn at gmail.com
Mon Jun 4 17:19:50 UTC 2007


2007/6/4, Matt Rogers <mattr at kde.org>:
>
> On Jun 4, 2007, at 9:43 AM, dukju ahn wrote:
>
> > Apart from the general wrapper around QFileSystemWatcher, what
> > I want to discuss here is specific project tree watcher which
> > targets project managers.
> >
> > Although we can use the general wrapper discussed, I think that
> > using general wrapper for project managers is duplication of memory
> > usages. The key to project manager tree watcher is that it should
> > stores
> > Project**Items for each watched path. And it can compare difference
> > using that project**items.
> >
> > So my plan is that the "general" wrapper around QFSWachter will not
> > be used for projecttreewatcher.
> >
> > Also, rather than emitting signal, my plan is that we have base class
> > named "projecttreewatcher", and provides virtual interfaces, because
> > we can provide some default implementations. Especially,
> > directoryCreated() and deleted() implementation would be common
> > among the project managers, since makefile parsing event will be
> > taken place in fileCreated() deleted() modified() method..
> >
> > Any objection?. I expect as before.
> Where's the code? I want to see some code before i'm comfortable with
> this.

Attached are full source. The 5 virtuals in ProjectFSWatcher is the thing
we will reimplement.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: watch.tar.gz
Type: application/x-gzip
Size: 4246 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20070604/f4cd0343/attachment.gz>


More information about the KDevelop-devel mailing list