Feature-wise comparison of QtWebKit reboot with official sources:
https://github.com/annulen/webkit/wiki/Comparison-with-QtWebKit-5.6
Note that we are very close to feature parity now, i.e. there are very little features that work with legacy QtWebKit and are not yet supported with reboot, and their number is constantly lowering.
Hi,
You have to do some testing to see which one works best for you.
Since you are using Qt, QNAM asynchronous nature follows Qt design and what you are used to.
@Rizwan94 said in Make QNAM not sent any new request, until the last requests' response has arrived.:
I am concerned if the UI hangs
If you're using signals/slots then the UI will not hang (do not wait "actively" using any "wait*" methods or loops).
"When button1 is clicked, I send the request1 and wait for the response" - how do you "wait"? With signals/slots you do not have to wait and block anything.
@Rizwan94 said in Interceptor in QT?:
I got to know that in java spring framework etc. We have interceptors which help process the request & response.
In QT, do we have anything similar that can be used.
Qt uses signals and slots: https://doc.qt.io/qt-5/signalsandslots.html
Currently for making REST api calls in my application i am making use of QNAM.
When you call get() or post(), QNAM returns a QNetworkReply object. Connect the QNetworkReply::finished() signal to a slot to process the reply. Remember to delete the QNetworkReply when you have finished processing.
@radhank said in Qt Thin Client Application:
Sorry for not being precise. its 5.3.2
That version reached end-of-life in 2016. Would you consider upgrading?
You are right. Test application does not have any issue. we could see the cursor.
Am quite new to X windows as well as Qt. we have a display manager, which manages displaying these clients. We create a qt window and we share the window ID with the display manager through a FIFO and set this property using XchangeProperty.
...
We want to understand though we can see the pages, why the caret cursor is missing.
I don't know the answer, sorry.
Is the caret cursor missing if you use XChangeProperty on a simple widget like a QLineEdit?
Is the caret cursor missing if you use XChangeProperty on a non-Qt application?
I have found that this problem occur when the focus is over a numeric field. The web throw an alert message. The keyboard disappear. And after this moment, only when the focus is recieved by another numeric field, the keyboard is shown.
Hi,
While this clearly looks like a regression, Qt 5.5 is way outdated. Please test against a more recent version. Qt 5.12.4 is the current LTS but you can also try Qt 5.13.0 which is the current release.
@ahmed000001 See https://doc.qt.io/archives/qt-5.10/qnetworkreply.html#redirected
Set QNetworkRequest::FollowRedirectsAttribute in your request, then you will get the above signal with new URL if your request is redirected.
@U7Development said in Web Application development...:
can i develope my app using Qt Creator but with Cutelyst framework ?
Yes. Stock Qt Creator understands the default cmake project that Cutelyst creates quite well. I think Cutelyst also provides their own, customized version, but I have never used it.
How did you debug this? Is there any logging available?
Yes, there is JS console in Web Inspector. Also it's possible to get console messages via API
Also, does QtWebkit use some non-recent version of Webkit engine?
5.212 (which is currently shipped in Ubuntu) is based on WebKit branch from 2016
When V8 came out was around the same time I stopped programming in C++. I still love QT but was very under impressed by the JavaScript engine in QML. I have moved most of my focus since on JavaScript and Node.js (and even Microsoft Jscript.net for a time) because of the speed at which I could develop complex business applications and network applications.
My love of V8 makes it emotionally hard to accept a new V4VM but the arguments made in here seem valid and I think this may convince me to move ahead and try out QML again. It's either that or Electron.
In terms of the future and general popularity of QT, there could be nothing better than JavaScript QT. going head-to-head with Electron. However, my personal preference would be doing this without XML. I wish I could just code QT in JavaScript similar to how it's done with C++. There is a QT npm for node.js but I couldn't get it to compile... clearly not well maintained.
