> A simple push button is made of ( IIRC ) more than 30 QObjects with Quick Controls 1, the version of Quick Controls 2 with less features still consists of 7 QObjects. Each stop of a gradient is made as QObject for no other reason, than to make it accessible from QML.
Wouldn't the better solution here be to allow multiple QML-defined objects to coalesce into a single "C++" QObject ? This way you'd get much better cache friendliness, less allocations, etc etc. Ideally this could be doable in C++ too, but with a good meta-object refactoring. Something like QObject mixins (this would *really* solve world hunger :p). Would certainly require templates at some point. ------- Jean-Michaël Celerier http://www.jcelerier.name On Fri, Oct 20, 2017 at 3:38 PM, Roland Hughes <rol...@logikalsolutions.com> wrote: > > On 10/20/2017 08:25 AM, Vlad Stelmahovsky wrote: > > is someone pushes someone to use QML as a mandatory or store data into > JSON DBs? Where? How? Its ridiculous. > > > You go out for training to learn how to properly use a tool. All you are > taught is QML and JSON because they are "new." Nothing ridiculous about it. > When the only tool you have is a hammer, every problem must be a nail. > > -- > Roland Hughes, President > Logikal Solutions > (630)-205-1593 > http://www.theminimumyouneedtoknow.comhttp://www.infiniteexposure.nethttp://www.johnsmith-book.comhttp://www.logikalblog.comhttp://www.interestingauthors.com/bloghttp://lesedi.us/http://onedollarcontentstore.com > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest