Re: [Development] http://testresults.qt.io/ci/status/ stale?

2016-03-21 Thread Liang Qi
The status of new CI: http://testresults.qt.io/coin/ On 21 March 2016 at 18:19, MrMstormo . wrote: > > Looks like > http://testresults.qt.io/ci/status/ > is stale? All reports are erroring out, and there's no reports for 5.6, > 5.7 etc? > > Is the CI system on an early Easter break? :) > > -

Re: [Development] Source compatibility for third parties using auto (Was: What qtbase looks like with extensive use of auto)

2016-03-21 Thread Marc Mutz
On Tuesday 22 March 2016 03:01:44 Stephen Kelly wrote: > Thiago Macieira wrote: > > On sábado, 19 de março de 2016 19:02:08 GMT Stephen Kelly wrote: > >> Hi, > >> > >> > >> > >> In case you missed it, I wrote an auto-modernizer > >> > >> https://steveire.wordpress.com/2016/03/19/aaargh > >> >

[Development] Source compatibility for third parties using auto (Was: What qtbase looks like with extensive use of auto)

2016-03-21 Thread Stephen Kelly
Thiago Macieira wrote: > On sábado, 19 de março de 2016 19:02:08 GMT Stephen Kelly wrote: >> Hi, >> >> In case you missed it, I wrote an auto-modernizer >> >> https://steveire.wordpress.com/2016/03/19/aaargh >> >> It is not quite AAA, as it doesn't convert >> >> QString s; >> >>

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

2016-03-21 Thread Allan Sandfeld Jensen
On Monday 21 March 2016, René J. V. Bertin wrote: > For further comparison, here's a screenshot showing > > CoreText vs Cocoa+Freetype vs XCB+Freetype+Fontconfig > > all on OS X, using a theme & style based on QtCurve. > > The XCB+Freetype rendering is hands-down the easiest on the eyes for me,

Re: [Development] What qtbase looks like with extensive use of auto

2016-03-21 Thread Thiago Macieira
On sábado, 19 de março de 2016 19:02:08 GMT Stephen Kelly wrote: > Hi, > > In case you missed it, I wrote an auto-modernizer > > https://steveire.wordpress.com/2016/03/19/aaargh > > It is not quite AAA, as it doesn't convert > > QString s; > > into > > auto s = QString(); Thanks Stephen

Re: [Development] What qtbase looks like with extensive use of auto

2016-03-21 Thread André Pönitz
On Sat, Mar 19, 2016 at 07:02:08PM +0100, Stephen Kelly wrote: > It is not quite AAA, as it doesn't convert > > QString s; > > into > > auto s = QString(); > I used it to port qtbase to an extensive use of auto: > > https://github.com/steveire/qtbase/commits/aaa > > This isn't something I

Re: [Development] What qtbase looks like with extensive use of auto

2016-03-21 Thread Mandeep Sandhu
On Sat, Mar 19, 2016 at 11:02 AM, Stephen Kelly wrote: > Hi, > > In case you missed it, I wrote an auto-modernizer > > https://steveire.wordpress.com/2016/03/19/aaargh Thanks for this blog post. It made me smile...and also auto aware! (yes!! I did it too!) :) -mandeep > > It is not quite AAA,

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

2016-03-21 Thread René J . V . Bertin
For further comparison, here's a screenshot showing CoreText vs Cocoa+Freetype vs XCB+Freetype+Fontconfig all on OS X, using a theme & style based on QtCurve. The XCB+Freetype rendering is hands-down the easiest on the eyes for me, though that's of course all in the eye of the beholder. It'd be

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

2016-03-21 Thread Allan Sandfeld Jensen
On Monday 21 March 2016, René J. V. Bertin wrote: > Allan Sandfeld Jensen wrote: > > If the right one is freetype, it looks like it didn't disable font gamma- > > It is. > > > correction. We usually disable that when using freetype, since they don't > > have stem darkening, and thus gets must pal

Re: [Development] What qtbase looks like with extensive use of auto

2016-03-21 Thread Richard Moore
There are certainly quite a few areas of the qtnetwork patch that I think make the code significantly easier to read. I don't think I'd apply everything from it, eg. some of the changes from int to auto just make things less clear in my eyes, but other parts are a massive win. Thanks for sharing th

Re: [Development] What qtbase looks like with extensive use of auto

2016-03-21 Thread Stephen Kelly
Matthew Woehlke wrote: > On 2016-03-19 14:02, Stephen Kelly wrote: >> In case you missed it, I wrote an auto-modernizer >> >> https://steveire.wordpress.com/2016/03/19/aaargh > > Thanks for sharing. I admiringly adore all the abounding (and artistic) > alliteration adorning the article. (Sorry,

[Development] http://testresults.qt.io/ci/status/ stale?

2016-03-21 Thread MrMstormo .
Looks like http://testresults.qt.io/ci/status/ is stale? All reports are erroring out, and there's no reports for 5.6, 5.7 etc? Is the CI system on an early Easter break? :) -- .marius ___ Development mailing list Development@qt-project.org http://

Re: [Development] What qtbase looks like with extensive use of auto

2016-03-21 Thread Matthew Woehlke
On 2016-03-19 14:02, Stephen Kelly wrote: > In case you missed it, I wrote an auto-modernizer > > https://steveire.wordpress.com/2016/03/19/aaargh Thanks for sharing. I admiringly adore all the abounding (and artistic) alliteration adorning the article. (Sorry, couldn't think how to avoid "the"

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

2016-03-21 Thread René J . V . Bertin
Allan Sandfeld Jensen wrote: > If the right one is freetype, it looks like it didn't disable font gamma- It is. > correction. We usually disable that when using freetype, since they don't have > stem darkening, and thus gets must paler text-colors when fonts are > antialiased. Do you disable i

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

2016-03-21 Thread Allan Sandfeld Jensen
On Monday 21 March 2016, René J.V. Bertin wrote: > On Friday March 18 2016 14:15:32 Sergio Martins wrote: > > To get parameters passed to QCocoaIntegration::QCocoaIntegration(), you > > should use -platform cocoa:fontengine=freetype, which I haven't tried, > > but similar works for me on Windows.

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

2016-03-21 Thread René J . V . Bertin
Konstantin Tokarev wrote: >> So how am I supposed to invoke generate-forwarding-headers.pl ? > > No, it should be execute as a part of build process So, it is as I feared. When I execute qmake and then make manually from a terminal generate-forwarding-headers.pl is called as it apparently shou

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Giuseppe D'Angelo
On Mon, Mar 21, 2016 at 3:01 PM, André Somers wrote: > Are we following Sean Parent though? Because if we are, we better start > thinking about also replacing our QObject parent/child stuff with some > external forest data structure in the future... Please, can we avoid thread derailment again? :

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread André Somers
Op 21/03/2016 om 14:25 schreef Marc Mutz: On Monday 21 March 2016 13:38:43 Sean Harmer wrote: On Monday 21 March 2016 12:23:44 Poenitz Andre wrote: It's to support one-to-many delivery of an event-like object to backends potentially running on multiple threads concurrently. The type is not a Q

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Marc Mutz
On Monday 21 March 2016 13:18:18 Sean Harmer wrote: > On Monday 21 March 2016 12:44:34 Marc Mutz wrote: > > On Monday 21 March 2016 12:07:24 Poenitz Andre wrote: > > > Marc Mutz wrote: > > > > I said then and I repeat it now that imho template aliases are not > > > > interesting for library develo

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Poenitz Andre
Sean Harmer wrote: > On Monday 21 March 2016 12:23:44 Poenitz Andre wrote: > > I will argue that if user code looks ugly by default, or needs one specific, > > controversial coding style when using an API, the API is bad. > > > > A possible question here is why there's a need to have the QSharedP

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Marc Mutz
On Monday 21 March 2016 13:38:43 Sean Harmer wrote: > On Monday 21 March 2016 12:23:44 Poenitz Andre wrote: > > Marc Mutz wrote: > > > On Monday 21 March 2016 12:07:24 Poenitz Andre wrote: > > > > Marc Mutz wrote: > > > > > I said then and I repeat it now that imho template aliases are not > > >

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Sean Harmer
On Monday 21 March 2016 12:23:44 Poenitz Andre wrote: > Marc Mutz wrote: > > On Monday 21 March 2016 12:07:24 Poenitz Andre wrote: > > > Marc Mutz wrote: > > > > I said then and I repeat it now that imho template aliases are not > > > > interesting for library development. In particular, I don't

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Poenitz Andre
Marc Mutz wrote: > On Monday 21 March 2016 12:07:24 Poenitz Andre wrote: > > Marc Mutz wrote: > > > I said then and I repeat it now that imho template aliases are not > > > interesting for library development. In particular, I don't think > > > something like > > > > > > > > > template > > > > >

Re: [Development] [OS X] next Qt 5.6.0 question : Freetype (building with -fontconfig)?

2016-03-21 Thread René J . V . Bertin
On Friday March 18 2016 14:15:32 Sergio Martins wrote: > To get parameters passed to QCocoaIntegration::QCocoaIntegration(), you > should > use -platform cocoa:fontengine=freetype, which I haven't tried, but similar > works for me on Windows. FWIW, here's a small preview of CoreText vs. Freet

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Sean Harmer
On Monday 21 March 2016 12:44:34 Marc Mutz wrote: > On Monday 21 March 2016 12:07:24 Poenitz Andre wrote: > > Marc Mutz wrote: > > > I said then and I repeat it now that imho template aliases are not > > > interesting for library development. In particular, I don't think > > > something like > > >

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Marc Mutz
On Monday 21 March 2016 12:07:24 Poenitz Andre wrote: > Marc Mutz wrote: > > I said then and I repeat it now that imho template aliases are not > > interesting for library development. In particular, I don't think > > something like > > > > > > > template > > > > > using QNodeCreatedChangePtr = >

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Poenitz Andre
Marc Mutz wrote: > I said then and I repeat it now that imho template aliases are not interesting > for library development. In particular, I don't think something like > > > > > template > > > > using QNodeCreatedChangePtr = QSharedPointer>; > > should be part of an API of a library. We have a

Re: [Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Marc Mutz
On Monday 21 March 2016 10:46:40 Sean Harmer wrote: > On Sunday 20 March 2016 18:28:37 Thiago Macieira wrote: > > On domingo, 20 de março de 2016 12:07:01 GMT Sean Harmer wrote: > > > Hi, > > > > > > Can MSVC 2012 configurations be removed from the CI please? My > > > understanding is that this co

[Development] Allowed C++11 features [was: Re: Re: MSVC2012 in CI]

2016-03-21 Thread Sean Harmer
On Sunday 20 March 2016 18:28:37 Thiago Macieira wrote: > On domingo, 20 de março de 2016 12:07:01 GMT Sean Harmer wrote: > > Hi, > > > > Can MSVC 2012 configurations be removed from the CI please? My > > understanding is that this compiler was only kept around to support > > Windows EC but that t

Re: [Development] Problems with QtWebKit 5.6 / Please do not remove QtWebkit from 5.6 official binaries

2016-03-21 Thread Koehne Kai
> -Original Message- > From: Development [mailto:development- > bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of > Adrian Jakel > Sent: Sunday, March 20, 2016 7:00 PM > To: development@qt-project.org > Subject: Re: [Development] Problems with QtWebKit 5.6 / Please do not >