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.
@Konstantin-Tokarev I can not familiar with Yocto. Could you answer my a very entrylevel question?
How to update .bb in QT to compile webkit instead of webengine? Don't consider any further error.
First just to involve webkit back.
Thanks
@Sudip-Ghimire
subclass QNetworkAccessManager and reimplement createRequest and call the base class implementation.
Then set your custom NAM to the QWebPage:
https://doc.qt.io/archives/qt-5.5/qwebpage.html#setNetworkAccessManager
FWIW, I applied the changes for src/corelib/Qt5CoreMacros.cmake as shown in https://github.com/qt/qtbase/compare/5.12.7...5.12.8, and I am now able to build QtWebKit just fine. Thanks again Konstantin!
Hi,
You should do an out of source build and start from a clean state. If you have to restart your build, just nuke the folder and start again, it will keep your sources clean.
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.
