Re: [Development] Let's please drop MSVC 2013 for 5.10

On Friday, 16 June 2017 16:35:54 PDT André Pönitz wrote: > On Fri, Jun 16, 2017 at 12:52:24PM -0700, Thiago Macieira wrote: > > Here's a tricky question: how do you create a QStringLiteral with > > non-ASCII > > characters that will work on all our supported compilers? > > I don't have to, unless

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Fri, Jun 16, 2017 at 12:52:24PM -0700, Thiago Macieira wrote: > Here's a tricky question: how do you create a QStringLiteral with non-ASCII > characters that will work on all our supported compilers? I don't have to, unless I have profiler supported evidence that it matters. In the common cas

Re: [Development] "Getting started" tutorials (Was: Examples and Demos in qtdoc)

> On 16 Jun 2017, at 16:17, Sze Howe Koh wrote: > > On 15 June 2017 at 01:29, Tuukka Turunen wrote: > > Hi, > > > > Yes, we would like to overall improve the examples. This is related to > > having a new repo for examples, but not fully the same thing. Main goal in > > example improvement bei

Re: [Development] CI problems

On Thursday, 15 June 2017 23:44:08 PDT Tony Sarajärvi wrote: > Hi > > We're facing an unknown problem with contacting our RHEL 6.6 virtual > machines. This stops all CI from progressing. We're investigating. Pretty sure that either what caused this problem or the solution is the reason why tst_Q

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

On Friday, 16 June 2017 13:23:07 PDT Thiago Macieira wrote: > QDEBUG : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) > QHostAddress("fe80::250:56ff:feab:4818%eth1") > FAIL! : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) > '(neutralReadSpy.count() > > 0)' returned FALSE. () > > Loc: [../tst_qud

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Friday, 16 June 2017 13:10:10 PDT Henry Skoglund wrote: > That question reminds me of the discussion last August > http://lists.qt-project.org/pipermail/interest/2016-August/023882.html > about Unicode code points in MSVC and how to fix so that > tr("Coördinaat") or tr("Co\u00F6rdinaat"); worked

[Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

QDEBUG : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) QHostAddress("fe80::250:56ff:feab:4818%eth1") FAIL! : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) '(neutralReadSpy.count() > 0)' returned FALSE. () Loc: [../tst_qudpsocket.cpp(1600)] This test was passing on Linux without a problem for

Re: [Development] Let's please drop MSVC 2013 for 5.10

On 2017-06-16 21:52, Thiago Macieira wrote: On Friday, 16 June 2017 11:14:20 PDT André Pönitz wrote: On Thu, Jun 15, 2017 at 04:07:03PM -0700, Thiago Macieira wrote: character set. Without the /utf-8 option added in MSVC 2015 Update 2, the conversion fails and the compiler prints: warning C456

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Fri, Jun 16, 2017 at 07:18:25PM +, Shawn Rutledge wrote: > > > On 16 Jun 2017, at 11:14, André Pönitz wrote: > > > > On Thu, Jun 15, 2017 at 04:07:03PM -0700, Thiago Macieira wrote: > >> character set. Without the /utf-8 option added in MSVC 2015 Update 2, the > >> conversion fails and t

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Friday, 16 June 2017 11:14:20 PDT André Pönitz wrote: > On Thu, Jun 15, 2017 at 04:07:03PM -0700, Thiago Macieira wrote: > > character set. Without the /utf-8 option added in MSVC 2015 Update 2, the > > conversion fails and the compiler prints: > > > > warning C4566: character represented by un

Re: [Development] Let's please drop MSVC 2013 for 5.10

> On 16 Jun 2017, at 11:14, André Pönitz wrote: > > On Thu, Jun 15, 2017 at 04:07:03PM -0700, Thiago Macieira wrote: >> character set. Without the /utf-8 option added in MSVC 2015 Update 2, the >> conversion fails and the compiler prints: >> >> warning C4566: character represented by universal

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Thu, Jun 15, 2017 at 04:07:03PM -0700, Thiago Macieira wrote: > character set. Without the /utf-8 option added in MSVC 2015 Update 2, the > conversion fails and the compiler prints: > > warning C4566: character represented by universal-character-name '\u0431' > cannot be represented in the cu

Re: [Development] Let's please drop MSVC 2013 for 5.10

> On 16 Jun 2017, at 18:11, Thiago Macieira wrote: > > On Thursday, 15 June 2017 16:07:03 PDT Thiago Macieira wrote: >> We have not one, not two, but THREE integration failures TODAY alone caused >> by that compiler failing to meet what we've come to expect from C++11. This >> is going to happen

Re: [Development] QtScript (deprecated) vs QJSEngine and reasons why QJSEngine isn't up to scratch

16.06.2017, 19:45, "NAVSYSTEMS LTD" : > NB I also use WebKit and am looking at the QWebEngine replacement but thats a > whole other story and is similar and also rather unpleasant. http://lists.qt-project.org/pipermail/development/2017-May/029795.html Sorry, I don't have anything to comment on

[Development] QtScript (deprecated) vs QJSEngine and reasons why QJSEngine isn't up to scratch

I have been using QtScript for many years (along with many other qt modules). Porting from QtScript to QJSEngine is clearly not trivial especially when I have multiple QScriptEngine uses in many processes but thats specific to my use not general. One very nice feature in QtScript is the debugger

Re: [Development] "Getting started" tutorials (Was: Examples and Demos in qtdoc)

> > On the topic of showing users "how to use Qt" and "leverage our tooling", > I feel that our "getting started" tutorials/examples need some love too. > > IMHO, the "Getting Started" tutorial from Qt 4.3 ( > https://doc.qt.io/archives/4.3/tutorial-t1.html) is more accessible to > beginners than h

Re: [Development] Development Digest, Vol 69, Issue 22 - Getting Started Tutorials

Sze-Howe Wrote: > On the topic of showing users "how to use Qt" and "leverage our tooling", I > feel that our "getting started" tutorials/examples need some love too. > > IMHO, the "Getting Started" tutorial from Qt 4.3 ( > https://doc.qt.io/archives/4.3/tutorial-t1.html) is more accessible to >

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Thursday, 15 June 2017 16:07:03 PDT Thiago Macieira wrote: > We have not one, not two, but THREE integration failures TODAY alone caused > by that compiler failing to meet what we've come to expect from C++11. This > is going to happen again and again. Fourth reason, just over 24 hours since th

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Thursday, 15 June 2017 23:57:28 PDT Santtu Ahonen wrote: > We also have paying customers whom may be using MSVC2013 and whom are not on > this list, thus we need to look at this from business side too. Not ready > yet to give my vote for dropping it but will get back to this in due time. This i

[Development] "Getting started" tutorials (Was: Examples and Demos in qtdoc)

On 15 June 2017 at 01:29, Tuukka Turunen wrote: > Hi, > > Yes, we would like to overall improve the examples. This is related to having a new repo for examples, but not fully the same thing. Main goal in example improvement being to make them more useful in what they are: examples of how to use Qt

Re: [Development] CI problems

Hi All seem to be working again. We also had some problems with servers not seeing LUNs for some reason, and we fixed those as well. -T From: Development [mailto:development-bounces+tony.sarajarvi=qt...@qt-project.org] On Behalf Of Tony Sarajärvi Sent: perjantai 16. kesäkuuta 2017 9.44 To: de

Re: [Development] Examples and Demos in qtdoc

On 15 Jun 2017, at 15:23, Mitch Curtis mailto:mitch.cur...@qt.io>> wrote: -Original Message- From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt- project.org] On Behalf Of Joerg Bornemann Sent: Thursday, 15 June 2017 9:54 AM To: Pasi K

Re: [Development] Let's please drop MSVC 2013 for 5.10

On Friday 16 June 2017 06:57:28 Santtu Ahonen wrote: > >From: Shawn Rutledge > > > >> On 15 Jun 2017, at 16:07, Thiago Macieira > >> wrote: > >> > >> We have not one, not two, but THREE integration failures TODAY alone > >> caused by that compiler failing to meet what we've come to expect from >

Re: [Development] Dropping older compilers for Qt 5.10 (was: Qt 5.10 pre-built bunaries)

On Fri, Jun 9, 2017 at 10:46 PM, Ville Voutilainen < ville.voutilai...@gmail.com> wrote: > > So, what's your take on gcc versions? You seemed hesitant to drop > support for QNX 6 > here: http://lists.qt-project.org/pipermail/development/2017- > June/030113.html > Are you suggesting we drop support