Re: [Development] Proposing David Faure as maintainer of Qt Models

I added the "Item Models" component to Jira and the maintainer wiki, -- ALex From: Development on behalf of Lars Knoll Sent: Wednesday, 2 May 2018 9:24:39 AM To: Qt

Re: [Development] Fornux C++ Superset

Thiago Macieira wrote: > On Wednesday, 2 May 2018 13:45:46 PDT Phil Bouchard wrote: >> So what do you think Qt? Are you: >> >> 1) Not interested or whatsoever >> 2) Interested to give a trial version a shot >> 3) You get the idea already and might consider it > >

Re: [Development] Fornux C++ Superset

On Wednesday, 2 May 2018 13:45:46 PDT Phil Bouchard wrote: > So what do you think Qt? Are you: > > 1) Not interested or whatsoever > 2) Interested to give a trial version a shot > 3) You get the idea already and might consider it Probably (1). -- Thiago Macieira - thiago.macieira (AT)

Re: [Development] Fornux C++ Superset

Phil Bouchard wrote: On the other hand I am more targeting QML because QWidgets are fine already so I assume: - QML compiler converts QML into C++ - Fornux C++ Superset could then inject its memory manager - Compile the resulting code It’s just a matter of making sure QML

[Development] QTest qWaitForWindowExposed and qWaitForWindowActive (was: Consistently flaky test QTabWidget test)

> On 2 May 2018, at 09:29, Thiago Macieira wrote: > > FAIL! : tst_QTabWidget::paintEventCount() Compared values are not the same >Actual (tab2->count): 2 >Expected (1) : 1 >Loc: [tst_qtabwidget.cpp(573)] > [on macOS 10.12] Hi, I recently

Re: [Development] Consistently flaky test QTabWidget test

tst_QWindow::requestUpdate is also causing problems. Two patches to solve that: https://codereview.qt-project.org/#/c/228024/ https://codereview.qt-project.org/#/c/228027/

[Development] Jira changes going forward

Hi, there are quite a few changes to Jira on my todo list. Some of them result from some internal TQtC process changes (related to public requirements mgmt) and others were put forward by individuals with a keen interest in improving things (thank you for that). Unfortunately some of proposals

Re: [Development] Proposing Orgad Shaneh as Maintainer of Version Control modules in Qt Creator

+1 Orgad is doing a great job, about time that we make that defacto state official! :) > On 2. May 2018, at 12:14, Tobias Hunger wrote: > > Hello, > > I want to propose Orgad Shaneh as maintainer of the version control related > modules in Qt Creator. > > So far I have

Re: [Development] Proposing David Faure as maintainer of Qt Models

On 2018-05-02 08:24, Lars Knoll wrote: Currently that's true. But if we have separate maintainers for the item models and views, we might want to split it. Yes, please split. "Item Models" is also used with QtQuick so makes sense to separate it from QWidgets. Regrads, -- Sérgio Martins |

Re: [Development] Fornux C++ Superset

On 05/01/2018 09:27 AM, Phil Bouchard wrote: Michael Corcoran wrote: It's not really a "superset" if it doesn't support all of the features of the original language, much less core features such as nested structs... You may like to revisit that naming choice. I

Re: [Development] Proposing Orgad Shaneh as Maintainer of Version Control modules in Qt Creator

Of course +1 From: Development on behalf of Tobias Hunger Sent: Wednesday, May 2, 2018 12:14:14 PM To: qt-crea...@qt-project.org; development@qt-project.org Subject: [Development]

Re: [Development] Proposing Orgad Shaneh as Maintainer of Version Control modules in Qt Creator

+1! :) On 05/02/2018 12:14 PM, Tobias Hunger wrote: Hello, I want to propose Orgad Shaneh as maintainer of the version control related modules in Qt Creator. So far I have been handling that responsibility, but since I took over the project-related Qt Creator plugins, I had way too little

[Development] Proposing Orgad Shaneh as Maintainer of Version Control modules in Qt Creator

Hello, I want to propose Orgad Shaneh as maintainer of the version control related modules in Qt Creator. So far I have been handling that responsibility, but since I took over the project-related Qt Creator plugins, I had way too little time on my hands to take a lead in the version

[Development] CI stabilization status

Hi all, Additional effort was put in stabilizing the CI in the beginning of the February. Highlights of the improvements so far are: * Top flaky test cases have been fixed or blacklisted * This was initially the number one reason for randomly failing integrations * Mostly

Re: [Development] Consistently flaky test QTabWidget test

On onsdag 2. mai 2018 09.29.18 CEST Thiago Macieira wrote: > 8 out of 8 integrations attempted in both qtbase/dev and qtbase/5.11 > yesterday resulted in > > FAIL! : tst_QTabWidget::paintEventCount() Compared values are not the same > Actual (tab2->count): 2 > Expected (1) : 1 >

Re: [Development] Consistently flaky test QTabWidget test

Hi! I'm also taking a look at it. It's my change that broke it. The issue is that the test is getting some extra paint events on macOS. Previously it had a qWait(1000) that waited over them. Here's a change to add it back and stop blocking other integrations:

Re: [Development] Consistently flaky test QTabWidget test

I'll take a look! -Richard Fra: Development på vegne av Thiago Macieira Sendt: 2. mai 2018 09:46:40 Til: development@qt-project.org Emne: Re: [Development] Consistently

Re: [Development] Nominating Jüri Valdmann for Approver status

+1 absolutely. Best, Michael > On 27. Apr 2018, at 10:58, Michal Klocek wrote: > > Hi > > I would like to nominate Jüri Valdmann for Approver. > > He joined The Qt Company more than one year ago and he's been doing most > of his excellent work for QtWebEngine. > > You

Re: [Development] Consistently flaky test QTabWidget test

On Wednesday, 2 May 2018 00:29:18 PDT Thiago Macieira wrote: > 8 out of 8 integrations attempted in both qtbase/dev and qtbase/5.11 > yesterday resulted in Make that 9 of 9. I'll stop trying to stage anything in qtbase until further notice. -- Thiago Macieira - thiago.macieira (AT) intel.com

[Development] Consistently flaky test QTabWidget test

8 out of 8 integrations attempted in both qtbase/dev and qtbase/5.11 yesterday resulted in FAIL! : tst_QTabWidget::paintEventCount() Compared values are not the same Actual (tab2->count): 2 Expected (1) : 1 Loc: [tst_qtabwidget.cpp(573)] [on macOS 10.12] This test *is*

Re: [Development] Proposing David Faure as maintainer of Qt Models

Currently that's true. But if we have separate maintainers for the item models and views, we might want to split it. Cheers, Lars > On 2 May 2018, at 09:22, Thiago Macieira wrote: > > On Tuesday, 1 May 2018 23:49:46 PDT Lars Knoll wrote: >> That's different from the

Re: [Development] Proposing David Faure as maintainer of Qt Models

On Tuesday, 1 May 2018 23:49:46 PDT Lars Knoll wrote: > That's different from the item models. Not to me, no. All the bug reports I get related to the item models I immediately reassign to "Widgets: Itemviews". [...] > There is already a component "Widgets: Itemviews" which should be renamed >

Re: [Development] Proposing David Faure as maintainer of Qt Models

That's different from the item models. Cheers, Lars On 2 May 2018, at 08:45, Christian Ehrlicher > wrote: Hi, There is already a component "Widgets: Itemviews" which should be renamed then. Christian Gesendet: Mittwoch, 02. Mai 2018 um 08:37

Re: [Development] Proposing David Faure as maintainer of Qt Models

Hi,   There is already a component "Widgets: Itemviews" which should be renamed then.   Christian   Gesendet: Mittwoch, 02. Mai 2018 um 08:37 Uhr Von: "Lars Knoll" An: "Alex Blasche" Cc: "Qt development mailing list"

Re: [Development] Proposing David Faure as maintainer of Qt Models

I'd say we add one line for qtbase/Qt Core/Item models in the maintainer wiki. 'Item models' would probably also be the best name for Jira. Cheers, Lars > On 2 May 2018, at 08:34, Alex Blasche wrote: > > It was pointed out to me that this vote has come due. The usual

Re: [Development] Proposing David Faure as maintainer of Qt Models

It was pointed out to me that this vote has come due. The usual response is to update Jira components and the maintainer wiki. Neither of these have a category for this. What is the conclusion here? Do we need a new entry in the wiki and Jira? If so what would be the name for it. -- Alex