In fact, in my case the purpose is to have PDF.JS in a QML app (with QtWebView), especially to have a viewer on android.
I managed to use PDF.JS on my PC with my application by stating the absolute path. The problem is ultimately not really done the same but I'll see if I can with your components advancing. And if you have an idea it will be welcome ;).
had absolutely no effect on the memory leak under Windows 10 and MAC OS X 10.
After reading the post above, about the QWebView's caching mechanism and memory usage, I looked for more information and came across this article: https://webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/
Something caught my attention - "unload event handlers, prevent pages from going into the Page Cache". Ding, ding, ding... :)
So I decided to try and manually add an unload event handler to the source of each page that is loaded and see what happens.
So after the page loading is complete, I do:
/usr/bin/ld: warning: libicui18n.so.56, needed by /opt/Qt/5.6/gcc_64/lib/libQt5Core.so, may conflict with libicui18n.so.52
/usr/bin/ld: /home/alan/Desktop/qtwebkit-opensource-src-5.6.1/Source/WTF//.obj/wtf/unicode/icu/CollatorICU.o: undefined reference to symbol 'ucol_setAttribute_56'
/opt/Qt/5.6/gcc_64/lib/libicui18n.so.56: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make: *** [../../bin/jsc] Error 1
make: *** [sub-jsc-pro-make_first-ordered] Error 2
Well, needless to say that I am calling it a day. :) In the end, I have got a working solution, so I am 'happy' to accept that I don't and might never understand why I need to export a new PKG_CONFIG_PATH rather than modify it 'inline'...
However, if you are planning to write plugins yourself, you may find it easier to inject your conent into the page with QObject bridge. More complicated approach (but still more productive and likely more CPU-efficient than NPAPI way) is implementing your custom elements inside WebKit.
Could you specify what are you planning to achieve with plugin?
But if are using a latest i.e Qt WebEngine then you will need to update to Qt 5.6 where they have added new API's to do so. As per this doc.
We’ve also added a new Qt WebEngineCore module for new low-level APIs. This includes features such as support for custom URL schemes, intercepting and blocking network requests and for tracking and blocking cookies.
@luca yes you are right. :)
Just now I've tried to export the private key from the .p12 file with the openssl API. This key could be constructed into QSslKey object now. Thanks a lot.
But to configure in such a way is a little bit too complicated. Is there any class or method I can use, so that I can directly import the .p12 file into the QSslConfiguration object?
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.