Some more background would help. With the flexibility of QML, why would you want to restrict yourself to HTML? There are 3 paragigms at play:
1. Classic C++ Qt, parent-child heiarchial based layouts.
2. QML, Anchor and parent/child/sibling based layouts
3. HTML, DOM based layouts
My choice is QML, though I do find myself working in C++ occasionally. And I drop to C++ for good reason: There are some things that are just not do-able in HTML5 yet.
Sent: Tuesday, March 08, 2016 at 6:22 AM
From: "Daniel França" <daniel.fra...@gmail.com>
To: "interest@qt-project.org" <interest@qt-project.org>
Subject: [Interest] Hybrid Qt/HTML5 app
From: "Daniel França" <daniel.fra...@gmail.com>
To: "interest@qt-project.org" <interest@qt-project.org>
Subject: [Interest] Hybrid Qt/HTML5 app
Hi guys,
I was planning to create an hybrid app using Qt/QML/HTML5.
I found that we can do that using WebKit [1] (at least for Qt widgets)
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interestI was planning to create an hybrid app using Qt/QML/HTML5.
The application should be able to inject some QML elements or Qt widgets inside and interact with it.
I found that we can do that using WebKit [1] (at least for Qt widgets)
But it seems that it's not yet implemented in WebEngine (isn't Webkit deprecated?).
Does anyone has experience doing a similar thing? Which approach do you think is better? How do you suggest to work with Qt/QML/HML5?
Best,
Daniel
Does anyone has experience doing a similar thing? Which approach do you think is better? How do you suggest to work with Qt/QML/HML5?
Best,
Daniel
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
