[Development] Deprecation of Qt Quick Controls 1
enmarantispam at gmail.com
Wed Feb 7 14:12:40 CET 2018
And no, widgets is not an alterlative to proper qml controls on desktop
when you want custom interface.
I have an app that uses qml to draw a custom listview for users, it would
be extremely hard to replicate it with widgets and why should I do that
when I have qml?
On Wed, Feb 7, 2018 at 4:10 PM, NIkolai Marchenko <enmarantispam at gmail.com>
> I basically can't use Controls 2 in my application because combobox in
> controls 2 has extremely out of place style for desktop applications, is
> too bloated and you can't control it enough to make it look more like
> Controls 1.
> Admittedly, I almost do not use QML in my apps but I wasn't able to find
> an easy solution to make combobox tolerable for desktop
> On Wed, Feb 7, 2018 at 4:06 PM, Helmut Mülner <helmut.muelner at gmail.com>
>> > It should come as no big surprise that we are not working much on Qt
>> Quick Controls 1.
>> After some discussions inside The Qt Company, we concluded that it would
>> make sense to clarify the situation.
>> We see the value Controls 1 provides - more platform native styling - but
>> it comes at a high price.
>> > […]
>> > As you can see, the effort is currently split and we'd like to reduce
>> the attention to the two big areas - Widgets and Quick with Controls 2. This
>> means we will spend even less time on Controls 1, where we'll only fix
>> critical issues in the future.
>> In my application I mostly use Controls 2 but have to add some controls
>> from Qt Quick Controls 1, e.g. TableView, SplitView, Calendar, ScrollView.
>> It would be nice to have these controls available in Controls 2 before you
>> deprecate Controls 1.
>> Development mailing list
>> Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development