Hear hear.
I would also bring to the table the removals from QtQuick API. The
QtQuick.Extras was removed in Qt6. The missing CircularGauge (which is
non-trivial to implement or port) has prevented me to migrate to Qt6.
With modern C++, the value of Qt is the multiplatfrom GUI (and as a
profes
Fair enough, as long as they are not removed anytime soon
> Marc Mutz via Development kirjoitti 4.12.2023
> kello 10.20:
>
> On 04.12.23 09:06, Jyrki Yli-Nokari wrote:
>>
>> While I do not use them, I feel that deprecating such core functionality of
>> a fra
While I do not use them, I feel that deprecating such core functionality of a
framework without measurable gain would seriously harm anyone using them and,
most importantly, fundamentally harm the promise and dependability of Qt as a
framework of choice.
> Giuseppe D'Angelo via Development ki
For me, the key use case is to implement https server (with authentication) to
my embedded device code
> Vladimir Minenko kirjoitti 18.3.2022 kello 18.04:
>
> Hello all,
>
> as it was mentioned in https://www.qt.io/blog/qt-roadmap-for-2022, there are
> more topics in development at the momen
standpoint.
I am not a license holder and am a long time critic of QtC licensing to
startups.
And I love Qml
> Jyrki Yli-Nokari kirjoitti 13.5.2021 kello 10.22:
>
> The decision will eventually alienate OS community which will force current
> licensees consider the viabilty of
Thiago is right. Qt’s biggest problem is the barrier of entry. User facing
tools must work as documented.
> Thiago Macieira kirjoitti 16.2.2021 kello 1.15:
>
> On Monday, 15 February 2021 01:18:16 PST Joerg Bornemann wrote:
>>> To be clear:
>>> 1) the binaries from Qt company must also perform
