GitLab

Reviewed-by: kh1

Reviewed-by: ck

- Remove ListView by ComboBox. Uses less space
- Ports are now spinboxes, to allow for better input validation

Reviewed-by: ck

Task-number: QTCREATORBUG-1074
Reviewed-by: kh1

Task-number: QTCREATORBUG-1073

Fixes a crash introduced with the mentioned revision, since one can only
have a single instance of the ne7ssh object. Poroper fix follows next.

Reviewed-by: ck

--[ Details ]---------[ remember extra blank line after subject ]---|

(No actual functionality yet.)

Reviewed-by: kh1

Reviewed-by: kh1

Since the ne7ssh implementation starts the select thread directly inside
the constructor, we would have it polling after initializing the project
manager. Still we should apply the fix Thiago proposed for polling.

Reviewed-by: ck

Some categories do not have icons yet, unfortunately.

Reviewed-by: kh1

... use it.

Reviewed-by: dt

Reduces the minimum size of the Options dialog.

Reviewed-by: kh1

Reviewed-by: kh1

This is a big change touching almost all of our .pro file parsing.
With this patch we only evaluate once exact for all needs and once
greedy for the filelist. That is the qt runconfigurations don't have own
evaluaters but reuse the project wide exact evaluation.

We reevaluate if the user changes the build directory, the qmake
buildconfiguration or the qmake arguments. That is if you open src.pro
(or projects.pro) of qt with a shadow build you still don't get all the
files, but after correcting the build directory, we reevaluate the .pro
files and find all files. So for a suitable definition of fixed, that
bug is now fixed.

We now get the exact defines of all .pro files instead of all defines for all
buildconfigurations. We still don't distinguish in which
.pro file a DEFINE is set. So the code model now knows about all the
defines set for the given configuration but not for which files it is
actually set. Also that includes all DEFINES set in .qmake.cache or the
mkspecs. This means all defines from .pro files should now work.

The intial loading is still synchronous. I haven't looked into it to
deeply, but it seems possible to make it also async.There are probably a
few issues which need to be solved fist.

Also due to the asynchronous nature of the code, the executable is
updated a few seconds after actually changing the build configuration

Reviewed-by: kh1

Reviewed-by: kh1

Reviewed-by: ck

Functionality depends entirely on the active start-up project, all other
projects should have the the button disabled if they have no Maemo run
config or the the run config is not the active on.

Reviewed-by: ck

 * kh1 says there is no such thing as there is no technical
   destinction between Maemo devices and the Maemo emulator.

Reviewed-by: kh1

Reviewed-by: Thorbjorn