[Development] Separation of QtQuick 1 from QtDeclarative repo
lars.knoll at nokia.com
lars.knoll at nokia.com
Mon Feb 13 20:12:55 CET 2012
On 2/13/12 5:52 PM, "ext Stephen Kelly" <stephen.kelly at kdab.com> wrote:
>On Friday, February 03, 2012 12:17:35 lars.knoll at nokia.com wrote:
>> >Hi,
>> >
>> >It seems like this change broke qt/qttools, can you confirm this
>>please ?
>>
>> I'd assume qttools doesn't include the qtquick1 repo as a dependency.
>
>It needs declarative in Qt4 because lupdate uses it to extract
>translations.
>
>This raises the question of whether lupdate will also need to use the Qt5
>declarative module to extract QML2 translations, or will the language and
>features remain static so that the qtquick features will also be
>sufficient.
It should be. Let's fix it once the renaming is done.
>
>On Monday, February 06, 2012 07:58:04 martin.jones at nokia.com wrote:
>> Yes, we are working on renaming the classes in the declarative module to
>> either Qml... or QQuick... depending on case. There will be a period
>>where
>> using QtQuick 1 and 2 together is not possible, but we will sort this
>>out
>> as quickly as we can, hopefully without causing big disruptions to
>>users of
>> either library.
>
>This raises the question of whether the Qt5/declarative module will be
>renamed (if all classes in it are renamed Qml*) and if the module
>includes will be moved.
>
>
>The followup question is whether the qtqtuick1 module can be renamed
>QtDeclarative so that there is less source incompatibility (of the
>buildsystem and module includes).
See my comment on https://bugreports.qt-project.org/browse/QTBUG-23737 .
It's WIP.
Cheers,
Lars
More information about the Development
mailing list