* Use Ui file
 * Add more tooltips to the tree widget

using the targetsetuppage.

Handle the deletion of temporary QtVersions properly. Remove
workaround.

Reviewed-by: dt

... so that we can sanity check.

Remove all hacks/conventions of considering the last generated
file as project file, etc. and instead add attributes flags to
Core::GeneratedFile, giving fine-grained control of what to do
with the file. Implement static utility functions in wizards
that handle it. Add boolean XML-attributes "openeditor"/"openproject"
to the file elements used by the CustomWizard XML-specification.
Manually set the attributes in all wizards.

Task-number: QTCREATORBUG-1166

Tasknumber: QTCREATORBUG-1148

Reviewed-by: dt

 * Remove PathChooser widget so that you need to use a proper dialog
   to select pathes. So typing into that PathChooser is no longer slow;-)

   The PathChooser does not provide a proper signal on when a user is done
   entering a directory, so it was not a good choice.

Tasknumber: QTCREATORBUG-1128
Reviewed-by: dt

Reviewed-by: dt

Reviewed-by: dt

If the same Qt version was imported twice then this was not
detected properly.

Reviewed-by: dt

* Fix a possible memleak while at it.

TaskNumber: QTCREATORBUG-1125
Reviewed-by: dt

Properly register Qt versions and do not delete them afterwards

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

It changed in dc197e74

Reviewed-by: Friedemann Kleint

This patch marks up invalid Qt versions as Desktop.

Make sure we add a the always existing invalid Qt version in the path
available in the targetselectionpage if no valid Qt versions could be found.

This way a project can be set up and loaded without a valid Qt version set up.
Trying to build this will fail of course. This is basically how we handled
this situation before we had targets, too.

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

Reviewed-by: Friedemann Kleint

As it has a special constructor and is rarely used.
Task-number: QTCREATORBUG-1025

 ... in the TargetSetupPage.

 Make sure that if there is only one thing we can check that it is checked.

Reviewed-by: dt

Reviewed-by: Roberto Raggi

 * Comment out TARGET.CAPABILITY in symbian section
 * Use += to append to already set capabilities instead of
   overwritting them.

 * This page differs from the targetspage as it supports
   importing of existing builds and will replace the
   targetspage in time.

Reviewed-by: dt

 * If we are building a mobility app:
    * Add MOBILITY api support
    * Add symbian specific stuff (UID3, etc)

Reviewed-by: aportale

 * Do not add menubars, etc. to mobile applications by default

Task-number: QTCREATORBUG-423

 * Expand all targets
 * Do not check any Qt flavour by default