+1
> -Original Message-
> From: Development On Behalf Of
> Jan-Arve Sæther via Development
> Sent: Wednesday, June 21, 2023 2:56 AM
> To: Jack Simcox via Development
> Subject: [Development] Nominating Santhosh Kumar Selvaraj for approver
> rights
>
> Hello all,
>
> I would like to
On 20.06.2023 17:01, Volker Hilsheimer wrote:
On 20 Jun 2023, at 16:24, Arno Rehn wrote:
On 20.06.2023 16:12, Jani Heikkinen via Development wrote:
Qt 6.5 status:
-Branching from '6.5' to '6.5.2' done
- Qt 6.5.2 content is not frozen yet. The target is to freeze the Qt
6.5.2 content later
+1
Richard
20. jun. 2023 kl. 20:58 skrev Jan-Arve Sæther via Development
:
Hello all,
I would like to nominate Santhosh Kumar Selvaraj for approver rights in the Qt
project.
Santhosh is a member of the UI Team, and has been working on improvement to our
styles, dark mode support, palette
+1
Santhosh is a highly experienced software engineer, a very good reviewer and I
trust he will add value as an approver.
Disclaimer: Santhosh and I are office roommates.
On 20 Jun 2023, at 21:26, Shawn Rutledge via Development
wrote:
+1
On 20 Jun 2023, at 20:55, Jan-Arve Sæther via
+1
On 20 Jun 2023, at 20:55, Jan-Arve Sæther via Development
wrote:
Hello all,
I would like to nominate Santhosh Kumar Selvaraj for approver rights in the Qt
project.
Santhosh is a member of the UI Team, and has been working on improvement to our
styles, dark mode support, palette handling
Hello all,
I would like to nominate Santhosh Kumar Selvaraj for approver rights in the Qt
project.
Santhosh is a member of the UI Team, and has been working on improvement to our
styles, dark mode support, palette handling both in qtbase and qtdeclarative.
You can see his merged changes here:
On 20 Jun 2023, at 16:24, Arno Rehn wrote:
On 20.06.2023 16:12, Jani Heikkinen via Development wrote:
Qt 6.5 status:
- Branching from '6.5' to '6.5.2' done
- Qt 6.5.2 content is not frozen yet. The target is to freeze the Qt 6.5.2
content later this week
- The target is to release Qt 6.5.2
I'm technically not a maintainer of either QtQml or QtQuick, but I think
I'm qualified to chime in here:
QML has (slightly hidden in
https://doc.qt.io/qt-6/qtqml-cppintegration-data.html#enumeration-types)
a way to disable this behavior by setting
Q_CLASSINFO("RegisterEnumClassesUnscoped",
On 20.06.2023 16:12, Jani Heikkinen via Development wrote:
Qt 6.5 status:
- Branching from '6.5' to '6.5.2' done
- Qt 6.5.2 content is not frozen yet. The target is to freeze the Qt
6.5.2 content later this week
- The target is to release Qt 6.5.2 Wed 28th June
Will we have to pick to
Qt 6.5 status:
- Branching from '6.5' to '6.5.2' done
- Qt 6.5.2 content is not frozen yet. The target is to freeze the Qt 6.5.2
content later this week
- The target is to release Qt 6.5.2 Wed 28th June
Qt 6.6 status:
- Qt 6.6.0 Beta1 released
- Target is to release Qt 6.6.0 Beta2 ~Mid
> On 14 Jun 2023, at 14:59, Marc Mutz via Development
> wrote:
[…]
> C) scoped enums SHOULD NOT repeat (part of) an enum's type name in the
> enumerators²
[…]
> I have been told today that QML allows scoped C++ enums to be used
> without the scope. If this is true, it should be fixed to
On 31 May 2023, at 16:05, Thiago Macieira wrote:
On Wednesday, 31 May 2023 00:17:21 PDT Marc Mutz via Development wrote:
I doubt there's an accepted project-wide standard, yet, but as a rule of
thumb that everyone might be able to agree on: If the function doesn't
store the string as-is (=parses
12 matches
Mail list logo
