Hi,
just for clarification: If we factor out shared resources into a library, then
that wouldn't be one big QtExamplesShared module,
but rather one library per module (unless something actually needs to be shared
across multiple modules, e.g. icons).
Anything else would require moving examples
> On 4 Mar 2024, at 10:57, Marc Mutz via Development
> wrote:
>
> Hi,
>
> TL;DR:
> - Treat all APIs not clearly marked as private (private access, *Private
> namespace or "We mean it!" comment) as public, in particular keep SC/BC
> and deprecate before remove.
> - Avoid adding APIs that
+1
From: Development on behalf of Tor Arne
Vestbø via Development
Sent: Thursday, March 7, 2024 10:27
To: Axel Spoerl
Cc: development@qt-project.org
Subject: Re: [Development] Nominating Dr. Máté Barany as an approver for the
Qt project
+1!
On 6 Mar
Hi,
We have quite a few Qt examples and tutorials that share assets (images,
sources, ...) via relative paths in the file system. That is, there's often a
'shared' directory that multiple examples use by relative paths (see e.g.
+1
From: Development On Behalf Of Matthias
Rauter via Development
Sent: Thursday, March 7, 2024 7:04 AM
To: development@qt-project.org
Subject: Re: [Development] Nominating Dr. Máté Barany as an approver for the Qt
project
+1
-Matti
From: Development
Hi Tor Arne,
On 06.03.24 09:34, Tor Arne Vestbø wrote:
> The choice of where we use/allow `#pragma once` should not be coupled to
> whether a header is considered public or not.
Let's be careful with wording here. No-one proposes to use #pragma once
to distinguish public from private headers!
+1!
On 6 Mar 2024, at 23:09, Axel Spoerl via Development
wrote:
Dear Colleagues,
I hereby nominate Dr. Máté Barany as an approver for the Qt project.
Máté has been a valuable contributor and reviewer, providing sound code,
guidance and input.
As a reference, see his dashboard
