[Interest] Qt Quick Controls 1 deprecated but no native styles for Qt Quick Controls 2?

[Mitch Curtis]

Accidentally sent this privately.

> -----Original Message-----
> From: Mitch Curtis
> Sent: Friday, 7 December 2018 2:12 PM
> To: 'Giuseppe D'Angelo' <giuseppe.dangelo at kdab.com>
> Subject: RE: [Interest] Qt Quick Controls 1 deprecated but no native styles for
> Qt Quick Controls 2?
> 
> > Well, if you have nothing better than what you used to, stick with
> > that. This is my proposal. That is, I do understand what problems you
> > see in QStyle
> 
> Are you sure? :D Personally, I have so far avoided having to touch QStyle
> code, working mainly on Qt Quick, but let's take what Giuseppe was referring
> to as an example:
> 
> > Giuseppe D'Angelo via Interest
> > [snip]
> >
> > 2) At the very core of native styling in Qt there's QStyle, which uses
> > CPU-based rendering, relying on pixel perfect output provided by
> > QPainter. (Take a look into a style class, you'll found thousands of
> > QPainter draw calls). A native style built for QQC2 will mean one of
> > these options:
> 
> Here are some links for just the Windows styles alone:
> 
> http://code.qt.io/cgit/qt/qtbase.git/tree/src/widgets/styles/qwindowsstyle.
> cpp - 2401 lines
> http://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/styles/windowsvista/q
> windowsxpstyle.cpp - 4243 lines
> http://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/styles/windowsvista/q
> windowsvistastyle.cpp - 2405 lines
> 
> This, for me, is why I would never want to base future desktop styling on
> QStyle. I don't think this is maintainable or future-proof at all. That's just my
> opinion though. I don't speak for anyone else.
> 
> > but one only should remove something when there's a replacement for it.
> 
> They haven't been removed though?