On Thu, Aug 16, 2018 at 4:17 PM Vlad Stelmahovsky <
> A bit unclear about deprecating QQC1
> Since in QQC2 no TreeView and even no plans for this, isn't it a bit too
> early to deprecate QQC1?
> On Thu, Aug 16, 2018 at 4:02 PM Jason H <***@gmx.com> wrote:
>> 5.11 included WebGL TP2. Is there any change? Why is it staying TP2, or
>> should it be TP3?
>> 5.12 looks like it'll be a pretty great update!
>> I'm not sure what's on the agenda for 5.13... but as I mentioned on
>> interest, one pain point I continually have is the amount of custom
>> platform integrations for mobile. This is one area where Xamrain excels, as
>> they have a simple property on an object you can set to control things like
>> the status bar visibility, the screen brightness, etc. The downside is the
>> Xamarin stuff is all platform-specific so using a iOS property on Android
>> won't work. This is one area where Qt can leapfrog the other platforms
>> including React Native by being cross platform. Anything that doesn't
>> require me to write Obj-C is a very good thing! I figure this would need
>> to be a few Qt Quick/QObject Singletons. Notifications should be supported
>> too, and this could also be used for desktop platform notifications as
>> well. The notifications support would only need to cover being messaged my
>> the platform, and not any display - this would get me out of having to deal
>> with Obj-C almost completely. (My beef wi
>> th ObjC is other than being not good at it, is whatever I'm writing
>> isn't cross-platform. Java I am more comfortable with, so I complain less,
>> but I still cringe on the non-portability!)
>> Looking forward to 5.12!
>> > Sent: Wednesday, August 15, 2018 at 12:50 AM
>> > From: "Jani Heikkinen" <***@qt.io>
>> > To: "***@qt-project.org" <***@qt-project.org>
>> > Subject: [Development] Qt 5.12 new features
>> > Hi,
>> > Qt 5.12 Feature Freeze will be in effect Mon 20th August and we should
>> have already now pretty good understanding what is new in Qt 5.12. So
>> please update 5.12 new features page here:
>> > br,
>> > Jani
Why deprecate QQC1?
If you aim for a native looking QML application in Windows 7 then QQC1 is
basically the only viable way to go.
I know there is a third party plugin for QQC2 and the QWidgets style (thus
also Windows 7) integration, but it's a third party one  and not shipped
with Qt. I have no clue how much of the QWidgets style is supported by that
I think it would be nice to not deprecate the only QML way to make native
looking Windows 7 applications in the Qt 5.xx lifecycle.
Or do deprecate it, but offer the plugin  from within the Qt installer
as an alternative.
Also, i vaguely remember that QQC1 was meant for integrating applications
in QML with your host OS and QQC2 was targeted at mobile and to be free of
QWidgets to allow for performance improvements.
So they both serve a different target group despite having quite some
overlap in functionality.