[Development] [Interest] Current status of the co-installation

Chris Adams chris.adams at qinetic.com.au
Tue Oct 30 01:12:02 CET 2012


Hi,

[snip]


> Question: qml2scene or qml2viewer? If no one speaks up, it will be
> qml2scene.
> The patches for that are ready, pending approval.
>

[snip]


>
> The relevant changes are:
>  Qt Quick 1 & 2:
>         https://codereview.qt-project.org/37104 (QQ1's imports with no
> subdir)
>         https://codereview.qt-project.org/37242 (adds -qmldir)
>         https://codereview.qt-project.org/37431 (renames qml1plugindump
> back)
>         https://codereview.qt-project.org/37434 (renames QQ2 tools to
> qml2*)
>         https://codereview.qt-project.org/37539 (use the Qml2ImportPath)
>         https://codereview.qt-project.org/35521 (changes QQ2 examples dir)
>         https://codereview.qt-project.org/36711 (doc update about the
> examples)
>         https://codereview.qt-project.org/37555 (updates Qt Creator)
>

[snip]

qml2scene makes more sense than qml2viewer, in my opinion.
I've added some comments to various reviews, although I'm slightly confused
about what the current plan is with respect to 37104 vs 38300 for example.
The only one I have an issue with, really, is the rename of the environment
variable to QML2_IMPORT_PATH - purely from a consistency perspective with
the other envvars like QML_COMPILER_STATS and so forth.

I've added Martin as reviewer to most of them, to see if he has any issue
with any of the changes, also.

Cheers,
Chris.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121030/632f115b/attachment.html>


More information about the Development mailing list