> Widgets are heavy, often very complex objects. They often come with all bells > and > whistles. QPushButton always has the data structure to support > QPushButton::setMenu, > even if probably <1% of buttons out there ever use that feature. That’s ok on > desktop > machines, it’s not ok on embedded systems.
Hm, this kind of confirms my impression: Quick is lightweight, simplified and suited for embedded and touch. While widgets are more powerful and suited for complex desktops applications. This makes me wonder even more why Qt gave up widgets. The logical explanation is, Qt kind of gave up desktop. You explained why the widgets concept is not compatible with the Quick concept. Can you also explain why it was not possible to implement Quick as an additional, mostly widget- independent C++ layer and then wrap it declaratively? -- Best Regards, Bernhard Lindner _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
