Andre, Thank you. It's indeed very interesting. My application is a very memory hungry one. So, I'm looking at how to save memory and not to use QML.
QWidgets are fine, but they are non-native in many cases, lack some important features, and there integration with native objects has some open bugs. Thus, a natively-developed GUI could be without the above issues. At another side, QtCore and other infrastructure is so impressive so that it is worth bringing it in. Regards, Robert On Thu, Sep 3, 2015 at 10:00 AM, André Somers <an...@familiesomers.nl> wrote: > Op 3-9-2015 om 07:38 schreef Robert Iakobashvili: >> Gentlemen, >> To overcome various issues and not-nativeness of Qt on iOS, >> I was thinking about the following combination: >> >> 1. Swift-written native GUI; >> 2. Internals supported by Qt-containers, QString, networking, IPC >> from QtCore, QtNetwork; >> >> Has somebody tried the above combination and any experience >> could be shared like best practices or caveats? >> Thank you. >> >> Regards, >> Robert >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest > At QtCS in Oslo this summer there was an interesting presentation on > using native widgets from QML [1]. Looked like a very cool and via approach. > > André > > [1] > https://wiki.qt.io/Qt_contributors_summit_2015_Program#NativeQML_-_Wrapping_native_UI_controls_in_QML > _______________________________________________ > 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
