startup sequence

[Milian Wolff]

On Friday 30 January 2015 17:18:15 René J.V. Bertin wrote:
> Hi,
> 
> I have the impression that when opening a session currently, KDevelop loads
> the session's different projects, and starts parsing each project as it is
> finished loading. If true, this increases the time required to load the
> other projects and thus the time before "one can get to work". With CMake
> projects being loaded through a non-killable background job, it also
> increases the time one has to wait in order to close the session cleanly if
> ever one misclicked (and during which on OS X >= 10.9 one better has to
> keep KDevelop the front application if one doesn't want to trigger what
> must be app nap flaws).
> 
> I think this approach could be improved by postponing the parsing start,
> which in turn could probably be done with some kind of trigger (semaphore)
> with which the parsing job could still be created immediately after a
> project has been loaded.
> 
> What do you think? How difficult would it be for someone not very well
> acquainted with kdevelop's internals to come up with a draft?

I think we should continue to parse stuff as soon as possible. Esp. in KF5, 
project loading is nearly instant, even with big CMake projects. I have never 
encountered any issues with load times being bad b/c the parse jobs have 
started, but then again maybe I don't have as bad hardware as you.

Anyhow, try out KF5 kdevelop and see for yourself. Lets rather optimize code 
than trying to "improve" stuff by adding unnecessary latencies.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de