from Menu entry

Don't show the icon of checkable items in the menu to avoid being
affected by broken styles.

Task-number: QTCREATORBUG-1173

Reviewed-by: Thorbjørn Lindeijer
Task-number: QTCREATORBUG-865

 - lessens open file handles
 - improves help plugin startup further

Task-number: QTCREATORBUG-337
Reviewed-by: ck

Task-number: QTCREATORBUG-1621
Reviewed-by: ck

Reviewed-by: kh1

Reviewed-by: hjk

This is improving the updating.

Reviewed-by: Marco Bubke
Task-id: QTCREATORBUG-1493

This is needed to suppert inline script function of Qml in the designer

raw strings would break things due to the missing null terminator. this
did not affect unix, as there we convert to 8 bit anyway.

Task-number: QTCREATORBUG-1364

Fixes breakage introduced by 34982c1f.
Task-number: QTCREATORBUG-1612
Reviewed-by: dt

Fixes a crash when drag&dropping e.g. the WebView element to a file
which doesn't already import the org.webkit package.

Enable correct handling of imports again.
This reverts commit de610cac.

E.g. if the type of the node is 'Qt/Image', version 4, 6, search through
the list of imports to find 'Qt'. If an alias for the namespace has been
defined, prepend this to the element name.

Reviewed-by: Erik Verbruggen

Task-number: BAUHAUS-602
Reviewed-by: Erik Verbruggen

The order of imports does matter, therefore it should also be
represented as a list in the model.

Reviewed-by: Marco Bubke

Task-Nr: QTCREATORBUG-1593

Task-number: BAUHAUS-780
Reviewed-by: kkoehne

 * Fix displayed shadow build location
 * Fix shadow build location used by newly set up shadow builds

Task-number: QTCREATORBUG-1599
Reviewed-by: dt
(cherry picked from commit 1d8e1760)

The heuristics to find the file to run and the logic that decides
whether the show / debug button is shown weren't in sync. Also, don't
try to run .qmlproject files if open in the editor.

Reviewed-by: Lasse Holmstedt

On the project page isn't much information for the end user.

Task-number: QTCREATORBUG-1609

Pointed out by static code analysis.

Just disable them, but preserve them. This is different from qmake, but
for qmake we do have different assumptions what a buildconfiguration is.

Task-Nr: QTCREATORBUG-1591

Reviewed-by: Friedemann Kleint

use local8bit instead of latin1 resp. 8bit-passthrough, after all.

the situation was as follows:
- if the pro files and file names were all ascii, everything just worked
- if either contained non-ascii:
  - on unix, the evaluator would work as long as the file content
    encoding matched the file name encoding, and the ui would work as
    long as the file name encoding was latin1 (i.e., on no modern
    system)
  - on windows, both would work only if the ansi code page was
    latin1/cp1252 (i.e., on western systems)

i.e., even in the low-level evaluator, only native latin1 systems with
actual latin1 files worked consistently. given this situation, it makes
little sense to make an encoding adapter between the evaluator and the
ui as originally planned. instead, take the easy way out and use
local8bit - this continues to work for native latin1 systems+files in
the backend, and makes the ui work for everything the backend groks and
some more.

Reviewed-by: dt
Task-number: QTCREATORBUG-930

every path should be separator-fixed

Reviewed-by: dt