Make the check more generic, to also work for all other Qt namespaces
than qt.ver.s.ion. Still there's something broken in Qt webkit or so.
Reviewed-by: ck
In the GTK style the scroll bar likes to be outside of the scroll area
frame. Like with the completion widget, we put the visible frame
explicitly outside of the scroll bar.
Reviewed-by: Jens Bache-Wiig
It looks wrong when a shadow is added, which a lot of window managers do
these days. Whether is looks better when no shadow is added by the
window manager is debatable.
Reviewed-by: Jens Bache-Wiig
The links have been taken before from the model, now we need to get
them out of the help files, since the help eninge core does not provide
(yet) such functionality. Also return a sensible amount of hits for the
first character, limited for now to 300 for speed reasons.
Reviewed-by: ck
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
Both implementations are now split into two source files, based on the
base class type. They share also a commen implementation, but the class
interface looks now clean to the outside. Adopt other classes for use.
Since we use a two column model/treeview we need to prevent returning
some text data, otherwise we will see dots in the secound column. We also
need to emit pagesChanged once we init the model.
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
