project tree watcher interface plan

dukju ahn dukjuahn at gmail.com
Mon Jun 4 14:43:46 UTC 2007


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.




More information about the KDevelop-devel mailing list