Results of review.

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

1 files changed, 15 insertions, 1 deletions

diff --git a/src/plugins/qt4projectmanager/qt-s60/qt-s60-todo.txt b/src/plugins/qt4projectmanager/qt-s60/qt-s60-todo.txt
index 38a01bdbb7..c399e28437 100644
--- a/src/plugins/qt4projectmanager/qt-s60/qt-s60-todo.txt
+++ b/src/plugins/qt4projectmanager/qt-s60/qt-s60-todo.txt
@@ -12,15 +12,29 @@
 * Debugging helpers
     * must probably be compiled for different toolchains
 
+* Tool chains
+    * derive GCCE tool chain from GCC toolchain to get the includes/defines
+      implementation
+    * delete toolchain in more intelligent way (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)
+    * Qt4Project::setQtVersion should think about tool chains,
+      might be better to remove the magic in toolChainType method
+    * should the default make target be defined by the project
+      instead of tool chain, or perhaps by the QtVersion dependent on a
+      tool chain?
+
 * Run Configurations
     * handling of active run config getting disabled not optimal yet
+    * might be better from a user perspective if the run configuration
+      defines possible tool chains
 
 * Run on device
     * makesis, signsis and applicationinstaller don't report errors back
       via exit code :-(
     * passphrase for signing
 
-* Add compile output parser winscw at least!
+* Add compile output parser winscw at least
 
 * WINSCW tool chain:
     * predefined macros