"README.md" did not exist on "95fc94d91fca50d35f4458dce89cbd6a0248bf50"
- Mar 05, 2010
-
-
hjk authored
-
- 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
-
- Aug 14, 2009
-
-
hjk authored
-
- Jun 16, 2009
-
-
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
-
- May 26, 2009
-
-
Thorbjørn Lindeijer authored
The actions are already lazily instantiated in TextEditorActionHandler::setupActions(), so there should be no need to call initializeActions() in all plugins on startup. Only the main text editor plugin will still initialize its actions, to make sure the menu items are there.
-
- Feb 25, 2009
- Jan 13, 2009
-
-
Daniel Molkentin authored
-
Daniel Molkentin authored
-
- Dec 16, 2008
-
-
hjk authored
-
- Dec 02, 2008