Introduced new Creator-specific qmake variable QML_IMPORT_PATH that
lists the import paths required by the QmlJS engine.

Done-with: Alessandro Portale

QString::isNull() vs. isEmpty() discrimination is a time bomb ...

e.g. DEFINES+=bla on the qmakestep command line now work

Task-Nr: QTCREATORBUG-2091

Reviewed-by: dt <qtc-committer@nokia.com>

Patch by Jarek

Reviewed-by: dt <qtc-committer@nokia.com>

That is: a) Figure out a suitable default location for Add New on a
virtual folder.
b) If that default location is deployed, don't show a Add Existing Files
option, since that is confusing.

That is tell the user that those files need not be added to any project,
and show "<Implicitly Add>" for them on the last wizard page.
This fixes Add/New for the QML/OTHER_FILES folder structure, except for
the virtual folder itself.

Reviewed-By: Jarek Kobus <jaroslaw.kobus@nokia.com>

Qmake treats "." special, we need to do the same

Reviewed-by: dt <qtc-committer@nokia.com>
Task-number: QTCREATORBUG-125

Also only watch folders not files.
That also removes files that are directly listed in INSTALLS /
DEPLOYMENT, I'll readd them in a later commit.

That's a child of the .pri file for our new wizard. To be improved.

Some windows header have a define for DeleteFile.

Use the full path for folders to sort in the project tree.

For virtual folders ensure that the path ensures the sorting we want.

Reviewed-By: kkoehne

Qmake treats "." special, we need to do the same

when attempting to save a file under Perforce.

Reviewed-by: con
Task-number: QTCREATORBUG-1823

Reviewed-by: dt

Task-number: QTCREATORBUG-1631

we don't use anything the features may set up, so loading them just
wastes time. this may change if we start processing extracompilers
properly.

the message manager is not thread-safe, so don't use it outside the main
thread.

every path should be separator-fixed

Reviewed-by: dt

Extract qrc paths from ui file by simple xml parsing.

Reviewed-by: dt <qtc-committer@nokia.com>
Reviewed-by: Friedemann Kleint <qtc-committer@nokia.com>
Task-number: QTCREATORBUG-42

Task-Nr: QTCREATORBUG-1443

And refuse to add it twice. The check is pretty simplistic in that it
doesn't take scopes or which variable it's exactly in into account.
But in those cases you need to edit the .pro file manually anyway.

Task-Nr: QTCREATORBUG-932
Task-Nr: QTCREATORBUG-891
Task-Nr: QTCREATORBUG-653

That is e.g. SOURCES instead of whatever variable is used first in the
project file.

Reviewed-By: ossi

Task-Nr: QTCREATORBUG-765

Reviewed-By: con
Reviewed-By: Friedemann Kleint

We now support renaming files. The version control system tries first to
rename, if that doesn't support or can't rename the file we do a normal
rename. (Note: git, hg, perforce > 2009.02 support renaming, cvs not.
(perforce untested)). We correctly notify all editors of the renamed
file and tell the project manager to rename the file in the project.

Note: Only the qt4projectmanager knows how to rename files.

Note: renaming folders, moving files to different folders, renaming
.pro/.pri files is not supported. Those things can be later added after
this has proven to work correctly in the simple case.

Also we don't do any actions based on the renaming like renaming
classes, changing include guards or #include lines.

Symbian mkspec puts the package file into the build directory,
not the destination directory.

Task-Nr: QTCREATORBUG-1108
Task-Nr: TOOLS-339