[Releasing] QtDeclarative aka QtQuick1 examples & docs

Robin Burchell robin+qt at viroteck.net
Wed Dec 12 12:27:46 CET 2012

On Tue, Dec 11, 2012 at 11:10 PM, André Pönitz
<andre.poenitz at mathematik.tu-chemnitz.de> wrote:
> How many people would you expect to use QtQuick 1 in a Qt 5 environment
> instead of going to QtQuick 2?

Right now? Quite a lot. People have existing projects written using
QtQuick1, and just like QWidget, that won't go away overnight (if
ever, given the nature of legacy software). And unfortunately, it's
not possible for QtQuick1 and QtQuick2 code to coexist in the same
scene side by side, as far as I know, so that transition isn't
something you can do piece by piece.

In the future (say, 12-18 months)? I hope it'll go away pretty fast. I
don't like QtQuick1 now I've used QtQuick2. I think it could still
have some value in the embedded space, on hardware that can't (or
won't) deal with OpenGL, but I don't see it being used on desktop, for
instance, provided ANGLE deals with the OpenGL issue on Windows in a
robust way (but that's not something I know anything about, really).

The key point I was making with bringing up deprecation is that it's
too early. QtQuick2 hasn't been released, and with all the chopping
and changing that Qt 5 has undergone, I think it's safe to say that it
would have been massively risky for anyone to use it for anything
other than experimentation - let alone trying to actually create
products using it. Now that the release is finally on the horizon,
it's getting to the point where it can be looked at and evaluated for
things like that, and that's when you'll see uptake _start_. But it'll
still be some time before you can safely say that nobody is doing
anything new with QtQuick1.

> It's a serious question.

I never took it as anything other than that :-)

More information about the Releasing mailing list