[Qt-qml] QtQuick 2.0?

Stephen Kelly steveire at gmail.com
Thu May 5 00:43:29 CEST 2011


Alan Alpert wrote:

> On Wed, 4 May 2011 19:33:55 ext Stephen Kelly wrote:
>> Alan Alpert wrote:
>> > On Wed, 4 May 2011 03:39:22 ext Jason H wrote:
>> >> I thought with modularization, that what is in "qt 4.8" should matter
>> >> less and less.
>> >> 
>> >> For instance, there is a QML2 plugin that will work with QML1
>> >> http://labs.qt.nokia.com/2011/05/03/qml-shadereffectitem-on-
>> 
>> qgraphicsview/
>> 
>> >> If everything except the core is a plug in, then what is in 4.8 should
>> >> be less relevant.
>> > 
>> > That plugin is a QML1 plugin designed to emulate a QML2 element. As far
>> > as I'm aware, it is a completely different element (C++-wise). But it
>> > does aim for QML source compatibility, like the QML2 elements designed
>> > to act like the QML1 elements we all know and love. Modularization
>> > doesn't do anything to solve this problem, alas, as QtQuick 1 and
>> > QtQuick 2 will still be incompatible.
>> 
>> Will it be possible to import QtQuick 1.0 while QtQuick 2.0 is shipped?
>> 
> 
> The theory (and there's no answer 'in practice' yet because QtQuick isn't
> shipped) is that when QtQuick 2.0 comes, you can still import QtQuick 1.0
> and it works fine. Since they're incompatible QtQuick 1.0 elements and
> QtQuick 2.0 elements will not be able to coexist in the same application,
> but your QtQuick 1.0 application will not stop working when 2.0 arrives -
> you'll have the option to upgrade it to 2.0 when you're ready.
> 
>> Wouldn't that mean complete duplication if they are so incompatible?
> 
> Depends on your application. This is a major version change though, and so
> they are not merely different (and incompatible) backends. You will likely
> need to make changes throughout your code to use the new features
> effectively. We are investigating ways to make this process easier,
> particularly for applications where it is nearly identical.
> 

Ok, thanks for the info.

Sounds comparable to a Qt 3 to 4 change in scope though not in scale.

Cheers,

Steve.




More information about the Qt-qml mailing list