* If the qmake path does match then the target does match, too.

 * Do not use the BuildManager but have the qmakestep trigger
   the update via the target and project.

Reviewed-by: dt

 * Initialize it to the toolchain used, not the preferred one

 * Update the import label (and related stuff) whenever the
   project was rebuild.

 * Ease cross device development by introducing 'targets' which
   group build- and runsettings that are valid for this one target

 Most of the kudos for the code review go to dt. Con, thorbjorn,
 ckandler and others did also review parts of this patch.

Reviewed-by: dt

Reviewed-by: dt

Instead note that it is invalid if trying to build and on the projects
mode pane.

Task-Nr: QTCREATORBUG-459

  * Use id() for methods returning a string used to represent
    some type of object.
  * Use displayName() for strings that are meant to be user
    visible.
  * Quieten some warnings while touching the files anyway.
  * Move Factories to their products in the plugins where that
    was not done before.

Reviewed-by: dt

Resetting the cursor to the end of line and resetting the line edit on
changing the shadow build checkbox

Should fix a lot of corner cases, might introduce a few bugs.
Also rename functions/slots to be better named.

Generic Project Manager and CMake Project Manager are missing from this
patch.

Also rename some methods/signal to make clearer that those only are
relevevant for user changes not for all arguments.

Fix for that will come later

Note: I didn't fix all the connects and there are a few missing things.
This compiles, more work is coming.

The pointers can be used to distinguish BuildConfigurations

Each project has it's own BuildConfiguarion * classes, they'll get a
decent type safe interface and the setValue/value stuff will be removed.

Separate category and trCategory and introduce sorting characters
to the categories. Same for id/name.

Enables users to change which buildsteps get run per buildconfiguration.
Some further tweaks are probably necessary. This is a rather big
change, though it should work. :)

Also ensure that Qt4ProjectConfigWidget does not emit any signals from
it's init method.

That is we actually parse the mkspec and evaluate QMAKE_CXX (and a few
other variables) to figure out the correct mkspec. This makes using
custom mkspecs easier and is also cleaner. I also changed mkspec() and
mkspecPath() to behave a little diffrent, essentialy mkspec() will
return only the name (the actual dir name) of the mkspec. That is in
general not sufficient for passing on to qmake. mkspecPath() only
returns the correct path to mkspecs/default.
Hopefully I haven't broken WinCE/Maemo/MinGW.

Also move Designer::Internal::FormWindowEditor ->
Designer::FormWindowEditor.