Hi,
Thank you for the proposals Giuseppe!
On 18.1.2023, 14.14, "Development" wrote:
On 18/01/2023 10:51, Kimmo Leppälä via Development wrote:
> Also, the guideline is a living document in wiki and we would be happy
> to hear feedback and proposals for it!
>
Here's a few considerations:
> RE
Hi!
It's is again time to start updating 3rd party components for Qt 6.5.0. The
follow-up task is here: https://bugreports.qt.io/browse/QTBUG-110331
Maintainers, please check
a) All needed subtasks/modules are included in the main one
b) if your module needs 3rd party component updates & do needed
On Wed, Jan 18, 2023 at 04:10:20PM +, Kai Köhne via Development wrote:
> > -Original Message-
> >[...]
>
> > > MANDATORY
> > >
> > > Do not use QT_BEGIN_NAMESPACE ... QT_END_NAMESPACE for example
> > types. This namespace is exclusively for types in the Qt libraries.
> >
> > This
Il 18/01/23 17:10, Kai Köhne ha scritto:
(A nasty feature of uic is btw that it also does generate C++ code inside
QT_BEGIN_NAMESPACE, QT_END_NAMESPACE. That is, if you have a .ui file for a
Dialog, and you want to pre-declare the type generated by uic, you have to also
put it in QT_BEGIN_NAME
Il 18/01/23 17:10, Kai Köhne ha scritto:
Do not use QT_BEGIN_NAMESPACE ... QT_END_NAMESPACE for example
types. This namespace is exclusively for types in the Qt libraries.
This is broken. How is one going to correctly forward declare Qt names
in a namespaced build of Qt without using those
> -Original Message-
>[...]
> > MANDATORY
> >
> > Do not use QT_BEGIN_NAMESPACE ... QT_END_NAMESPACE for example
> types. This namespace is exclusively for types in the Qt libraries.
>
> This is broken. How is one going to correctly forward declare Qt names
> in a namespaced build of
On 18/01/2023 10:51, Kimmo Leppälä via Development wrote:
Also, the guideline is a living document in wiki and we would be happy
to hear feedback and proposals for it!
Here's a few considerations:
RECOMMENDED
Consider also compiling with the more strict warning flags and fix any issues th
Hi,
Yes, intention is to improve also the application / project examples in qtdoc
repo. In addition to the Qt 6 best practices, these could also get a bit of
visual or functionality polish. Problematic or unnecessary existing examples
could be removed. Intention is also to adjust how the exampl
Hi,
Typically pick to 6.5 as the examples like documentation is unproblematic to
update.
Yours,
Tuukka
From: Development on behalf of Ivan
Solovev via Development
Date: Wednesday, 18. January 2023 at 12.09
To: development@qt-project.org , Kimmo Leppälä
Subject: Re: [Develo
Hello,
I'd like to point to https://bugreports.qt.io/browse/QTBUG-100100 where
you can read:
"Ah, those examples are in the qtdoc repository, where nobody looks at
them..."
"Back when we worked on QTBUG-98130, we forgot to add the examples in
qtdoc to the list."
Are these going to receive
Hi,
Should the example updates be picked to 6.5, or is it only a 6.6 thing?
Is there any general guideline from the Release Team?
Best regards,
Ivan
From: Development on behalf of Kimmo
Leppälä via Development
Sent: Wednesday, January 18, 2023 10:51 AM
To: deve
Also, the guideline is a living document in wiki and we would be happy to hear
feedback and proposals for it!
-Kimmo
From: Kimmo Leppälä
Date: Wednesday, 18. January 2023 at 11.37
To: development@qt-project.org
Subject: New Qt example development guideline and revamping examples
Hi,
We have s
Hi,
We have started revamping Qt examples (https://doc.qt.io/qt-6/qtexamples.html)
to follow the new example development guideline:
https://wiki.qt.io/Qt6/Example-Guideline.
Target is to go through all the ~600 examples and either modify according the
guideline or remove, if the example is obso
13 matches
Mail list logo
