One less need for qmakestep.

Task-Nr: 257765

Hides the gory details, and in most cases the user doesn't care anyway.

It may be that a non-default Qt version provides documentation even if
the default one does not.

Fixes: 257970

Only connect in restoreSettingsImpl() not in the constructor.

Not finished 100%

Requires a lot of trivial forwarding.

Specially for FakeVim users out there who want an easy way to switch to
vim's default color theme on a dark brackground.

Also did a little cleanup.

Since that method actually checks if Qt is built 64bit,
not if MSVC is 64bit.

Create a new one and check if it's the same as the old one,
has the advantage that cached data doesn't need to be retrieved again.
It was that way before tool chain was moved to Qt4Project.

There were both variants, with and without extra semicolon.

Bug was introduced when separating the version list into "Autodetected" and
"Manual" subtrees.

this also removes the bogus special casing of various
filename-containing variables inside the pro parser.

A project's existing .pro file could be added to the project, making
the .pro file appear twice in the project tree. This is sub-optimal
because

1. It does not make sense for the .pro file to appear twice.
2. Qt Creator crashes when trying to remove either of the duplicate
.pro files.

Added translation macros to some editor kinds.
Added possibility to translate names of editors in Open With context menu. Translation context is "OpenWith::Editors".

Merge-request: 808
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

E.g. cmake pops up a wizard then, the running of cmake can fail though.
Now you don't end i[ with a empty project then. The error reporting in
that case is not yet optimal.

Make Gui app wizard use Qt Designer wizard code to write the classes.
Remove the settings from the form class wizard page extension area and
add a settings page instead. Polish the designer plugin's structs to
parametrize class generation with QSharedData and settings code.
Export them and use them in the Gui app wizard.

Task-number: 256927

Cannot put a source file template into a resource in a source directory
as Visual Studio will grab and build it.

This is a fix for a446491a.
The option debug_and_release determines whether the debug/ and release/
subdirectories are used to put *object* files there. The option
debug_and_release_target is used to put the final taget into debug/
and release/ directories.

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

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

Add the wizard. Modify basefilewizard to use be able to handle binary
data. Add some properties to path chooser (filters).

Task-number: 251982
Initial-patch-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

Indexing both /include/Qt and /include/{QtCore,QtGui,...} makes the code completion with fedora.

Don't crash then

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

Tool chain type is saved in settings, make sure that the value doesn't
change between S60 enabled/disabled Qt Creator version.
Run configurations can change independent from the run settings
property page, re-add handling of signals.
Add some things to consider to the todo list.

Reviewed-by: dt

And if Qt version changed.

Transform the method in Qt4Project into a signal that is handled
by the run configurations themselves.

Not able to give it an additional passphrase yet, though.