Re: [Development] Upcoming Jira outage (9 Nov 2:00-4:00 UTC)

2016-11-08 Thread Alexander Blasche
Hi, The changes are completed.You may need to clean the cache to load the site. Compression was enabled during the changes,see https://bugreports.qt.io/browse/QTJIRA-300 -- Alex From: Development

Re: [Development] [HiDPI] Rethinking the scaling algorithm

2016-11-08 Thread Allan Sandfeld Jensen
On Tuesday 08 November 2016, Niccolò Belli wrote: > 1) Always round down. With your current formula a 145ppi screen gets scaled > by a 2x factor, while every other toolkit (GTK3 for example[3]) starts > scaling at 192ppi. This is also what people expect and it would return the > correct 2x scaling

Re: [Development] [HiDPI] Rethinking the scaling algorithm

2016-11-08 Thread Thiago Macieira
Em terça-feira, 8 de novembro de 2016, às 15:57:40 CST, Niccolò Belli escreveu: > 1) Always round down. With your current formula a 145ppi screen gets scaled > by a 2x factor, while every other toolkit (GTK3 for example[3]) starts > scaling at 192ppi. This is also what people expect and it would

Re: [Development] QtQuickControls for desktop: what's the plan?

2016-11-08 Thread Jake Petroules
> On Nov 8, 2016, at 1:45 AM, Marco Martin wrote: > > On Tuesday 08 November 2016, Alberto Mardegan wrote: >>> Even if is still incomplete (and are things that unfortunately can't be >>> fully styled yet in a fully desktop friendly way) it seems to work >>> remarkably well.

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

2016-11-08 Thread Louai Al-Khanji
+1 for qt/quips, I don't think of it as a web site thing either. -Louai _ From: Kai Koehne > Sent: Tuesday, November 8, 2016 3:48 AM Subject: Re: [Development] QCS2016 Session Notes - QUIPs for Qt To: Oswald Buddenhagen

Re: [Development] Qt Charts poor dynamic/resolution with OpenGL

2016-11-08 Thread Jeandet Alexis
Hi Uwe, Le mardi 08 novembre 2016 à 15:06 +, Uwe Rathmann a écrit : > On Tue, 08 Nov 2016 13:30:45 +0100, Jeandet Alexis wrote: > > > Our goal is to improve QtCharts to be able to use it in our > > scientific > > softwares. So we need to improve the current dynamic with OpenGL > > and/or > >

Re: [Development] Qt Charts poor dynamic/resolution with OpenGL

2016-11-08 Thread Uwe Rathmann
On Tue, 08 Nov 2016 13:30:45 +0100, Jeandet Alexis wrote: > Our goal is to improve QtCharts to be able to use it in our scientific > softwares. So we need to improve the current dynamic with OpenGL and/or > improve performances of non OpenGL plots. Have you ever considered to use a 3rd party

Re: [Development] [HiDPI] Rethinking the scaling algorithm

2016-11-08 Thread Niccolò Belli
On martedì 8 novembre 2016 15:57:40 CET, Niccolò Belli wrote: [2]https://bpaste.net/show/e2f39fad5f5e Wrong link for the EDID, this is the correct one: https://bpaste.net/show/0e34f12832d9 ___ Development mailing list Development@qt-project.org

[Development] [HiDPI] Rethinking the scaling algorithm

2016-11-08 Thread Niccolò Belli
Hi, My laptop's monitor is a 13" with a 16:9 aspect ratio and a 3200x1800 resolution. As you can see[1] the EDID[2] is perfectly correct. QT computes the scaling factor using a formula like this: scaling_factor=qRound(yourDpi/96) This is far from ideal in my opinion, because if we want to scale

Re: [Development] Qt Charts poor dynamic/resolution with OpenGL

2016-11-08 Thread Jeandet Alexis
Hi Qt devs, To continue on this topic, in my lab we plan to take an intern to work on this. It would be a 6 month Master degree internship, starting around February 2017. Does QtCharts maintainers/experts have some time to help us to advise our intern? It would just be for short discussions like

[Development] CI has workitem creation problems

2016-11-08 Thread Tony Sarajärvi
Hi all You all might have noticed the problems we're facing with the CI not able to produce workitems. The culprit is most likely a buggy lru_cache in Python. We've tried a few work-arounds, but as you've seen none of them have really made a difference. The buggy lru_cache came with a new

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

2016-11-08 Thread Kai Koehne
> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Tuesday, November 08, 2016 11:15 AM > To: development@qt-project.org > Subject: Re: [Development] QCS2016 Session Notes - QUIPs for Qt > > On

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

2016-11-08 Thread Oswald Buddenhagen
On Tue, Nov 08, 2016 at 09:11:23AM +, Lars Knoll wrote: > Yes, let’s get the repo created and this whole thing off the ground. > so, anyone has a concrete proposal for a fully qualified repository name? www/quips? > As noted, we need a better way to document results of discussions,

Re: [Development] QtQuickControls for desktop: what's the plan?

2016-11-08 Thread Marco Martin
On Tuesday 08 November 2016, Alberto Mardegan wrote: > > Even if is still incomplete (and are things that unfortunately can't be > > fully styled yet in a fully desktop friendly way) it seems to work > > remarkably well. > > That looks smart and simple! Any plans for submitting that to Qt, maybe

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

2016-11-08 Thread Lars Knoll
Yes, let’s get the repo created and this whole thing off the ground. As noted, we need a better way to document results of discussions, decisions and processes. Grepping through a mailing list archive and trying to figure out which opinion prevailed in the end is not that ;-) Cheers, Lars On

[Development] Upcoming Jira outage (9 Nov 2:00-4:00 UTC)

2016-11-08 Thread Alexander Blasche
Hi, Due to maintenance on the Jira machine, bugreports.qt.io will be temporarily unavailable on November 9 , 2:00 AM ~ 4:00AM UTC+0 We apologize for the inconvenience that this might cause. -- Alex ___ Development mailing list

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

2016-11-08 Thread Edward Welbourne
Louai Al-Khanji said: > this is not a bureaucratization process. It is about having a way to document the final conclusions of discussions we already have. In the process, it shall also force us to be explicit and leave fewer dangling ambiguities, where different parties have subtly different