Previously, the import statement was not necessarily set up correctly
for the type we wanted to instantiate. We simply use
QDeclarativeType::create now and thus can skip finding the right import.
Change-Id: I545ef690dd6181f5b7a49bcb2018aaba4b60d5a5
Reviewed-on: http://codereview.qt.nokia.com/1646
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
If the current working directory was a direct parent of the qmldir path
the exported modules had the path as the module URI on macs.
Also changes the QtQuick export back to 1.0 to make it work with
Qt 4.7.3. The version of that import statement does not actually matter
as long as it's valid.
Change-Id: Ib702356062bd239b1ad807c2592f8a69d6fde38f
Reviewed-on: http://codereview.qt.nokia.com/896
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
(cherry picked from commit dc3e803614)
Compare the full uri/name, not just the uri. Also
QDeclarativeType::module was not available in 4.7.3.
Change-Id: I0d04d826c72d4aed5d70c3c65a1f97ad5872827c
Reviewed-on: http://codereview.qt.nokia.com/759
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
The qmltypes file reader now ignores unknown bindings and components
to allow for better forward-compatibility.
Change-Id: I2e31c17344dc8fdcd301a62c8d08e98c29ef53ee
Reviewed-on: http://codereview.qt.nokia.com/202
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
Absolute file pathes containing drive identifiers do not work in qml.
(C:\)
workaround: use "." imports and setting the component url.
Reviewed-by: Christian Kamm
