- Sep 08, 2011
-
-
Christian Kamm authored
Change-Id: I6721b42a6ae8cc4de3d85754bf12c95f7366212e Reviewed-on: http://codereview.qt-project.org/4395 Reviewed-by:
Christian Kamm <christian.d.kamm@nokia.com>
-
- Sep 07, 2011
-
-
Christian Kamm authored
Change-Id: Iaedaaa88915f2010bfdd0d2b5ca95f01f8663ed7 Reviewed-on: http://codereview.qt.nokia.com/4254 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@nokia.com>
-
Christian Kamm authored
Evaluate supports ExpressionStatements now. Change-Id: I74c440fe0abf27c3d3b41b7d28a69fdd9359fb2e Reviewed-on: http://codereview.qt.nokia.com/4080 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@nokia.com>
-
- Sep 06, 2011
-
-
Christian Kamm authored
Change-Id: I2cc1236552e00e99a846b0d4b724135724f175fc Task-number: QTCREATORBUG-3666 Reviewed-on: http://codereview.qt.nokia.com/4241 Reviewed-by:
Leandro T. C. Melo <leandro.melo@nokia.com>
-
- Aug 08, 2011
-
-
Christian Kamm authored
The distinction between QmlJS and QmlJS::Interpreter has always been weak and the extra namespace just added an unnecessary complication. Change-Id: I4db8ef4bd91b5f6bf610a9d23fdbf55bd60250fc Reviewed-on: http://codereview.qt.nokia.com/2743 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@nokia.com>
-
Christian Kamm authored
Previously Context was not entirely thread safe and had to be copied locally. Now it is thread safe and its lifetime managed by QSharedPointer. The non-safe parts were moved into ScopeChain in a previous commit. Change-Id: I851a93de85cbd6391dbea0fe33b011e2e093addb Reviewed-on: http://codereview.qt.nokia.com/1695 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@nokia.com>
-
Christian Kamm authored
Context is created by Link and has information about imports for all Documents in a Snapshot. ScopeChain represents how lookup is done at a specific place in a Document. Change-Id: I874102d57bbaf1a497fa3f27633bed6ee75dcf10 Reviewed-on: http://codereview.qt.nokia.com/1694 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@nokia.com>
-
- Jul 05, 2011
-
-
Christian Kamm authored
Change-Id: I91331b7039e27e2f57cc19b985c8ed86c955ec9e Reviewed-on: http://codereview.qt.nokia.com/1042 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@nokia.com>
-
- Jun 24, 2011
-
-
Christian Kamm authored
Change-Id: Iaeb96ff67cfc92bcddeb1b7075b7fdcbaed317c0 Reviewed-on: http://codereview.qt.nokia.com/691 Reviewed-by:
Thomas Hartmann <Thomas.Hartmann@nokia.com>
-
- Jun 23, 2011
-
-
Christian Kamm authored
Task-number: QTCREATORBUG-3541 Change-Id: Ida8e59b65836c8515fbfbd2a9e4737d9ae04e76c Reviewed-on: http://codereview.qt.nokia.com/639 Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@nokia.com>
-
- Jun 07, 2011
-
-
Fawzi Mohamed authored
correctly insert the scope for code blocks in UiScriptBindings and UiPublicMember, and improve find usages for types (correctly detecting variables in the same scope) Change-Id: Iaaf1a59f041f3831fbe04243b220fb85fde76479 Reviewed-on: http://codereview.qt.nokia.com/335 Reviewed-by:
Christian Kamm <christian.d.kamm@nokia.com>
-
- May 20, 2011
-
-
Christian Kamm authored
To avoid lots of follow-up errors where the root cause is a failed prototype resolution or a prototype cycle. Task-number: QTCREATORBUG-4952 Change-Id: Id474c8c6c152c993aca8c6c421b6d88eb1481676 Reviewed-on: http://codereview.qt.nokia.com/36 Reviewed-by:
Thomas Hartmann <Thomas.Hartmann@nokia.com>
-
- May 12, 2011
-
-
Christian Kamm authored
UiPublicMember is now initialized with a statement.
-
- May 06, 2011
-
-
Tobias Hunger authored
Change-Id: I8b73d583be1ee7183f4074bce49d5390e38631a2
-
Christian Kamm authored
To avoid order-of-initialization problems. Reviewed-by: Thomas Hartmann
-
- May 04, 2011
-
-
Christian Kamm authored
Task-number: QTCREATORBUG-2306
-
- Apr 21, 2011
-
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
-
- Apr 13, 2011
-
-
hjk authored
-
- Mar 01, 2011
-
-
Thomas Hartmann authored
Unifying the api and exposing the options.
-
Thomas Hartmann authored
Missing files should be a warning.
-
- Feb 21, 2011
-
-
Christian Kamm authored
The problem was that several lookup calls suddenly failed because the actual QML types were no longer in the default scope chain. However, the QML documentation says the type names are in the scope. Also, 'MyComponent.' in a JS-expression context only showed the attached properties of MyComponent and missed the enums. With this change completion now may offers too many options, but that's better than missing some. This reverts parts of 490f2797 Reviewed-by: Leandro Melo
-
- Feb 10, 2011
-
-
Christian Kamm authored
-
- Feb 09, 2011
-
-
Christian Kamm authored
-
- Jan 12, 2011
- Dec 17, 2010
-
-
con authored
-
- Dec 13, 2010
-
-
Thomas Hartmann authored
Each Components starts a new scope for ids. Using a stack to check this properly.
-
Thomas Hartmann authored
-
- Dec 07, 2010
-
-
Thomas Hartmann authored
We are checking for duplicate ids and duplicate property definitions now.
-
- Dec 06, 2010
-
-
Christian Kamm authored
Reviewed-by: Erik Verbruggen
-
Christian Kamm authored
Also * check the condition of the 'for(var' statement for assignment * allow comma expressions in 'for(var' Reviewed-by: Erik Verbruggen
-
- Nov 29, 2010
-
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
-
Christian Kamm authored
The "value might be 'undefined'" warning triggered whenever the static expression evaluator failed to produce a value. At the moment, it does so for almost all non-trivial expressions. The warning is now disabled. Task-number: QTCREATORBUG-3208
-
- Nov 25, 2010
-
-
Christian Kamm authored
Task-number: QTCREATORBUG-3071 Reviewed-by: Erik Verbruggen
-
Christian Kamm authored
It still generates too many false-negatives for now. Will be enabled once the remaining lookup failures have been fixed. Reviewed-by: Erik Verbruggen
-
Christian Kamm authored
Reviewed-by: Erik Verbruggen
-
- Sep 24, 2010
-
-
Christian Kamm authored
-
- Sep 16, 2010
-
-
Christian Kamm authored
Link now caches imports. That means importing the same library (say, Qt) from more than one file no longer creates an importing namespace for each one. Instead, a single one is created for the instance of Link. To make this work, the type environment in ScopeChain has been given its own type: Interpreter::TypeEnvironment. That has the added benefit of being able to carry meta-information about imports. You can use TypeEnvironment::importInfo(qmlComponentName) to get information about the import node that caused the import of the component.
-