Hi,
on openSuse 42.2 I have a self-built 5.9.1 version and also the openSuse 5.9.1
installed one.
For some reason (which is not important for my question) my application picks
up the openSuse library
but fails with the error
libQt5Core.so.5: version `Qt_5.9.1_PRIVATE_API' not found (required by
Hi,
I’d like to nominate Tomi Korpipää from my team here at The Qt Company for
approver status. Tomi has been key contributor in Qt Charts, Qt
DataVizualisation, Qt3D Editor and in the recently unveiled Qt 3D Studio. I
think this nomination is long overdue as Tomi has been one of the carrying
On 11 October 2017 at 03:49, Thiago Macieira wrote:
>
> On Tuesday, 10 October 2017 20:18:42 CEST Mat Sutcliffe wrote:
> > On 10 October 2017 at 15:28, Thiago Macieira
> >
> > wrote:
> > > On Tuesday, 10 October 2017 15:12:52 CEST Christian Gagneraud wrote:
> > > > (PS: I don't even know if qDebu
On Tue, Oct 10, 2017 at 2:34 PM, Andy Nichols wrote:
> We also will take inspiration from our sister project KDE, who already has a
> Code of conduct.
If you want to have a chat about KDE's code of conduct feel free to
reach out to me. I'm one of the people who drafted it and am happy to
answer q
On Tuesday, 10 October 2017 20:18:42 CEST Mat Sutcliffe wrote:
> On 10 October 2017 at 15:28, Thiago Macieira
>
> wrote:
> > On Tuesday, 10 October 2017 15:12:52 CEST Christian Gagneraud wrote:
> > > (PS: I don't even know if qDebug streaming is lock-free and i'm
> > > interested to know the answ
On 10/10/2017, 15.12, "Development on behalf of Rafael Roquetto"
wrote:
>
>Hello,
>
>Out of curiosity, was this decision triggered by an incident, i.e., is
> there
>any motiviation for this beyond being a nice thing to have?
No single incident. This was asked/discussed also
On 10 October 2017 at 15:28, Thiago Macieira
wrote:
> On Tuesday, 10 October 2017 15:12:52 CEST Christian Gagneraud wrote:
>
> > (PS: I don't even know if qDebug streaming is lock-free and i'm
> > interested to know the answer:))
>
> It's not. There are mutexes inside.
>
The SO answer and its co
Back on 13 September 2017 at 10:54 I announced:
> Change reviews generated:
>
> https://codereview.qt-project.org/205317 -- qtbase
> https://codereview.qt-project.org/205318 -- qtdeclarative
> https://codereview.qt-project.org/205319 -- qtmultimedia
> https://codereview.qt-project.org/205320 -- qtl
Hello
I was asked how to do this. If you're a maintainer or approver, you probably
want to watch for any new changes matching paths you're involved with. Here's
how:
1) Log in to gerrit
2) Click on your name on the top right, then Settings
3) Select "Watched Projects"
4) Add an entry like:
On Tuesday, 10 October 2017 15:12:52 CEST Christian Gagneraud wrote:
> On 10 October 2017 at 22:48, Thiago Macieira
wrote:
> > do not change qdebug but provide structured tracing as a new facility
>
> Any chance this can be made lock-free from a caller point of view?
No, we cannot provide a loc
> (4x difference measured).
wow, good to know.
---
Jean-Michaël Celerier
http://www.jcelerier.name
On Tue, Oct 10, 2017 at 3:33 PM, Thiago Macieira
wrote:
> On Tuesday, 10 October 2017 15:04:29 CEST Jean-Michaël Celerier wrote:
> > > ** Wrapping std::{unordered_}map may be acceptable
> >
Oops, here's the non-internal URL:
https://docs.kdab.com/analysis/qt5/clazy.html
Thanks Mitch
On 2017-10-10 14:27, Sergio Martins wrote:
Hi,
KDAB is now running clazy over the Qt code base, you can check the
results here: https://ci.kdab.com/~build/analysis/qt5/clazy.html
Next step is t
It seems this page is behind a login.
> -Original Message-
> From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt-
> project.org] On Behalf Of Sergio Martins
> Sent: Tuesday, 10 October 2017 3:27 PM
> To: development@qt-project.org
> Subject: [Development] Clazy results for
On Tuesday, 10 October 2017 15:04:29 CEST Jean-Michaël Celerier wrote:
> > ** Wrapping std::{unordered_}map may be acceptable
>
> Hmmm... from these benchmarks, QHash seems to regularly beat
> std::unordered_map so is it really worth it ?
> => https://tessil.github.io/2016/08/29/benchmark-hopscot
Hi,
KDAB is now running clazy over the Qt code base, you can check the
results here: https://ci.kdab.com/~build/analysis/qt5/clazy.html
Next step is to figure out which sub-set we want to use in within
qt-project, if we want to enforce any via CI, which ones we want to fix
for Qt5 and which
Hello,
Out of curiosity, was this decision triggered by an incident, i.e., is there
any motiviation for this beyond being a nice thing to have?
On Tue, Oct 10, 2017 at 12:34:14PM +, Andy Nichols wrote:
> # Qt Project Code of Conduct (discussion)
>
> ## Goals
> We want to adopt a code of con
On 10 October 2017 at 22:48, Thiago Macieira wrote:
> do not change qdebug but provide structured tracing as a new facility
Any chance this can be made lock-free from a caller point of view?
(PS: I don't even know if qDebug streaming is lock-free and i'm
interested to know the answer:))
A lock-fr
On Tuesday, 10 October 2017 14:49:48 CEST Thiago Macieira wrote:
> * They'd all need to be inline and some could be big
Missing context here: this was about making them templated so they could work
on std::string and other string-like types.
--
Thiago Macieira - thiago.macieira (AT) intel.com
> ** Wrapping std::{unordered_}map may be acceptable
Hmmm... from these benchmarks, QHash seems to regularly beat
std::unordered_map so is it really worth it ?
=> https://tessil.github.io/2016/08/29/benchmark-hopscotch-map.html
Besides, with the Qt implementation the performance is more-or-less
> On 10 Oct 2017, at 14:38, Thiago Macieira wrote:
>
> On Tuesday, 10 October 2017 14:01:47 CEST Rafael Roquetto wrote:
>> Howdy,
>>
>> I would like to nominate Andras Mantia, a fellow colleague at KDAB, for
>> approver status. Andras has been a key contributor in the develpment of the
>> recen
[we combined the main and containers session; we did not have time for
QIODevice]
== Intro ==
Suggested topics:
* QIODevice for Qt 6
* adding std::hash for Qt types
* expanding the hash seed to 64- or 128-bit
Move to the containers session:
* use qssize_t
Quick conclusions:
* QRandomGenerator a
On Tuesday, 10 October 2017 14:34:14 CEST Andy Nichols wrote:
> We will form a small committee to draft a proposal to become the Qt Project
> Code of Conduct. We will start with the [Contributor Covenant Code of
> Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct.h
> tml) a
On Tuesday, 10 October 2017 14:01:47 CEST Rafael Roquetto wrote:
> Howdy,
>
> I would like to nominate Andras Mantia, a fellow colleague at KDAB, for
> approver status. Andras has been a key contributor in the develpment of the
> recently unveiled Qt3DStudio. His continuous involvement with the pr
Qt 6 Changes epic ( https://bugreports.qt.io/browse/QTBUG-62425 ) has a Qt
Quick Scenegraph subtask: https://bugreports.qt.io/browse/QTBUG-62439
Basis of discussion.
- background story. Qt 3D Studio likely based on Qt 3D in the future, it has
been brought up if Qt Quick should also be unified
On 2017-10-10 13:01, Rafael Roquetto wrote:
Howdy,
I would like to nominate Andras Mantia, a fellow colleague at KDAB, for
approver status. Andras has been a key contributor in the develpment of
the
recently unveiled Qt3DStudio. His continuous involvement with the
project and
deep understandi
# Qt Project Code of Conduct (discussion)
## Goals
We want to adopt a code of conduct for the Qt project to establish a formal
line-in-the-sand about what is unacceptable behavior. We want new members of
the Qt community to feel comfortable and accepted, and we want to foster a
healthy working
* Qt 3D Studio is now open (GPLv3/Commercial), on Gerrit at
qt3dstudio/qt3dstudio.
https://codereview.qt-project.org/gitweb?p=qt3dstudio%2Fqt3dstudio.git;a=summary
* Official Qt 3D Studio 1.0 release targeting end of November.
* Meanwhile research/work is on-going for a new, Qt 3D-based runtim
Howdy,
I would like to nominate Andras Mantia, a fellow colleague at KDAB, for
approver status. Andras has been a key contributor in the develpment of the
recently unveiled Qt3DStudio. His continuous involvement with the project and
deep understanding of the code makes his nomination very pertinen
10.10.2017, 13:10, "Thiago Macieira" :
> On Tuesday, 10 October 2017 11:59:07 CEST Konstantin Tokarev wrote:
>> 10.10.2017, 12:50, "Thiago Macieira" :
>> > On Tuesday, 10 October 2017 11:48:02 CEST Konstantin Tokarev wrote:
>> >> > We would like to have CBOR support in QtCore.
>> >>
>> >> If
On Tuesday, 10 October 2017 11:59:07 CEST Konstantin Tokarev wrote:
> 10.10.2017, 12:50, "Thiago Macieira" :
> > On Tuesday, 10 October 2017 11:48:02 CEST Konstantin Tokarev wrote:
> >> > We would like to have CBOR support in QtCore.
> >>
> >> If you do this, please support stringref extension:
10.10.2017, 12:59, "Konstantin Tokarev" :
> 10.10.2017, 12:50, "Thiago Macieira" :
>> On Tuesday, 10 October 2017 11:48:02 CEST Konstantin Tokarev wrote:
>>> > We would like to have CBOR support in QtCore.
>>>
>>> If you do this, please support stringref extension:
>>> http://cbor.schmorp.
10.10.2017, 12:50, "Thiago Macieira" :
> On Tuesday, 10 October 2017 11:48:02 CEST Konstantin Tokarev wrote:
>> > We would like to have CBOR support in QtCore.
>>
>> If you do this, please support stringref extension:
>> http://cbor.schmorp.de/stringref
>
> Point me to the IETF draft. No actio
On Tuesday, 10 October 2017 11:48:02 CEST Konstantin Tokarev wrote:
> > We would like to have CBOR support in QtCore.
>
> If you do this, please support stringref extension:
> http://cbor.schmorp.de/stringref
Point me to the IETF draft. No action before then.
--
Thiago Macieira - thiago.macieir
== Discussion ==
* Structured logging:
** We want to extract information from logs and detect common messages. For
example:
{|
! From
! To
|-
|
Got message "Hello"
|
Got message "%s" Hello
|-
|
Got message "World"
|
Got message "%s" World
|}
** We want to al
10.10.2017, 12:43, "Thiago Macieira" :
> == CoAP Client ==
>
> * Contribution consists of CoAP client
> ** Supports PUT/GET/POST/DELETE
> *** Not yet FETCH/PATCH (RFC 8132)
> ** Supports Blockwise transfer
> ** Supports Notification (QCoapReply::notified signal,
> QCoapClient::cancelObserve())
>
== CoAP Client ==
* Contribution consists of CoAP client
** Supports PUT/GET/POST/DELETE
*** Not yet FETCH/PATCH (RFC 8132)
** Supports Blockwise transfer
** Supports Notification (QCoapReply::notified signal,
QCoapClient::cancelObserve())
** Partially supports multicast
*** Sending on multicast
36 matches
Mail list logo
