Using more *::Constants::ICON_* where it makes sense and
wrapping the file names into QLatin1String where they were
missing.
The increased usage of the ICON constants needed a few more
cross plugin includes of *constants.h, here and there.
I think that it is OK, since the dependencies were alredy there
icon resource wise.
If a plugin requests asyncronous shutdown, the shutdown sequence does
not continue to deleting the plugins before it has sent a
asynchronousShutdownFinished signal. During that time an event loop
is running.
If we where not in full help mode at least once, the engine
would still run without valid help collection due to the new
lazy initialisation, thus the right side pane would not be
able to retrieve the requested help file.
Reviewed-by: ck
If we where not in full help mode at least once, the engine
would still run without valid help collection due to the new
lazy initialisation, thus the right side pane would not be
able to retrieve the requested help file.
Reviewed-by: ck
When changing the language, the sidebar items would break because
their localized window titles were used for storing the settings. Now,
id's are used.
Reviewed-by: con
To make the addition of the qml docs more prominent, make the content
item the default one as it shows all available documentation sets.
Task-number: QTCREATORBUG-1024
Reviewed-by: kkoehne
We now do as much as possible lazy initialisation, e.g only start the
full text search indexer if we really access the search widget. Also
moved the QFutur progress into the search widget. Changed all ctors to
be called without an argument, since we share the help engines from
help manager all over the place. Make use of the fact that we only need
to call setupData on the gui engine if we access the help mode, otherwise
all data is fetched thru the core engine whichs setupData is really fast.
Currently we can only retrieve a list of keywords from the help index
model, which is slow and needs a fully setup gui help engine. This needs
to be implmeneted in the help lib though.
Reuse the core help engine in the settings pages. Do not setup the gui
help engine at all since any getter will do so. Split update documentation
into smaller pieces for better performance.
Reviewed-by: ck
