- Jan 13, 2011
-
-
Tobias Hunger authored
* Move the environment model code to utils and export it * rename the environmenteditmodel files to environmentwidget (which is the class they actually contain) Reviewed-by: dt
-
- Jan 12, 2011
- Dec 17, 2010
-
-
con authored
-
- Nov 17, 2010
-
-
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
-
- Nov 01, 2010
-
-
Friedemann Kleint authored
Acked-By: dt
-
- Sep 27, 2010
- Sep 23, 2010
-
-
Tobias Hunger authored
Reviewed-by: dt
-
- Sep 03, 2010
-
-
Kai Koehne authored
Reviewed-by: dt
-
- Sep 01, 2010
-
-
Lasse Holmstedt authored
-
Lasse Holmstedt authored
There's a UI in qml/customexec/cmake/qmake run configs for choosing the debugger languages (C++ and QML). The default for all except .qmlproject is only C++, so default debugging behavior is the same. However, if the user wants to do simultaneous debugging with two languages, or only debug QML, they can select the languages from Run Settings and it will be remembered. Reviewed-by: hunger
-
- Aug 27, 2010
-
-
Tobias Hunger authored
* Fix all warnings about non-explicit constructors except for those in 3rdparty code.
-
- Aug 24, 2010
-
-
Tobias Hunger authored
* Enable support for this in all ProjectConfiguration items (Targets, projects, BCs, DCs, RCs, etc.). This is nicer than having custom code in individual configuraiton items. Reviewed-by: dt
-
- Jun 09, 2010
-
-
dt authored
Just disable them, but preserve them. This is different from qmake, but for qmake we do have different assumptions what a buildconfiguration is. Task-Nr: QTCREATORBUG-1591
-
- Apr 16, 2010
-
-
Thorbjørn Lindeijer authored
Renamed RunConfiguration::configurationWidget to createConfigurationWidget. Reviewed-by: dt
-
- Mar 05, 2010
-
-
hjk authored
-
- Feb 09, 2010
-
-
Tobias Hunger authored
* 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
-
- Feb 02, 2010
-
-
Tobias Hunger authored
This is in preparation of the addition of "targets" in the sense of "platforms to develop for" into the codebase. Reviewed-by: dt
-
- Feb 01, 2010
-
-
con authored
Reviewed-by: dt
-
Tobias Hunger authored
Reviewed-by: dt
-
- Jan 07, 2010
-
-
Tobias Hunger authored
* 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
-
- Dec 14, 2009
-
-
dt authored
Task-Nr: QTCREATORBUG-277
-
- Dec 07, 2009
-
-
dt authored
Otherwise we need to parse the cbp file, which happens only if the buildconfiguration gets active. Also try to decouple a few internals a little bit by using signals. The CMakeProject still handles a few things directly instead of via signals, more to come eventually.
-
- Nov 30, 2009
-
-
dt authored
-
- Nov 19, 2009
-
-
dt authored
-
- Oct 05, 2009
-
-
Friedemann Kleint authored
Also move Designer::Internal::FormWindowEditor -> Designer::FormWindowEditor.
-
- Oct 01, 2009
-
-
dt authored
-
- Sep 25, 2009
-
-
Friedemann Kleint authored
and ApplicationRunConfiguration to LocalApplicationRunConfiguration, preparing remote debugging. Change the interface canRun() to be const, run() to create() (since it does not run anything), use references to the QSharedPointer<Foo>. Introduce d-Pointer and remove unneeded headers from ProjectExplorerPlugin and add missing includes everywhere.
-
- Sep 17, 2009
-
-
dt authored
This splits up the edit and active settings. Let people try it and report usability problems. I'm not 100% convinced of the layout either.
-
- Aug 14, 2009
-
-
hjk authored
-
- Jul 20, 2009
-
-
dt authored
Hides the gory details, and in most cases the user doesn't care anyway.
-
- Jul 15, 2009
-
-
dt authored
Requires a lot of trivial forwarding.
-
- Jul 14, 2009
-
-
Adriaan de Groot authored
-
- Jun 17, 2009
-
-
dt authored
Best effort only though. This can make detection in the debugger which engine should be used easier. Task-Nr: 256161
-
- Jun 16, 2009
-
-
dt authored
Task-Nr: 254424
-
con authored
Reviewed-by: Trust Me Conflicts: src/libs/cplusplus/CppBindings.cpp src/libs/cplusplus/CppBindings.h src/libs/cplusplus/FastPreprocessor.cpp src/libs/cplusplus/FastPreprocessor.h src/plugins/cpptools/cppcurrentdocumentfilter.cpp src/plugins/cpptools/cppcurrentdocumentfilter.h src/plugins/cpptools/cppsemanticsearch.cpp src/plugins/cpptools/cppsemanticsearch.h src/plugins/duieditor/parser/qmljs.g src/plugins/duieditor/parser/qmljsast.cpp src/plugins/duieditor/parser/qmljsast_p.h src/plugins/duieditor/parser/qmljsastfwd_p.h src/plugins/duieditor/parser/qmljsastvisitor.cpp src/plugins/duieditor/parser/qmljsastvisitor_p.h src/plugins/duieditor/parser/qmljsengine_p.cpp src/plugins/duieditor/parser/qmljsengine_p.h src/plugins/duieditor/parser/qmljsgrammar.cpp src/plugins/duieditor/parser/qmljsgrammar_p.h src/plugins/duieditor/parser/qmljslexer.cpp src/plugins/duieditor/parser/qmljslexer_p.h src/plugins/duieditor/parser/qmljsmemorypool_p.h src/plugins/duieditor/parser/qmljsnodepool_p.h src/plugins/duieditor/parser/qmljsparser.cpp src/plugins/duieditor/parser/qmljsparser_p.h src/plugins/duieditor/parser/qmljsprettypretty.cpp src/plugins/duieditor/parser/qmljsprettypretty_p.h src/plugins/duieditor/rewriter/rewriter.cpp src/plugins/duieditor/rewriter/rewriter_p.h src/plugins/duieditor/rewriter/textwriter.cpp src/plugins/duieditor/rewriter/textwriter_p.h src/shared/cplusplus/ASTClone.cpp tests/manual/cplusplus/main.cpp
-
Jason McDonald authored
Reviewed-by: Trust Me
-
- Jun 12, 2009
-
-
con authored
Done with dt.
-
- Jun 08, 2009
-
-
kh authored
Reviewed-by: dt
-