On quinta-feira, 17 de março de 2016 14:28:34 PDT Larry Martell wrote:
> > If they are Macs, yes. You can also solve the problem by installing a
> > recent version of OpenSSL.
>
> Rebuilt Qt with -securetransport and it did not fix the problem.
Please check that QSslSocket::supportsSsl() returns
On Thu, Mar 17, 2016 at 11:39 AM, Thiago Macieira
wrote:
> On quinta-feira, 17 de março de 2016 09:39:44 PDT Larry Martell wrote:
>> 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 t
17.03.2016, 07:13, "Larry Martell" :
> On Wed, Mar 16, 2016 at 12:04 PM, Konstantin Tokarev
> wrote:
>> 16.03.2016, 18:39, "Larry Martell" :
>>> On Wed, Mar 16, 2016 at 6:29 AM, Konstantin Tokarev
>>> wrote:
16.03.2016, 02:15, "Larry Martell" :
> -How can I debug the Angular
On Thu, Mar 17, 2016 at 6:41 AM, Konstantin Tokarev wrote:
>
>
> 17.03.2016, 07:13, "Larry Martell" :
>> On Wed, Mar 16, 2016 at 12:04 PM, Konstantin Tokarev
>> wrote:
>>> 16.03.2016, 18:39, "Larry Martell" :
On Wed, Mar 16, 2016 at 6:29 AM, Konstantin Tokarev
wrote:
>16.0
16.03.2016, 18:39, "Larry Martell" :
> On Wed, Mar 16, 2016 at 6:29 AM, Konstantin Tokarev
> wrote:
>> 16.03.2016, 02:15, "Larry Martell" :
>>> -How can I debug the Angular code?
>>
>> QtWebKit has developer tools. You need to create QWebInspector, set
>> QWebPage to it,
>> and enable
On Wed, Mar 16, 2016 at 12:04 PM, Konstantin Tokarev wrote:
>
>
> 16.03.2016, 18:39, "Larry Martell" :
>> On Wed, Mar 16, 2016 at 6:29 AM, Konstantin Tokarev
>> wrote:
>>> 16.03.2016, 02:15, "Larry Martell" :
-How can I debug the Angular code?
>>>
>>> QtWebKit has developer tools. Yo
On quinta-feira, 17 de março de 2016 09:39:44 PDT Larry Martell wrote:
> 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
On Thu, Mar 17, 2016 at 8:11 AM, Larry Martell wrote:
> On Thu, Mar 17, 2016 at 6:41 AM, Konstantin Tokarev wrote:
>>
>>
>> 17.03.2016, 07:13, "Larry Martell" :
>>> On Wed, Mar 16, 2016 at 12:04 PM, Konstantin Tokarev
>>> wrote:
16.03.2016, 18:39, "Larry Martell" :
> On Wed, Mar 16,
On Wed, Mar 16, 2016 at 6:29 AM, Konstantin Tokarev wrote:
>
>
> 16.03.2016, 02:15, "Larry Martell" :
>> -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
16.03.2016, 02:15, "Larry Martell" :
> On Tue, Mar 15, 2016 at 12:45 PM, Thiago Macieira
> wrote:
>> On terça-feira, 15 de março de 2016 12:04:34 PDT Larry Martell wrote:
>>> > To make matters short, these two URLs are different:
>>> >
>>> > http://foo.bar.com:8000/#/workitem/12345
>>> >
>>
On terça-feira, 15 de março de 2016 20:12:25 PDT Thiago Macieira wrote:
> It's inside QtWebKit. Mac has another copy of it, inside its own WebKit
> framework.
Oh, QtScript has yet another copy of JSC.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source T
On terça-feira, 15 de março de 2016 21:42:24 PDT Larry Martell wrote:
> On Tue, Mar 15, 2016 at 9:14 PM, Thiago Macieira
>
> wrote:
> > On terça-feira, 15 de março de 2016 19:15:03 PDT Larry Martell wrote:
> >> So that led me to these questions:
> >>
> >> -What runs the JS code on the client?
>
On Tue, Mar 15, 2016 at 9:14 PM, Thiago Macieira
wrote:
> On terça-feira, 15 de março de 2016 19:15:03 PDT Larry Martell wrote:
>> So that led me to these questions:
>>
>> -What runs the JS code on the client?
>
> JavaScriptCore, WebKit's JS engine.
Is that part of Qt? I googled it, and it seems
On terça-feira, 15 de março de 2016 19:15:03 PDT Larry Martell wrote:
> So that led me to these questions:
>
> -What runs the JS code on the client?
JavaScriptCore, WebKit's JS engine.
> -Is there a cache for the JS code and is it the case that 8000/# will
> only actually go out on the wire if t
On Tue, Mar 15, 2016 at 12:45 PM, Thiago Macieira
wrote:
> On terça-feira, 15 de março de 2016 12:04:34 PDT Larry Martell wrote:
>> > To make matters short, these two URLs are different:
>> >
>> > http://foo.bar.com:8000/#/workitem/12345
>> >
>> > scheme = http
>> > authority = foo
On terça-feira, 15 de março de 2016 12:04:34 PDT Larry Martell wrote:
> > To make matters short, these two URLs are different:
> >
> > http://foo.bar.com:8000/#/workitem/12345
> >
> > scheme = http
> > authority = foo.bar.com:8000
> > path = /
> > fragment = /worki
On Tue, Mar 15, 2016 at 11:54 AM, Thiago Macieira
wrote:
> On terça-feira, 15 de março de 2016 11:45:12 PDT Larry Martell wrote:
>> >> QString urlStr = "http://foo.bar.com:8000/#/workitem/12345";;
>> >> QUrl reportUrl(urlStr);
>> >
>> > So I'm assuming you're misusing the term and that you
On terça-feira, 15 de março de 2016 11:45:12 PDT Larry Martell wrote:
> >> QString urlStr = "http://foo.bar.com:8000/#/workitem/12345";;
> >> QUrl reportUrl(urlStr);
> >
> > So I'm assuming you're misusing the term and that you did want a fragment.
>
> I realize that using # is typically
On Tue, Mar 15, 2016 at 11:37 AM, Thiago Macieira
wrote:
> On terça-feira, 15 de março de 2016 07:04:49 PDT Larry Martell wrote:
>> Sorry for not giving more details. It's not a fragment - it's an
>
> You say "it's not a fragment" and then your URL uses a fragment:
>
>> QString urlStr = "http:
On terça-feira, 15 de março de 2016 07:04:49 PDT Larry Martell wrote:
> Sorry for not giving more details. It's not a fragment - it's an
You say "it's not a fragment" and then your URL uses a fragment:
> QString urlStr = "http://foo.bar.com:8000/#/workitem/12345";;
> QUrl reportUrl(urlStr
On Tue, Mar 15, 2016 at 1:32 AM, Thiago Macieira
wrote:
> On segunda-feira, 14 de março de 2016 18:30:13 PDT Larry Martell wrote:
>> We have an app that emits a URL with a hashtag in it (#) and that is
>> processed by some Angular JS code we have
>> (https://docs.angularjs.org/guide/$location). Th
15.03.2016, 01:31, "Larry Martell" :
> We have an app that emits a URL with a hashtag in it (#) and that is
> processed by some Angular JS code we have
> (https://docs.angularjs.org/guide/$location). That URL is emitted with
> setUrl. It works fine on a Mac, but on Windows it acts as if the #
> w
On segunda-feira, 14 de março de 2016 18:30:13 PDT Larry Martell wrote:
> We have an app that emits a URL with a hashtag in it (#) and that is
> processed by some Angular JS code we have
> (https://docs.angularjs.org/guide/$location). That URL is emitted with
> setUrl. It works fine on a Mac, but o
We have an app that emits a URL with a hashtag in it (#) and that is
processed by some Angular JS code we have
(https://docs.angularjs.org/guide/$location). That URL is emitted with
setUrl. It works fine on a Mac, but on Windows it acts as if the #
were not there. Googling I found this:
https://bu
24 matches
Mail list logo
