+1
Best regards,
Mikhail
On Thu, May 7, 2020 at 11:39 AM Shawn Rutledge wrote:
>
> > On 2020 May 7, at 10:23, Christian Kandeler
> wrote:
> >
> > Hello,
> >
> > I'd like to nominate Ivan Komissarov as an approver.
> > Ivan has been doing valuable work in the qbs project for a while now,
> bot
it as a
> main part of Qt though.
>
> > Sent: Monday, February 03, 2020 at 9:29 AM
> > From: "Volker Hilsheimer"
> > To: "Mikhail Svetkin"
> > Cc: "development@qt-project.org"
> > Subject: Re: [Development] Request to mo
example of Qt marketplace.
I also would like to request to have an independent branch policy for the
new repository. It will allow to speed up development of qthttpserver and
it will not slow down Qt6 works.
Name of the project: Qt HTTP Server
Responsible person: Mikhail Svetkin
Gerrit username
Hi,
The idea looks awesome.
This is our rough plan of how we'd like to address one aspect of QML and Qt
> Quick today. We are looking forward to any feedback and questions to help
> us review and refine this design.
>
I was wondering is there any plans to use this pattern in other Qt modules?
A
s, but tracing the assembly code of
> QMutex vs std::mutex shows you why QMutex is better. Easy to check.
> In release mode of course.
>
> Philippe
>
> On Wed, 29 May 2019 20:12:05 +0200
> Mikhail Svetkin wrote:
>
>
> > The implementation of QMutex, and especially QRead
> The implementation of QMutex, and especially QReadWrtieLock is much more
efficient that one of most standard library.
I have run some benchmarks recently and the result did not show the QMutex
was the best.
I published the results here:
1.
https://bugreports.qt.io/browse/QTBUG-71036?focu
>
> No need to wait for c++20 =)
>
> > 16 мая 2019 г., в 22:23, Mikhail Svetkin
> написал(а):
> >
> > If we will return a range (C++20 accepted ranges) then we can provide
> better integration with other world and we will pay for
+ 1 for idea with Views.
All Qt containers are implicit shared. Why do we need to pay all the time
for implicit shared when we don't need it?
Qt containers are hard to integrate with 3rd-party libraries which use std
containers.
Also when we return a container we are always depend on the API of
c
I think it is not bad idea in general, but I think we need to wait only some of
them (maybe only build qtsvg and qt5).
I think instead of creating new branches in qt5 and qtsvg we need to work in
dev.
Best regards,
Mikhail
From: Development on behalf of Simon
with keeping
cmake up-to-date with qmake.
Let's send a patch and see what happens.
Best regards,
Mikhail
____________
From: Mikhail Svetkin
Sent: Thursday, March 21, 2019 4:06 PM
To: Alex Blasche
Cc: development@qt-project.org
Subject: Re: [Development] CMake branch
>
From: Volker Hilsheimer
Sent: Thursday, March 21, 2019 1:51 PM
To: Mikhail Svetkin
Cc: development@qt-project.org
Subject: Re: [Development] CMake branch
On 21 Mar 2019, at 13:00, Mikhail Svetkin
mailto:mikhail.svet...@qt.io>> wrote:
Hi everyone!
We’ve had an internal di
It will not block CI.
Best regards,
Mikhail
From: Kari Oikarinen
Sent: Thursday, March 21, 2019 1:13 PM
To: Mikhail Svetkin; development@qt-project.org
Subject: Re: [Development] CMake branch
On 21.3.2019 14.00, Mikhail Svetkin wrote:
> *
>
>
Hi everyone!
We’ve had an internal discussion about wip/cmake branch.
We thought maybe it is a good idea to merge wip/cmake into dev branch.
The advantages are:
- It allows our contributors to play with CMake in dev branch
- Speed-up the build of QtBase
- Easy to find a lot of bugs in C
I have tried a year ago. It was ok, but unfortunately i don't remember
version of Qt.
Best regards,
Mikhail
On Fri, 12 Oct 2018 at 15:45, Denis Shienkov
wrote:
> Hi guys.
>
> Does anybody tried to create and start the Android Service using Qt?
>
> I tried this example:
>
> * https://github.com
Yes, this library is very cool and requires only c++11.
Best regards,
Mikhail
On Wed, 22 Aug 2018 at 16:47, Tor Arne Vestbø wrote:
> On 17 Aug 2018, at 17:08, Thiago Macieira
> wrote:
> >
> > On Friday, 17 August 2018 02:50:32 PDT Tor Arne Vestbø wrote:
> >>> Unless someone can volunteer to t
>
> I'm also not sure if it's worth it. Perhaps using Q_PRIVATE_PROPERTY gets
> us
> close enough?
Q_PRIVATE_PROPERTY allows only pointer and can't use
ui->object->nextObject or ui_->getObject().
2014-03-12 18:36 GMT+06:00 Simon Hausmann :
> On Wednesday 12. March 2014 12.48.20 Olivier Goffar
16 matches
Mail list logo
