[Development] Dropping remaining support of qtquick1

[Kai Koehne]

Hi,

Can we drop the last remaining traces of qtquick1 from qtbase?

Remember that qtquick1 is not part of Qt anymore since Qt 5.6. Anyhow, some people might still compiled it compiled with later versions on their own ... Right now it doesn't compile for me with 5.12, but I haven't investigated why.

The last remaining support for Qt Quick 1 are in the build system (qml1_module.prf, qml1_plugin.prf), QLibraryInfo::ImportsPath, qmake ($$QT_INSTALL_IMPORTS), and finally in QObject and QWidget (handling of QAbstractDeclarativeData::destroyed_qml1).

We could remove these already in 5.12, in 5.13, or wait for Qt 6. I'd prefer 5.12 if nobody objects 😊

Regards

Kai

--
Kai Koehne, Senior Manager R&D | The Qt Company

The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg,
HRB 144331 B

The Future is Written with Qt
www.qtworldsummit.com

[Thiago Macieira]

On Friday, 5 October 2018 02:24:39 PDT Kai Koehne wrote:
> The last remaining support for Qt Quick 1 are in the build system
> (qml1_module.prf, qml1_plugin.prf), QLibraryInfo::ImportsPath, qmake
> ($$QT_INSTALL_IMPORTS), and finally in QObject and QWidget (handling of
> QAbstractDeclarativeData::destroyed_qml1).
>
> We could remove these already in 5.12, in 5.13, or wait for Qt 6. I'd prefer
> 5.12 if nobody objects

I don't think we should. qtquick1 may not be as dead as we'd like it to be.
I'd rather keep the QtCore API just in case someone is keeping the old module
working for their applications (or Linux distribution, though I can't find
any). They may also be (ab)using QLibraryInfo::ImportsPath for some other
purpose.

--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center

[NIkolai Marchenko]

I would like to remind people that there has already been a deprecation
thread "[Development] Deprecation of Qt Quick Controls 1" byFrederik
Gladhorn this Februrary.
A couple issues were raised there that were rather relevant and I would
like to know if they were ever addressed.

On Fri, Oct 5, 2018 at 6:29 PM Thiago Macieira <***@intel.com>
wrote:

> On Friday, 5 October 2018 02:24:39 PDT Kai Koehne wrote:
> > The last remaining support for Qt Quick 1 are in the build system
> > (qml1_module.prf, qml1_plugin.prf), QLibraryInfo::ImportsPath, qmake
> > ($$QT_INSTALL_IMPORTS), and finally in QObject and QWidget (handling of
> > QAbstractDeclarativeData::destroyed_qml1).
> >
> > We could remove these already in 5.12, in 5.13, or wait for Qt 6. I'd
> prefer
> > 5.12 if nobody objects
>
> I don't think we should. qtquick1 may not be as dead as we'd like it to
> be.
> I'd rather keep the QtCore API just in case someone is keeping the old
> module
> working for their applications (or Linux distribution, though I can't find
> any). They may also be (ab)using QLibraryInfo::ImportsPath for some other
> purpose.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel Open Source Technology Center
>
>
>
> _______________________________________________
> Development mailing list
> ***@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>

[Edward Welbourne]

NIkolai Marchenko (5 October 2018 18:30) wrote:
> I would like to remind people that there has already been a deprecation thread "
> [Development] Deprecation of Qt Quick Controls 1" by
> Frederik Gladhorn this Februrary.
> A couple issues were raised there that were rather relevant and I would like to know if they were ever addressed.

To save others the finding of it, that starts here:
https://lists.qt-project.org/pipermail/development/2018-February/032073.html

Eddy.

[Pierre-Yves Siret]

Le ven. 5 oct. 2018 à 18:34, Edward Welbourne <***@qt.io> a
écrit :

> NIkolai Marchenko (5 October 2018 18:30) wrote:
> > I would like to remind people that there has already been a deprecation
> thread "
> > [Development] Deprecation of Qt Quick Controls 1" by
> > Frederik Gladhorn this Februrary.
> > A couple issues were raised there that were rather relevant and I would
> like to know if they were ever addressed.
>
> To save others the finding of it, that starts here:
>
> https://lists.qt-project.org/pipermail/development/2018-February/032073.html
>
> Eddy.
> _______________________________________________
> Development mailing list
> ***@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development


Kai is talking about Qt Quick 1 not Qt Quick Controls 1

[NIkolai Marchenko]

Doesn't that mean that Controls will also get the boot though?

On Sat, Oct 6, 2018 at 3:33 PM Pierre-Yves Siret <***@gmail.com> wrote:

>
>
> Le ven. 5 oct. 2018 à 18:34, Edward Welbourne <***@qt.io> a
> écrit :
>
>> NIkolai Marchenko (5 October 2018 18:30) wrote:
>> > I would like to remind people that there has already been a deprecation
>> thread "
>> > [Development] Deprecation of Qt Quick Controls 1" by
>> > Frederik Gladhorn this Februrary.
>> > A couple issues were raised there that were rather relevant and I would
>> like to know if they were ever addressed.
>>
>> To save others the finding of it, that starts here:
>>
>> https://lists.qt-project.org/pipermail/development/2018-February/032073.html
>>
>> Eddy.
>> _______________________________________________
>> Development mailing list
>> ***@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>
>
> Kai is talking about Qt Quick 1 not Qt Quick Controls 1
>

[Thiago Macieira]

On Saturday, 6 October 2018 05:45:47 PDT NIkolai Marchenko wrote:
> Doesn't that mean that Controls will also get the boot though?

No, QtQuickControls1 is a QtQuick2 framework.

--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center