Aug 30, 2024
Qt/.NET — Using QML in a .NET WPF application
Qt/.NET is a proposed toolkit for interoperability between C++ and .NET,..
Jul 1, 2024
Qt for Android: a Novel Approach
This blog post is the third one in a series in which we will examine an..
May 21, 2024
Qt for Windows on ARM - today, it is more interesting than ever!
Qt is the leading framework for building cross-platform and multi-platform..
Commenting for this post has ended.
Uhm just listen to the votes in jira? 90% of the people would be fine with using a simple WebView if it was available on Windows. Now I have to ship an entire browser just to show our html documentation.
Yep, we are well aware of this need. We need to hear more voices to start this on the right end! :-)
WebEngine on Android would be great. iOS also opened up for 3rd party web engines (at least in EMEA region). WebView should be available on all platforms.
Yep, Qt WebEngine on Android is not provided, ATM. And if it was provided, it would appear as a sort of overkill, since there are pretty rich APIs meanwhile which talk to the Blink instance as a part of Android. So, do you mean the actual Qt WebEngine on Android or rather a Qt API layer on top of the native Android "WebView" and other web APIs?
The problem with WebView is that it cannot be fully integrated into the scene (e.g., [partly] covered by other Qml elements), or even hidden for offscreen rendering.
Tried to submit feedback but it fails at the question "Do you think, this survey covered most aspects essential for your work with Qt WebEngine and Qt WebView?" with error "! Please do not leave the comment field empty". The only way to pass was to remove my comment and select Yes. Anyway, I would like to see a simple WebView for Qt widgets that does not require shipping full web engine (but is a wrapper for native web view) and what would work with MinGW and WASM as well.
Had the same issue. The error text is wrong, it occurs when your text is too long.
Thanks for reporting this! We heard of this yesterday from someoe else! It is fixed now.