Gathering the set of files-to-watch

[David Nolden]

The priority should be ok (isn't there a hint saying what the default
priority for auto-parsing is?).

As features, you should use "VisibleDeclarationsAndContexts", what you
picked is far too much. You don't need to care about other queued stuff, the
background parser does that.

Greetings, David

Am 12.06.2010 21:06 schrieb "Esben Mose Hansen" <kde at mosehansen.dk>:

On Wednesday 09 June 2010 22:23:39 Andreas Pakulat wrote:
> > so having done my initial study, I'm d...
[...]


> You can get at all files from a project from IProject::fileSet() and
> you get to all projects us...
Ok, so far so good. My patch watches the files added/removed to the fileSet,
and schedules a reparse whenever these files are changed. There are some
details left in this, but it basically works.

A few question:

1. What would be a suitable priority? From reading the docs, 0 seems to high
as I want these jobs to not interfere with the actively edited document, so
I've used "10", for no particular reason other than it is a lower priority.
2. What featureset is appropriate for updating "everything stored" for a
file
that was changed externally? I currently use
TopDUContext::AllDeclarationsContextsUsesAndAST .
3. Does backgroundparser check if there is already a queued job for a given
url, or should I do that myself?

My next item on the list is getting and watching the includes of a file. The
cleanup, and finally I'll submit it to the mercy of the core developers :)

--
Kind regards, Esben


-- 
KDevelop-devel mailing list
KDevelop-devel at kdevelop.org
https://barney.cs.uni-potsdam.de/mailma...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100612/9cb39374/attachment.html>