> please, if it can be avoided, don't add yet another string-related class to
> Qt. Knowing
> when to properly use QString, QByteArray, QLatin1String, QStringLiteral,
> QStringRef and
> QStringView (I may have missed a few) is already a challenge. And I imagine
> for people
> new to Qt it can e
+1 !
> On 11 Jul 2019, at 17:27, Paul Wicking wrote:
>
> Hi all,
>
> I’d like to nominate Kavindra Palaraja as approver. She is a very active
> contributor and reviewer, in particular for documentation related changes,
> focusing on the Qt Automotive platform. She’s a former employee of Trol
On Thu, 11 Jul 2019 at 18:43, Matthew Woehlke
wrote:
> On 11/07/2019 05.05, Mutz, Marc via Development wrote:
> > There is a cost associated with another string class, too, and it's
> > combinatorial explosion. Even when we have all view types
> > (QLatin1StringView, QUtf8StringView, QStringView)
+1 from me too. I have reviewed a number of her doc patches and she would be a
good asset to help with approving too!
Andy
From: Development on behalf of Paul
Wicking
Date: Thursday, 11 July 2019 at 17:29
To: "development@qt-project.org"
Subject: [Development] Nominating Kavindra Palaraja fo
On 11/07/2019 05.05, Mutz, Marc via Development wrote:
> There is a cost associated with another string class, too, and it's
> combinatorial explosion. Even when we have all view types
> (QLatin1StringView, QUtf8StringView, QStringView), consider the overload
> set of QString::replace(), ignoring t
Paul Wicking (Thursday, July 11, 2019 5:27 PM)
>> I’d like to nominate Kavindra Palaraja as approver.
Topi Reiniö (11 July 2019 17:33)
> +1 from me.
And another +1 here.
Eddy.
___
Development mailing list
Development@qt-project.org
https://list
+1
From: Development on behalf of Topi Reiniö
Sent: Thursday, July 11, 2019 5:33 PM
To: development@qt-project.org
Subject: Re: [Development] Nominating Kavindra Palaraja for approvership
+1 from me.
\topi
From: Develop
+1 from me.
\topi
From: Development on behalf of Paul
Wicking
Sent: Thursday, July 11, 2019 5:27 PM
To: development@qt-project.org
Subject: [Development] Nominating Kavindra Palaraja for approvership
Hi all,
I’d like to nominate Kavindra Palaraja as approve
Hi all,
I’d like to nominate Kavindra Palaraja as approver. She is a very active
contributor and reviewer, in particular for documentation related changes,
focusing on the Qt Automotive platform. She’s a former employee of Trolltech
and Nokia, and has a lot of experience with Qt’s documentation
On 11 Jul 2019, at 10:26, Elvis Stansvik
mailto:elvst...@gmail.com>> wrote:
Den tors 11 juli 2019 kl 05:54 skrev Jason McDonald
mailto:macadd...@gmail.com>>:
Welcome back Jason :)
On Tue, Jul 9, 2019 at 1:39 AM Shawn Rutledge
mailto:shawn.rutle...@qt.io>> wrote:
On 8 Jul 2019, at 16:24, Vol
Jason McDonald (11 July 2019 05:53) wrote:
> I also recall that there used to be a wiki page that listed some
> best-practices for writing unit tests. If that list still exists
> somewhere, this advice should be added there.
Possibly:
https://wiki.qt.io/Writing_good_tests
Eddy.
__
On 2019-07-11 10:13, André Pönitz wrote:
On Wed, Jul 10, 2019 at 10:01:04PM -0300, Thiago Macieira wrote:
On Wednesday, 10 July 2019 09:55:02 -03 André Pönitz wrote:
> As far as I understand there's a perceived need to have "full" utf8
> literals, and there's a need to have ASCII literals. First
Konstantin Podsvirov (10 July 2019 22:52)
> The code.qt.io at 34.244.34.65 hase not response.
Seems to be back now, at least for me.
Shout if you're still not seeing it !
Eddy.
___
Development mailing list
Development@qt-project.org
https://list
Den tors 11 juli 2019 kl 05:54 skrev Jason McDonald :
>
> On Tue, Jul 9, 2019 at 1:39 AM Shawn Rutledge wrote:
> > > On 8 Jul 2019, at 16:24, Volker Hilsheimer
> > > wrote:
> > >
> > > Hi,
> > >
> > > Executive summary:
> > >
> > > * QTest::mouseMove seems to be broken
> > > * when simulating QE
On Thu, Jul 11, 2019 at 5:57 PM Palaraja, Kavindra wrote:
> On 11.07.19, 05:55, "Development on behalf of Jason McDonald"
> wrote:
>
>
>
> I also recall that there used to be a wiki page that listed some
> best-practices for writing unit tests. If that list still exists
> somewh
On Wed, Jul 10, 2019 at 10:01:04PM -0300, Thiago Macieira wrote:
> On Wednesday, 10 July 2019 09:55:02 -03 André Pönitz wrote:
> > As far as I understand there's a perceived need to have "full" utf8
> > literals, and there's a need to have ASCII literals. First could be
> > served by some QUtf8*, s
On 11.07.19, 05:55, "Development on behalf of Jason McDonald"
wrote:
I also recall that there used to be a wiki page that listed some
best-practices for writing unit tests. If that list still exists
somewhere, this advice should be added there.
Did you mean this page: https://
17 matches
Mail list logo
