Help offered

[Andreas Pakulat]

On 26.02.09 00:54:58, Lior Mualem wrote:
> On Wed, Feb 25, 2009 at 5:43 PM, David Nolden <
> david.nolden.kdevelop at art-master.de> wrote:
> 
> > One more thing about the parsing-progress:
> > Don't you see the progres-bar at the bottom? Although in my opinion, even
> > this
> > progress-bar can be annoying sometimes, because it really is no interesting
> > information for the user, and disturbs the work. So it should be hidden by
> > default, maybe just with a little indicator that "something" is happening,
> > similar to KMail, maybe with the possibility to expand it to see the full
> > progress.
> 
> I can see the progress bar below - and you're right that for normal editing,
> it's quite annoying, to see it pops constantly.
> I was talking about when parsing a new file or when a project loads and
> we're parsing the entire project.
> What comes to mind is the visual assist way of showing the progress report,
> it performs background parsing for the entire project and updates the
> progressbar below with the current file being parsed.
> As a "normal" user - the one that uses KMail, I assume that such information
> is useless and annoying but for a developer which is the primary audience
> for KDevelop, such information is nice to have. I love having stuff that
> simply "work" but I also like to know what happens in the background - where
> do we currently stand with parsing of my project - but this is really a
> "nice to have" feature.

Well, you know where you stand with the project (or even all the
projects) by looking at the percentage of the bar thats already filled.
And having the filename wouldn't help you as the list of files is
totally unordered, so path/fo/bar.cpp might be long before or long after
path/fo/boo.cpp.

> This also leads me to something else, probably off-topic a little bit - When
> checking the flag to parse the entire project, you'd expect that files that
> I currently inspect will get a boost and will be parsed first, before it
> continues to parse the entire project.

I think David had implemented support for that already, but as parsing
happens in n threads ultimately the kernel decides which one is finished
first. And of course it also depends on how many includes the current
file has. But the already opened files are (AFAIK) scheduled first for
parsing - at least I remember some commits related to that.

Andreas

-- 
You will be Told about it Tomorrow.  Go Home and Prepare Thyself.