- 10 Jan, 2011 1 commit
-
-
Friedemann Kleint authored
-
- 07 Jan, 2011 2 commits
- 17 Dec, 2010 1 commit
-
-
con authored
-
- 02 Dec, 2010 1 commit
-
-
hjk authored
-
- 29 Nov, 2010 1 commit
-
-
Kai Koehne authored
Task-number: QTCREATORBUG-2600
-
- 17 Nov, 2010 1 commit
-
-
Oswald Buddenhagen authored
get away from argument stringlists. instead, use native shell command lines which support quoting/splitting, environment variable expansion and redirections with well-understood semantics. Task-number: QTCREATORBUG-542 Task-number: QTCREATORBUG-1564
-
- 12 Nov, 2010 1 commit
-
-
dt authored
Since all the debuggers are implemented in the debuggerplugin, that's a natural place to put the action.
-
- 10 Nov, 2010 1 commit
-
-
hjk authored
There's some 'external' and some 'internal' part now. Other plugins are only supposed the external interface.
-
- 01 Nov, 2010 1 commit
-
-
Friedemann Kleint authored
Acked-By: dt
-
- 26 Oct, 2010 2 commits
-
-
Friedemann Kleint authored
Set complete build environment (MinGW). Reviewed-by:
Christian Kamm <christian.d.kamm@nokia.com> Reviewed-by:
Kai Koehne <kai.koehne@nokia.com> Task-number: QTCREATORBUG-2883 (cherry picked from commit f1fb0bdd)
-
Friedemann Kleint authored
Set complete build environment (MinGW). Reviewed-by:
Christian Kamm <christian.d.kamm@nokia.com> Reviewed-by:
Kai Koehne <kai.koehne@nokia.com> Task-number: QTCREATORBUG-2883
-
- 11 Oct, 2010 1 commit
-
-
Pawel Polanski authored
Reviewed-by: Friedemann Kleint
-
- 05 Oct, 2010 1 commit
-
-
Kai Koehne authored
QmlObserver right now requires 4.7.1 minimum. There's no gain in telling the user that he needs qmlobserver to debug, if it can't be build with 4.7.0 anyway. Reviewed-by: Christiaan Janssen
-
- 04 Oct, 2010 2 commits
-
-
Kai Koehne authored
Also only warn about missing qmlobserver when actually trying to debug a .qmlproject. Reviewed-by: Christiaan Janssen
-
Kai Koehne authored
Task-number: QTCREATORBUG-2501
-
- 29 Sep, 2010 1 commit
-
-
Lasse Holmstedt authored
Reviewed-by: hjk
-
- 23 Sep, 2010 1 commit
-
-
Tobias Hunger authored
Reviewed-by: dt
-
- 20 Sep, 2010 1 commit
-
-
Lasse Holmstedt authored
Adapt to latest changes in qt.git (commit a9e5329168c) Reviewed-by: kkoehne
-
- 03 Sep, 2010 1 commit
-
-
Kai Koehne authored
Reviewed-by: dt
-
- 02 Sep, 2010 1 commit
-
-
Lasse Holmstedt authored
-
- 24 Aug, 2010 2 commits
-
-
Lasse Holmstedt authored
Reviewed-by: hjk
-
Lasse Holmstedt authored
A new debugger engine, QmlCppEngine, is introduced, which wraps gdb and qml engines into one. Alternatively, if using Windows, Cdb is used instead of Gdb. Most of the debugger ui switcher is now rewritten, and it is tailored for the QML and CPP layout case, the only one supported anyway. Reviewed-by: hjk
-
- 20 Aug, 2010 1 commit
-
-
Friedemann Kleint authored
Fix breakage introduced by the new asynchronous stop() methods of the debugger run controls. Allow for RunControl::stop() to be asynchronous by introducing a return enumeration indicating that. Introduce additional method aboutToStop() asking user to quit (tie that to the RunControl instead of having to hack the behaviour elsewhere). If asynchronous stop is detected, terminate the ProjectExplorer asynchronously. This makes the behaviour consistent across switching sessions/ closing outputwindow tabs and quitting Qt Creator. Reviewed-by: dt Rubber-stamped-by: hjk
-
- 13 Aug, 2010 1 commit
-
-
Lasse Holmstedt authored
Now, QmlEngine creates the connection to the inferior (debuggee), and notifies QmlInspector when a connection is established. Before, inspector created the debugger engin, which was wrong. QmlEngine's responsibilities are connecting to the debuggee and basic QML/JS debugging features like locals & watchers, breakpoints etc. QmlInspector takes care of Live Preview and other fancy inspection features. Reviewed-by: hjk
-
- 06 Aug, 2010 1 commit
-
-
Friedemann Kleint authored
-
- 29 Jul, 2010 1 commit
-
-
Lasse Holmstedt authored
Reviewed-by: Thomas Hartmann
-
- 14 Jul, 2010 2 commits
-
-
Lasse Holmstedt authored
-
dt authored
Move link handling code to outputwindow from OutputFormatter Move createOutputFormatter to the RunConfiguration That makes it easier for Qt4RunConfiguration et all. This also fixes that each time a runcontrol was rerun a new OutputFormatter was created without deleting the old one, thus increasing the memory usage.
-
- 08 Jul, 2010 1 commit
-
-
Lasse Holmstedt authored
-
- 28 Jun, 2010 2 commits
-
-
Roberto Raggi authored
-
Roberto Raggi authored
-
- 03 May, 2010 1 commit
-
-
dt authored
And use it to implement changing the run icon in the application output. That implementation does only support the two run modes run and debug for now. Further abstraction for more run modes to be done once needed. Task-Nr: QTCREATORBUG-1232
-
- 19 Apr, 2010 3 commits
-
-
Erik Verbruggen authored
-
Erik Verbruggen authored
So now the "Applciation Output" can distinguish between these four, and handle them appropriately.
-
Erik Verbruggen authored
By introducing the OutputFormatter, RunControls can influence the formatting depening on the application started. A nice (and intended) side-effect is that the QML runtime specific formatting will not interfere anymore with anything else.
-
- 16 Apr, 2010 1 commit
-
-
Thorbjørn Lindeijer authored
Renamed RunConfiguration::configurationWidget to createConfigurationWidget. Reviewed-by: dt
-
- 15 Apr, 2010 1 commit
-
-
Lasse Holmstedt authored
It's not yet possible to attach to an external app running a qml debugging server, because the server is only started on startup if an env variable is set. Changing this requires action from Brisbane, but even the current solution works for C++ apps with QML in them. Task-number: BAUHAUS-585 Reviewed-by: dt
-
- 18 Mar, 2010 1 commit
-
-
Lasse Holmstedt authored
-
- 05 Mar, 2010 1 commit
-
-
hjk authored
-