Hi,
I made notes in the Modern C++ session. You can also find them on the
Wiki here: https://wiki.qt.io/QtCS2015_ModernCpp but I was requested to
also post them here on the ML. If you were there and remember things
differently, please edit and post a reply with corrections.
==
Sunday June
On Thursday 11 June 2015 23:15:20 André Pönitz wrote:
> That's exactly the kind of situation I was referring to in my previous
> mail: This is intentionally introducing API inconsistency. It does not
> really matter to me whether "poor-man's prefix name spacing" is
> unfashionable or "we" consider
On Friday 12 June 2015 00:28:05 Marc Mutz wrote:
> On Thursday 11 June 2015 22:07:00 André Pönitz wrote:
> > To be blunt: Even though some of the existing patterns and conventions
> > are unfashionable in 2015, consistency is a value by itself. Any
> > partial "modernization" of the API destroys th
On Thursday 11 June 2015 22:07:00 André Pönitz wrote:
> To be blunt: Even though some of the existing patterns and conventions
> are unfashionable in 2015, consistency is a value by itself. Any
> partial "modernization" of the API destroys that consistency, and
> therefore value. So even if "use pa
On Thu, Jun 11, 2015 at 06:46:54PM +0100, Sean Harmer wrote:
> On Thursday 11 June 2015 19:42:55 Stephen Kelly wrote:
> > Marc Mutz wrote:
> > > On Thursday 11 June 2015 13:09:39 Stephen Kelly wrote:
> > >> I didn't make any claim that "the use of a namespace for a Qt library is
> > >> new".
> > >>
On Thursday 11. June 2015 18.47.40 Oswald Buddenhagen wrote:
> On Thu, Jun 11, 2015 at 03:43:15PM +0200, Simon Hausmann wrote:
> > On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
> > > On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> > > > Hi,
> > > >
> > > > Ok :
On Thu, Jun 11, 2015 at 08:55:24AM +, Knoll Lars wrote:
> >On Tuesday 09 June 2015 13:35:14 Oswald Buddenhagen wrote:
> >> On Tue, Jun 09, 2015 at 10:59:32AM +, Heikkinen Jani wrote:
> >> > Hi,
> >> >
> >> > I tried to create error reports about the findings to be able to
> >> > follow-up
On Wed, Jun 10, 2015 at 7:21 PM, Stottlemyer, Brett (B.S.)
wrote:
> Hi Alan. Hi Simon.
>
> On 6/10/15, 4:23 PM, "Alan Alpert" <4163654...@gmail.com> wrote:
>>On Wed, Jun 10, 2015 at 6:52 AM, Simon Hausmann
>> wrote:
>>> On Tuesday, June 09, 2015 01:23:29 PM Alan Alpert wrote:
A brief overvie
On Thu, Jun 11, 2015 at 7:11 AM, Hausmann Simon
wrote:
> Hi,
>
> I agree about the inconsistency in tense, that is a good argument against
> error(),
> although it is similarly unfortunate that the inconsistency in tense is more
> widespread than
> assumed.
>
> I'm not sure onErred or onErrored
Sean Harmer wrote:
>> I don't know. As far as I know deciding to use a namespace for this one
>> was done without discussion on the mailing list?
>
> There has been at least some discussion of namespaces in the past. For
> e.g.
>
> http://lists.qt-project.org/pipermail/development/2012-August/00
Sean Harmer wrote:
> On Thursday 11 June 2015 19:42:55 Stephen Kelly wrote:
>> Marc Mutz wrote:
>> > On Thursday 11 June 2015 13:09:39 Stephen Kelly wrote:
>> >> I didn't make any claim that "the use of a namespace for a Qt library
>> >> is new".
>> >>
>> >> Whatever you rebutted was not my claim
On Thursday 11 June 2015 19:42:55 Stephen Kelly wrote:
> Marc Mutz wrote:
> > On Thursday 11 June 2015 13:09:39 Stephen Kelly wrote:
> >> I didn't make any claim that "the use of a namespace for a Qt library is
> >> new".
> >>
> >> Whatever you rebutted was not my claim.
>
> So, you believe there
Marc Mutz wrote:
> On Thursday 11 June 2015 13:09:39 Stephen Kelly wrote:
>> I didn't make any claim that "the use of a namespace for a Qt library is
>> new".
>>
>> Whatever you rebutted was not my claim.
So, you believe there is no use in pursuing any of the questions I asked
here:
http://thr
On Thu, Jun 11, 2015 at 03:43:15PM +0200, Simon Hausmann wrote:
> On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
> > On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> > > Hi,
> > >
> > > Ok :) let's try with reduced qmake syntax (just variables, no functions).
> >
> On 11 Jun 2015, at 16:16, Thomas Senyk wrote:
>
…
> Nothing in the UI is entering/leaving screen or explicitly created/destroyed
> ... so I wonder where the new Node comes from.
>
> I'll look closer at what the Node is.
QSG_VISUALIZE=changes and/or QSG_RENDERER_DEBUG=changes might help pin
On 11.06.2015 15:50, Gunnar Sletta wrote:
> Hi Thomas,
>
> You are hitting one of the less ideal code paths with this testcase, see my
> comments below. I think the core problems are already outlined in
> https://bugreports.qt.io/browse/QTBUG-42853.
>
>> On 11 Jun 2015, at 14:32, Thomas Senyk wr
Hi,
I agree about the inconsistency in tense, that is a good argument against
error(),
although it is similarly unfortunate that the inconsistency in tense is more
widespread than
assumed.
I'm not sure onErred or onErrored is any better, to be honest. I think it's
more likely
to result in a ty
Hi Thomas,
You are hitting one of the less ideal code paths with this testcase, see my
comments below. I think the core problems are already outlined in
https://bugreports.qt.io/browse/QTBUG-42853.
> On 11 Jun 2015, at 14:32, Thomas Senyk wrote:
>
> Hi,
>
> currently trying to debug a weird
On Thursday, June 11, 2015 12:29:10 PM Oswald Buddenhagen wrote:
> On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> > Hi,
> >
> > Ok :) let's try with reduced qmake syntax (just variables, no functions).
> > We can still fall back to json if it's too clumsy.
> as you can "parse an
On 11/06/15 16:26, "Marc Mutz" wrote:
>On Thursday 11 June 2015 13:56:12 Knoll Lars wrote:
>> >- QAbstractVideoFilter should re-use QObject::d_ptr instead of adding
>>its
>> >own
>> > (though its unclear why it's inheriting QObject in the first place).
>>
>> It could, since the module depends o
On 11/06/15 16:33, "Marc Mutz" wrote:
>On Thursday 11 June 2015 13:43:15 Knoll Lars wrote:
>> Well, QSslEllipticCurve is problematic IMO. The class only contains one
>> int and accesses it inline. Since we might have other backends than
>> openssl implementing this in the future, I’d like have th
Marc Mutz schreef op 11-6-2015 om 16:33:
> BTW: Can someone send a summary of Qt 5.6 vs. C++11 to the ML, for
> those that couldn't attend?
I made notes. Available from here:
https://wiki.qt.io/QtCS2015_ModernCpp
André
___
Development mailing list
De
On Thursday 11 June 2015 13:43:15 Knoll Lars wrote:
> Well, QSslEllipticCurve is problematic IMO. The class only contains one
> int and accesses it inline. Since we might have other backends than
> openssl implementing this in the future, I’d like have this non inline and
> a qint64 as data type (s
On Thursday 11 June 2015 13:56:12 Knoll Lars wrote:
> >- QAbstractVideoFilter should re-use QObject::d_ptr instead of adding its
> >own
> > (though its unclear why it's inheriting QObject in the first place).
>
> It could, since the module depends on private apis in Qt Core anyway.
> Still, no sh
Hi,
currently trying to debug a weird behavior on a TI chip (armv7 with a
SGX GPU).
I have a fairly simple QML with a simple GridView with model:200 and
delegate:Text{text: "T#"+index}.
(it's a tiny bit more then that, but for argument sake this should be
enough)
Then an animation scrolling
On 11/06/15 14:19, "Marc Mutz" wrote:
>On Thursday 11 June 2015 12:29:06 Knoll Lars wrote:
>> A src/multimedia/camera/qcameraviewfindersettings.h
>
>Aprt from the changes already uploaded to Gerrit, I would suggest to use
>the
>new QCamera::FrameRateRange class instead of separate
>minimumFrameR
On 11/06/15 12:29, "Knoll Lars" wrote:
>qtwebengine
>
>A src/webenginewidgets/api/qwebenginedownloaditem.h
>A src/webenginewidgets/api/qwebengineprofile.h
>A src/webenginewidgets/api/qwebenginescript.h
>A src/webenginewidgets/api/qwebenginescriptcollection.h
Some smaller issues here, talked to
On 11/06/15 14:28, "Marc Mutz" wrote:
>On Thursday 11 June 2015 12:29:06 Knoll Lars wrote:
>> A src/network/ssl/qsslellipticcurve.h
>> A src/network/ssl/qsslpresharedkeyauthenticator.h
>
>Fine imho (but I was partially involved in their upbringing, so another
>set of
>eyes wouldn't hurt).
Well,
On Thursday 11 June 2015 13:09:39 Stephen Kelly wrote:
> On Thu, Jun 11, 2015 at 12:29 PM, Marc Mutz wrote:
> > I was listing namespaces that are used in Qt already. That was to rebut
> > your claim that the use of a namespace for a Qt library is new.
>
> I didn't make any claim that "the use of
On Thursday 11 June 2015 12:29:06 Knoll Lars wrote:
> A src/network/ssl/qsslellipticcurve.h
> A src/network/ssl/qsslpresharedkeyauthenticator.h
Fine imho (but I was partially involved in their upbringing, so another set of
eyes wouldn't hurt).
--
Marc Mutz | Senior Software Engineer
KDAB (Deut
On Thursday 11 June 2015 12:29:06 Knoll Lars wrote:
> Qt Location: The APIs underwent some changes from the 4.8 mobility API,
> but the module got a good review during Nokia times.
The QtMultimedia changes I uploaded and described in my previous mail show
what - IMHO - needs to be done to each of
On Thursday 11 June 2015 12:29:06 Knoll Lars wrote:
> A src/multimedia/camera/qcameraviewfindersettings.h
Aprt from the changes already uploaded to Gerrit, I would suggest to use the
new QCamera::FrameRateRange class instead of separate
minimumFrameRate/maximumFrameRate properties.
That *may* i
On Thu, Jun 11, 2015 at 12:29 PM, Marc Mutz wrote:
> I was listing namespaces that are used in Qt already. That was to rebut your
> claim that the use of a namespace for a Qt library is new.
I didn't make any claim that "the use of a namespace for a Qt library is new".
Whatever you rebutted was
Hi Steve,
On Wednesday 10 Jun 2015 21:03:32 Stephen Kelly wrote:
> >> 5) Qt3D namespace
> >>
> >> This is the first time that all classes in a library are in a namespace.
> >> Previously only enums (in various modules) and free functions (in
> >> QtConcurrent) have been put in namespaces.
> >>
On Wed, Jun 10, 2015 at 08:32:07PM +, Hausmann Simon wrote:
> Hi,
>
> Ok :) let's try with reduced qmake syntax (just variables, no functions). We
> can still fall back to json if it's too clumsy.
>
as you can "parse anything", what's wrong with parsing the function
calls from qt.pro? they m
On 11/06/15 10:55, "Knoll Lars" wrote:
>On 11/06/15 11:38, "Marc Mutz" wrote:
>
>>On Tuesday 09 June 2015 13:35:14 Oswald Buddenhagen wrote:
>>> On Tue, Jun 09, 2015 at 10:59:32AM +, Heikkinen Jani wrote:
>>> > Hi,
>>> >
>>> > I tried to create error reports about the findings to be able to
Hello,
It was agreed during this year's Qt Contributors Summit that, as of Qt 5.6,
QNX 6.5.0 will no longer be supported. Therefore, it is being marked as
deprecated for Qt 5.5. Among other reasons, the lack of proper C++11 support
stood as the main driving factor to this.
Support for QNX 6.6 is
On Thu, Jun 11, 2015 at 12:29:34PM +0200, Marc Mutz wrote:
> So even if we follow your reasoning, Qt3D is doing nothing that QtConcurrent
> and QtXmlPatterns, combined, haven't been doing for years. So the only new
> thing is that instead of separate libraries, it's now used in one.
>
the thing
On Thursday 11 June 2015 10:47:27 Stephen Kelly wrote:
> On Thu, Jun 11, 2015 at 11:49 AM, Marc Mutz wrote:
> > On Wednesday 10 June 2015 21:03:32 Stephen Kelly wrote:
> >> I would encourage a discussion of why this module needs namespaces when
> >> the rest of Qt gets by without them. There is c
Thiago Macieira schreef op 10-6-2015 om 18:42:
> On Wednesday 10 June 2015 15:14:07 Hausmann Simon wrote:
>> Hi,
>>
>> I think renaming the getter to lastError is nice! I however do like error as
>> signal name and it looks good in qml as onError:...
> "onError" screams of Basic to me...
> ON
On Wednesday 10 Jun 2015 21:09:15 Stephen Kelly wrote:
> Stephen Kelly wrote:
> > Sean Harmer wrote:
> >>> 1) The include/Qt3DCore/Window file doesn't have a Q prefix.
> >>>
> >>> as every other header does. Should probably be Qt3DWindow.
> >>
> >> Right, this actually needs removing and somethin
On 11/06/15 11:38, "Marc Mutz" wrote:
>On Tuesday 09 June 2015 13:35:14 Oswald Buddenhagen wrote:
>> On Tue, Jun 09, 2015 at 10:59:32AM +, Heikkinen Jani wrote:
>> > Hi,
>> >
>> > I tried to create error reports about the findings to be able to
>> > follow-up the progress. Please create new
On Thu, Jun 11, 2015 at 11:49 AM, Marc Mutz wrote:
> On Wednesday 10 June 2015 21:03:32 Stephen Kelly wrote:
>> I would encourage a discussion of why this module needs namespaces when
>> the rest of Qt gets by without them. There is certainly a consistency
>> angle.
>
> I think you come a few yea
On Wednesday 10 June 2015 21:03:32 Stephen Kelly wrote:
> I would encourage a discussion of why this module needs namespaces when
> the rest of Qt gets by without them. There is certainly a consistency
> angle.
I think you come a few years late :)
QtPatternist
QtConcurrent
QTest
QV4
QtQml
QtDecl
On Tuesday 09 June 2015 13:35:14 Oswald Buddenhagen wrote:
> On Tue, Jun 09, 2015 at 10:59:32AM +, Heikkinen Jani wrote:
> > Hi,
> >
> > I tried to create error reports about the findings to be able to
> > follow-up the progress. Please create new one if something is missing.
>
> the point wa
Hi all,
We have new snapshot in
Linux: https://download.qt.io/snapshots/qt/5.5/5.5.0-rc/2015-06-10_111/
Mac: https://download.qt.io/snapshots/qt/5.5/5.5.0-rc/2015-06-10_93/
Windows: https://download.qt.io/snapshots/qt/5.5/5.5.0-rc/2015-06-10_89/
Src: https://download.qt.io/snapshots/qt/5.5/5.5
onError is immediately understood by all sentient beings in the universe.
martin
From: development-bounces+martin.smith=theqtcompany@qt-project.org
on behalf of
Christian Kandeler
Sent: Thursday, June 11, 2015 9:21 AM
To: development@qt-project.org
On 06/10/2015 06:42 PM, Thiago Macieira wrote:
> On Wednesday 10 June 2015 15:14:07 Hausmann Simon wrote:
>> Hi,
>>
>> I think renaming the getter to lastError is nice! I however do like error as
>> signal name and it looks good in qml as onError:...
>
> "onError" screams of Basic to me...
>
48 matches
Mail list logo
