On 31. Oct 2018, at 06:38, Bogdan Vatra via Development
mailto:development@qt-project.org>> wrote:
Hi,
În ziua de marți, 30 octombrie 2018, la 19:11:20 EET, Oswald Buddenhagen a
scris:
On Tue, Oct 30, 2018 at 01:16:43PM +0200, Bogdan Vatra wrote:
c.2) back then, none of the existing build
On 2018-10-31 11:40, Martin Koller wrote:
In this file I find:
// auto generated. DO NOT EDIT.
class QCssScanner_Generated
Who/what generates this file ?
Looks like is generated by util/lexgen
$ cd util/lexgen
$ qmake && make
$ ./lexgen css3-simplified.lexgen
Regards,
--
Sérgio Martins |
It is there, but you have to go to http://lists.qt-project.org for now, it is
being moved to a new server so at some point the https address will be back,
but until then you need to use the http address.
Andy
Development på vegne av Christian Gagneraud
skrev følgende den 31.10.2018, 14:36:
On 30/10/2018 17.51, Oswald Buddenhagen wrote:
> for starters just some food for thought:
> QBS-995 should be implementable on top of it.
> if you want to go full monty, QBS-942 is your target.
What are those? Can you provide links?
> one thing i noticed is that you multiplex build variants and
> -Original Message-
> From: J-P Nurmi
> Sent: Wednesday, 31 October 2018 12:41 PM
> To: Mitch Curtis
> Cc: development@qt-project.org
> Subject: Re: [Development] Serialising UI state in QML via QSettings and
> JSON: QByteArray vs QString
>
> On Wed, Oct 31, 2018 at 8:25 AM Mitch
On Wednesday, 31 October 2018 03:02:04 PDT Bernhard Lindner wrote:
> Maybe I worked for the wrong companies all the time. But whenever we wanted
> to have proof that some tool or library actually meets our requirements, it
> never was sufficient to *ask* for proof. We needed to test it by
On Thu, 1 Nov 2018 at 02:53, Andy Shaw wrote:
>
> It is there, but you have to go to http://lists.qt-project.org for now, it is
> being moved to a new server so at some point the https address will be back,
> but until then you need to use the http address.
In case you're not aware, HTTP is
> C++17 required (and I didn't know this specific syntax worked).
AFAIR, this is in fact a C++20 proposal.
Hence best is:
for (auto : std::as_const(container))
Philippe
On Wed, 31 Oct 2018 08:30:28 -0700
Thiago Macieira wrote:
> On Wednesday, 31 October 2018 03:35:32 PDT Giuseppe D'Angelo
On Tuesday, 30 October 2018 22:59:57 PDT André Pönitz wrote:
> Where would a QBS-promoting webpage be located?
>
> qt-project.org ?
Sure, why not?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Il 31/10/18 16:52, Philippe ha scritto:
AFAIR, this is in fact a C++20 proposal.
Yes, it is (only if / switch got the optional initializer in C++17).
Anyhow, nothing special about this:
1) can just do the same in pre-C++2a in two lines
2) not using C++-latest costs more :-)
Cheers,
--
On Wednesday, 31 October 2018 03:35:32 PDT Giuseppe D'Angelo via Development
wrote:
> > for (const auto = container; auto : c)
>
> Why not using this one for *both* lvalues and rvalues? Once more, one
> fewer thing to teach.
C++17 required (and I didn't know this specific syntax worked).
--
Hi,
Can we have Qt mailing list archive back?
I believe it is tracked by
https://bugreports.qt.io/browse/QTWEBSITE-831 and as been going on for
weeks. Can the "Qt Project Hosting Foundation" (from whois record)
take care of that?
What is going on?
Chris
WHAT A TWAT!
P.S.
Yes, feel free to ban me, it was worth it.
-Original Message-
From: Christian Gagneraud [mailto:chg...@gmail.com]
Sent: 31 October 2018 14:02
To: andy.s...@qt.io
Cc: development@qt-project.org
Subject: Re: [Development] Who is in charge of qt-project.org?
On Thu, 1
On Wednesday, 31 October 2018 08:52:10 PDT Philippe wrote:
> Hence best is:
>
> for (auto : std::as_const(container))
Which is why we added qAsConst.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
On Wed, Oct 31, 2018 at 10:17:04AM -0400, Matthew Woehlke wrote:
> On 30/10/2018 17.51, Oswald Buddenhagen wrote:
> > for starters just some food for thought:
> > QBS-995 should be implementable on top of it.
> > if you want to go full monty, QBS-942 is your target.
>
> What are those? Can you
>Date: Wed, 31 Oct 2018 08:28:45 -0700
>From: Thiago Macieira
>To:
>Subject: Re: [Development] Build system for Qt 6
>Message-ID: <7867869.XuAOyZs5DA@tjmaciei-mobl1>
>Content-Type: text/plain; charset="iso-8859-1"
>
>>On Tuesday, 30 October 2018 22:59:57 PDT Andr? P?nitz wrote:
> >Where would a
On Wednesday, 31 October 2018 03:19:46 PDT Иван Комиссаров wrote:
> Hello, Thiago wrote in the "buildsystem thread" that Qt 6 will be source
> compatible with Qt5. As long as I fully support source-compatibility with
> both hands, I would like to ask several questions about possible
>
On 31/10/2018 12.46, Oswald Buddenhagen wrote:
> On Wed, Oct 31, 2018 at 10:17:04AM -0400, Matthew Woehlke wrote:
>> On 30/10/2018 17.51, Oswald Buddenhagen wrote:
>>> after much thinking about the matter, i concluded that the interface
>>> files should correspond to "atomic linkable entities",
On Wed, Oct 31, 2018 at 01:09:13PM -0400, Matthew Woehlke wrote:
> On 31/10/2018 12.46, Oswald Buddenhagen wrote:
> > On Wed, Oct 31, 2018 at 10:17:04AM -0400, Matthew Woehlke wrote:
> >> On 30/10/2018 17.51, Oswald Buddenhagen wrote:
> >>> after much thinking about the matter, i concluded that
On 31/10/2018 14.26, Oswald Buddenhagen wrote:
> On Wed, Oct 31, 2018 at 01:09:13PM -0400, Matthew Woehlke wrote:
>> Again, how then does the consuming tool know which qt.core and which
>> qt.gui are compatible with each other? How does it handle the case of
>> finding a qt.core with no matching
On Thu, 1 Nov 2018 at 05:28, Kain Vampire via Development
wrote:
>
> WHAT A TWAT!
>
> P.S.
>
> Yes, feel free to ban me, it was worth it.
Was it?
You could have used the word 'idiot', at least it is not an insult to
the feminine gender.
You could have as well quoted which part of the message
Hi,
As part of our work projects we have a framework (named Proof and partly open
sourced). Most part of it is not really interesting outside of our industry,
but one of its basic ideas is heavy usage of future/promise technology with API
similar to one used in Scala. We also have tasks
On Wed, Oct 31, 2018 at 8:25 AM Mitch Curtis wrote:
> > Pass the state as a base64 string. Where does it turn to a byte array if
> > Qt.btoa() returns a string?
>
> As of the previous patch set, saveState() returned a QByteArray, so the user
> starts off with a byte array. If I somehow manage to
In this file I find:
// auto generated. DO NOT EDIT.
class QCssScanner_Generated
Who/what generates this file ?
I'm looking for the syntax definition for the attribute matching since
the docs only talk about attr=value and attr~=value
but in the code I find others:
enum ValueMatchType {
On Wed, Oct 31, 2018 at 11:16:18AM +0100, Robin Burchell wrote:
> On Tue, Oct 30, 2018, at 5:40 PM, Oswald Buddenhagen wrote:
> > on top of that there are long-term savings to be made from increased
> > productivity (which several posters to this thread have confirmed or
> > implied). that alone
Hi,
Il 31/10/18 11:19, Иван Комиссаров ha scritto:
1) QAbstractItemModel. I want to introduce change that adds QModelIndex
parameter to headerData(). For now, QHeaderView ignores the rootIndex()
property which prevents creating models with sub tables in each index (only
tree models are
On Tue, 30 Oct 2018 19:24:26 +, Adam Treat wrote:
> Lars gave a keynote saying pretty much the same. Simply is not true that
> we are planning major source compatible breakage for Qt6 so let's stop
> saying that.
When will the already deprecated QQuickControls 1 module going to be
finally
On Wed, 31 Oct 2018 at 11:08, Thiago Macieira wrote:
> On Tuesday, 30 October 2018 14:44:43 PDT Christian Gagneraud wrote:
> > On Wed, 31 Oct 2018 at 10:27, Thiago Macieira
> wrote:
> > > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenko wrote:
> > > The only thing I'm criticising is
Yeah, we were already wondering about that. Before the builds starts, it has
160 GB of free disk space. Could the build really eat up all that?
We've had kernel crashing on the host side of the VM, and that has caused the
VM to put its disks on read-only mode. That has then created errors that
> -Original Message-
> From: J-P Nurmi
> Sent: Tuesday, 30 October 2018 3:52 PM
> To: Mitch Curtis
> Cc: development@qt-project.org
> Subject: Re: [Development] Serialising UI state in QML via QSettings and
> JSON: QByteArray vs QString
>
> On Tue, Oct 30, 2018 at 3:04 PM Mitch
See: “deprecated”
From: Development on
behalf of Uwe Rathmann
Sent: Wednesday, October 31, 2018 2:35:50 AM
To: development@qt-project.org
Subject: Re: [Development] Build system for Qt 6
On Tue, 30 Oct 2018 19:24:26 +, Adam Treat wrote:
> Lars gave a
On Wed, 31 Oct 2018 10:44:43 +1300
Christian Gagneraud wrote:
> On Wed, 31 Oct 2018 at 10:27, Thiago Macieira
> wrote:
> > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenko wrote:
> > The only thing I'm criticising is that its proper chance involves Qt being
> > the
> > guinea pig.
Hi,
Initial ones here:
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.0%22,n,z
Maintainers, please do needed modifications now and make sure changes will be
approved as soon as possible
br,
Jani Heikkinen
Release Manager
On Wed, 31 Oct 2018 at 22:47, Christian Kandeler
wrote:
>
> On Wed, 31 Oct 2018 10:44:43 +1300
> Christian Gagneraud wrote:
>
> > On Wed, 31 Oct 2018 at 10:27, Thiago Macieira
> > wrote:
> > > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenko wrote:
> > > The only thing I'm
Il 31/10/18 11:17, Philippe ha scritto:
and for the rvalue reference case:
for (const auto = container; auto : c)
Why not using this one for *both* lvalues and rvalues? Once more, one
fewer thing to teach.
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software
On Tue, Oct 30, 2018 at 02:07:16PM -0700, Thiago Macieira wrote:
> On Tuesday, 30 October 2018 13:47:00 PDT Oswald Buddenhagen wrote:
> > On Tue, Oct 30, 2018 at 12:53:48PM -0700, Thiago Macieira wrote:
> > > On Tuesday, 30 October 2018 12:29:46 PDT Oswald Buddenhagen wrote:
> > > > doesn't
Il 29/10/18 13:00, André Hartmann ha scritto:
Looking athttps://docs.kdab.com/analysis/qtcreator/clazy.html gives
currently 223 potential detaching containers within range-based for, and
qtbase alone has 46 (https://docs.kdab.com/analysis/qt5/clazy.html).
Even if there may be some false
Il 29/10/18 12:43, Olivier Goffart ha scritto:
Deprecating means you will force user to port all their codebase away from it,
which is a huge work. If the rationale is just that they will save a couple of
atomic operations, i do not think it is worth it.
Deprecating it only for non-shared
Hi!
> No. However, I am asking for proof.
Maybe I worked for the wrong companies all the time. But whenever we wanted to
have proof
that some tool or library actually meets our requirements, it never was
sufficient to
*ask* for proof. We needed to test it by *ourselfs* in a feasibility
On Tue, Oct 30, 2018, at 5:40 PM, Oswald Buddenhagen wrote:
> on top of that there are long-term savings to be made from increased
> productivity (which several posters to this thread have confirmed or
> implied). that alone won't offset the cost vs. using cmake (it would vs.
> developing and
Good post, but:
>> * if you have a container and you want to do non-mutating iteration, use
>> for (const auto = container; const auto : c)
This is enough:
for (auto : std::as_const(container))
and for the rvalue reference case:
for (const auto = container; auto : c)
Philippe
On Wed,
Hello, Thiago wrote in the "buildsystem thread" that Qt 6 will be source
compatible with Qt5. As long as I fully support source-compatibility with both
hands, I would like to ask several questions about possible source-breaking
changes.
1) QAbstractItemModel. I want to introduce change that
42 matches
Mail list logo
