On Thu, Mar 17, 2016 at 8:11 AM, Larry Martell <larry.mart...@gmail.com> wrote: > On Thu, Mar 17, 2016 at 6:41 AM, Konstantin Tokarev <annu...@yandex.ru> wrote: >> >> >> 17.03.2016, 07:13, "Larry Martell" <larry.mart...@gmail.com>: >>> On Wed, Mar 16, 2016 at 12:04 PM, Konstantin Tokarev <annu...@yandex.ru> >>> wrote: >>>> 16.03.2016, 18:39, "Larry Martell" <larry.mart...@gmail.com>: >>>>> On Wed, Mar 16, 2016 at 6:29 AM, Konstantin Tokarev <annu...@yandex.ru> >>>>> wrote: >>>>>> 16.03.2016, 02:15, "Larry Martell" <larry.mart...@gmail.com>: >>>>>>> -How can I debug the Angular code? >>>>>> >>>>>> QtWebKit has developer tools. You need to create QWebInspector, set >>>>>> QWebPage to it, >>>>>> and enable QWebSettings::DeveloperExtrasEnabled >>>>>> >>>>>> You will get error console, JS debugger, and other goodies. >>>>> >>>>> This sounds very promising but I can't quite figure out how to use it. >>>>> >>>>> I have this JS code that's somehow downloaded (I assume by nginx). How >>>>> do I integrate QWebInspector and QWebPage into the Qt app so they can >>>>> access that code? >>>> >>>> In the beginning you've mentioned that you have QWebView. That's enough, >>>> you can get QWebPage using page() method, you can create QWebInspector as >>>> a separate widget (see code example in docs), call its setPage() method >>>> and show it somewhere >>> >>> Thanks. This is what I was doing before: >>> >>> ui->webView->setUrl(url); >>> >>> And I commented that out and I have this now: >>> >>> Dialog = new QDialog(this); >>> ui->webView->setPage(url); >> >> It should be >> >> ui->webView->setUrl(url); > > OK, I'll try that. I thought setUrl did a show and I only wanted to > set the url and not show it at that point.
Thanks, I was able to get this to work. It's very cool and oh so useful. And what I saw in the console was: GET https://code.jquery.com/jquery-2.1.4.min.js SSL handshake failed A couple of days back Thiago said: > Check if you have OpenSSL available. It might be that the requests fail > because they are HTTPS and there's no SSL support. > > If you're compiling on Mac from source, you may try the -securetransport > option, which uses the Mac API instead of OpenSSL. So I want to understand this - Is this error occurring because these machines do not have OpenSSL installed? Would rebuilding Qt with that option fix this? _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest