- Sep 29, 2010
-
-
Lasse Holmstedt authored
Moved qmljsdebugger to a dir under qml/, made qmlobserver compile without creator dependencies and made it compile with debugging helpers. Reviewed-by: hjk
-
- Sep 28, 2010
-
-
Christian Kamm authored
This lead to the semantic checker reporting incorrect errors in these initializers. Task-number: QTCREATORBUG-2340 Reviewed-by: Roberto Raggi
-
Kai Koehne authored
Reviewed-by: Christiaan Janssen (cherry picked from commit e871b7e3)
-
- Sep 27, 2010
-
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
- Sep 24, 2010
-
-
Christian Kamm authored
It's meant to be. Reviewed-by: Daniel Molkentin
-
Christian Kamm authored
-
Christian Kamm authored
-
Christian Kamm authored
When multiple threads share the Bind instance in a Document and do lookup on the objects contained inside, that may trigger a new object creation in some situations - which needs to be synchronized.
-
Christian Kamm authored
-
- Sep 23, 2010
-
-
hjk authored
-
Christian Kamm authored
The Qt4ProjectManager now uses metacalls to inform the QmlJSModelManager about the project data. Done-with: hjk
-
- Sep 22, 2010
-
-
Christiaan Janssen authored
Reviewed by: Thomas Hartmann
-
- 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.
-
Christian Kamm authored
-
- Sep 15, 2010
-
-
Christian Kamm authored
-
- Sep 08, 2010
-
-
Roberto Raggi authored
Reviewed-by: Christian Kamm
-
- Aug 31, 2010
-
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
-
Christian Kamm authored
Don't use QMultiHash::values(key), it rebuilds the values list from scratch for each lookup. Reviewed-by: Roberto Raggi
-
- Aug 30, 2010
-
-
Christian Kamm authored
We don't want people modifying the shared component chain on a const Context *.
-
Christian Kamm authored
-
- Aug 27, 2010
-
-
Olivier Goffart authored
-
Tobias Hunger authored
* Fix all warnings about non-explicit constructors except for those in 3rdparty code.
-
Christian Kamm authored
Now that Contexts are cached, it needs to be copyable. However, the ScopeChain has a QmlComponentChain member that owns resources and didn't have a correct copy constructor or copy assignment operator. I've made QmlComponentChain non-copyable and store a shared pointer to an instance instead, as it will generally not change for a given context. Reviewed-by: Lasse Holmstedt
-
- Aug 26, 2010
-
-
Christiaan Janssen authored
-
Christian Kamm authored
-
Christian Kamm authored
* If possible, create LookupContexts through SemanticInfo; it caches the linked Context and will be faster. * Contexts now own their Engine. Reviewed-by: Lasse Holmstedt
-
- Aug 25, 2010
-
-
Christian Kamm authored
-
Christian Kamm authored
The builtin QML plugins require to be imported with the full uri, i.e. import Qt.labs.particles 1.0 so setting the import path to imports/Qt/labs and doing import particles 1.0 is not supposed to work. (see QTBUG-11139) This change adjusts qmldump to take an import path *and* the import uri, so it will be able to dump the type information for these plugins. Reviewed-by: Erik Verbruggen
-
Christian Kamm authored
In preparation for caching Contexts. Reviewed-by: Erik Verbruggen
-
- Aug 19, 2010
-
-
Olivier Goffart authored
Apparently, it did not like ::label
-
Olivier Goffart authored
-
- Aug 13, 2010
-
-
Thomas Hartmann authored
closed() is emitted when the pane is hidden/closed.
-
Christian Kamm authored
The QColor constructor prints a warning if the string it gets passed isn't a known color name. Also, it doesn't know about the alpha value in strings like "#ff00ff00". Reviewed-by: Thomas Hartmann
-
- Aug 12, 2010
-
-
Kai Koehne authored
-
- Aug 10, 2010
-
-
Friedemann Kleint authored
-
Christian Kamm authored
Done-with: Thomas Hartmann
-
Christian Kamm authored
Reviewed-by: Roberto Raggi
-
- Aug 05, 2010
-
-
Lasse Holmstedt authored
When a change is done to an element that cannot be changed due to debugger/qdeclarative limitations, a warning is shown to the user in QML JS Editor. Reviewed-by: Olivier Goffart
-