Qt WebKit

i got the solution..... i understood exactly why should i call , reindexDocumentation for the search engine. Thanks....!

That's something I can't answer, I haven't worked on the internals of the V4 engine. You should rather ask this on the development mailing list. You'll find there Qt's developers/maintainers (this forum is more user oriented). There's also the #qt IRC channel

Hi, QtWebKit is not available on Android (nor iOS for that matter) because of one limitation of the platform: you have to use a native web view. For that, you can use the QtWebView module. It should give you a native web view to integrate to your application. Hope it helps

@maximo the problem is that page`s url is not changing when song data changes. I solved the problem by checking song data using a timer and emiting my own signal.

@shadownt I understand that the answer is a bit late, but maybe it will help someone. You can use the second parameter in QWebView::setHtml m_webView->setHtml( "html content here", QUrl("http://google.com")) now the window.location will have the following value: { Location hash: "" host: "google.com" hostname: "google.com" href: "http://google.com/" origin: "http://google.com" pathname: "/" port: "" protocol: "http:" search: "" proto: LocationPrototype }

Hi, Small correction for @maximo, there's no support for QtWebKit on iOS since it's not using the native webkit. @pullo You don't need to revert that patch, you can simply clone the corresponding repositories. Now since you could build 5.5.1. Was it from git or from Qt's source package ?

@maximo Thanks for the input. I'll look into that.

@Heiko93 I experimented with the Qt 5.5 tech preview of the QML QtWebKit (not to be confused with the embedded webkit in QWebView widget). I found some quirks with it that make it pretty much unusable in a normal production environment. I hope these quirks don't continue in the next version of Qt after Qt 5.5. I like the strategy of it, however, because if you want to get an iOS app approved, the Apple Store requires that you use native webkit that's in the operating system, not ship with Chromium or an embedded webkit. It also makes sense on Android, too, because why make your APK package have to install its own Chromium or embedded webkit (making it pretty fat) when there's already a webkit in the OS? As for OSX, it also has an embedded webkit in the OS (Safari uses it), so it makes a slimmer install if you can use QtWebView (native webkit) instead of QWebView (embedded webkit) or QtWebEngine (embedded Chromium). For now, unless the direction changes in a future version of Qt beyond 5.5, this looks like the most stable route: OSX. Build a widget-based app with QWebView widget. It's an embedded webkit, but she works and doesn't have the quirks. Plus, it's got a neato C++ bridge. I'm not certain yet whether Apple will allow an embedded webkit in their Apple Store for OSX. I'm waiting on their callback. The docs for Apple Store seem to point out the webkit issue is only for iOS, not OSX. iOS (and want to get it approved in the Apple Store). If you can live with the quirks of QtWebView in QML, you'll get native webkit support from the iOS operating system. It makes a thinner install, too. iOS (and don't care about the Apple Store). Use the embedded webkit from Qt with a widget-based app and QWebView widget. Android (and care about Google Play approval). Use the same technique for iOS and Apple Store approval -- native webkit with QtWebView. Android (and don't care about Google Play approval). Use the same technique for iOS and not caring about Apple Store approval -- embedded webkit with QWebView. Windows or Linux. These don't have an embedded webkit that I'm aware of. So, use QWebView (the embedded webkit) widget in a widget-based application for now, and migrate to the QtWebEngine later on. As for whether QtWebEngine will have quirks or not -- I still wait to see. When I'm talking quirks -- things like scrollbars that disappear when you want them, controls that don't work, controls that look wonky, not able to disable the rightclick context menu, not able to disable some keystrokes that make the pages go backward and forward, and not able to disable the zoom effect when you doubleclick the page.

@kmsharad83 This is what I do in jQuery. You can adapt it to your needs: $(document).ready(function(){ // Prevent anchor links and buttons and .nodrag items from being dragged $('A,BUTTON,.nodrag,IMG') .css('-moz-user-select','none') .css('-webkit-user-select','none') .bind('selectstart', function(e) { e.preventDefault(); return false; }) .bind('draggesture', function(e) { e.preventDefault(); return false; }) .bind('draggable', function(e) { e.preventDefault(); return false; }) .bind('dragstart', function(e) { e.preventDefault(); return false; }); });

@ThatDud3 However, my test code only loads "about:blank", I think, which has no resource to cache. I am not still understanding why this code incurs infinite virtual memory leak...

Any update on this

Thank you for your reply. By the way, How Will may be read normally (Server certificate) certificate file? Please tell someone how. Thanks a lot in advance.

@Vizi See there: http://doc.qt.io/qt-5/qthread.html#details

@jramm, signals are methods. You can declare a signal as Q_INVOKABLE and call it from JS.