--e89a8f2345758059cb052f0eb386
Content-Type: text/plain; charset=UTF-8

Steve,

Thank you for the input. I will probably take Qt out of the paper since it
really does not match what I am trying to convey.

There are other C++ related event handling libraries out there that better
match.

Thanks,

Brett

On Sun, Mar 27, 2016 at 1:52 PM, Stephen Kelly <steveire@gmail.com> wrote:

> Brett Searles wrote:
>
> > Bjorn,
> >
> > That is because QT and signals have a reference point for P0249,
>
> Hi Brett,
>
> I've just had a quick look over P0249. Thanks for your work on this.
>
> I have feedback for you to improve the accuracy of your paper and your
> understanding of Qt.
>
> The context of my feedback is that I have almost a decade of experience
> using Qt and I found your paper confusing in how it references Qt, and in
> claims of fact made about it.
>
> 1) QT is Apple QuickTime. Qt has a lowercase 't'.
>
> 2) You refer to Qt 4.8, but should instead refer to Qt 5. If there are any
> differences, the Qt 5 semantics/behaviors represent an updated design.
>
> 3) Your paper contains the following text:
>
>   QT has a library that supports event handling with a base object, QEvent,
>   and have incorporated the Boost Library how to handle actions around
>   certain window features, like menus. [QT1]
>
> As an english native speaker, I do not know what this text is attempting to
> communicate. Grammatically it doesn't seem to mean anything.
>
> The [QT1] reference simply refers to a Qt documentation page which makes no
> reference to Boost.
>
> As a matter of fact, no Qt version incorporates any Boost Library for
> anything. For the avoidance of doubt, Qt doesn't use Boost to handle
> actions
> around certain window features, like menus.
>
> 4) The paper contains the following text:
>
>   In order to create a custom event in QT, the developer needs to create
>   an object based on the parent event.
>
> You probably mean 'create an object inheriting QEvent'. You have already
> referred to QEvent, so it would be less confusing than 'based on the parent
> event'.  If 'based on the parent event' is not referring to inheritance of
> QEvent, I suggest you use different wording to communicate what it really
> means. Strive for accuracy and clarity.
>
> 5) The paper contains the following text:
>
>   QT has a virtual base class that registers event types defined either by
>   QT or a developer creating custom events.  QT uses the Observer Pattern
>   where the QApplication object notifies any events in a collection
>   that are registered in the base class.[QT2]
>
> At least part of this is redundant with content a few lines above.
>
> Events are not 'registered with the base class'. I don't know what you are
> referring to.
>
> Again, your [QT2] reference seems to be a link to a docs page which is
> unrelated 'registering in the base class' or any other claims of fact that
> seem implicit in what you wrote. Or, maybe I misunderstand what you wrote
> because it is not clear as written and you could consider rewriting it.
>
> 6) The paper contains the following text:
>
>   QT also offers an adaptation of the Boost Signal Library. The usage is
>   limited to a few objects, yet it does have that feature.
>
> As a claim of fact, I have no idea what you are referring to. Qt does not
> offer an 'adaption of the Boost Signal Library'.
>
> Again, maybe what you want to say is actually something different, and you
> should strive for more accuracy and clarity in what you write.
>
> 7) Qt signals and slots are very different to events
>
> The reference to QSignalMapper doesn't seem to be relevant. Especially the
> claim that it is a strange class because it invokes one slot is itself
> strange - the class behaves exactly as designed. A different class can be
> implemented to invoke multiple slots, but again that has nothing to do with
> the event system.
>
>
>
> In summary, for your next draft I suggest you get a thorough proof read
> from
> someone who is a native speaker and who is familiar with Qt to help you
> write accurately about it, remove things that are not relevant etc.
>
> Thanks,
>
> Steve.
>
> --
> You received this message because you are subscribed to the Google Groups
> "ISO C++ Standard - Future Proposals" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to std-proposals+unsubscribe@isocpp.org.
> To post to this group, send email to std-proposals@isocpp.org.
> To view this discussion on the web visit
> https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/56f8481d.918e1c0a.fe25d.ffffae81%40mx.google.com
> .
>

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAN1bbVKhYK-2huycVeK1m9KCZeV_ia%3DoTFuHgcdPjaTQiChw3Q%40mail.gmail.com.

--e89a8f2345758059cb052f0eb386
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Steve,</div><div><br></div><div>Thank you for the inp=
ut. I will probably take Qt out of the paper since it really does not match=
 what I am trying to convey.</div><div><br></div><div>There are other C++ r=
elated event handling libraries out there that better match.</div><div><br>=
</div><div>Thanks,</div><div><br></div><div>Brett</div></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Sun, Mar 27, 2016 at 1:52 PM=
, Stephen Kelly <span dir=3D"ltr">&lt;<a href=3D"mailto:steveire@gmail.com"=
 target=3D"_blank">steveire@gmail.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex"><span>Brett Searles wrote:<br>
<br>
&gt; Bjorn,<br>
&gt;<br>
&gt; That is because QT and signals have a reference point for P0249,<br>
<br>
</span>Hi Brett,<br>
<br>
I&#39;ve just had a quick look over P0249. Thanks for your work on this.<br=
>
<br>
I have feedback for you to improve the accuracy of your paper and your<br>
understanding of Qt.<br>
<br>
The context of my feedback is that I have almost a decade of experience<br>
using Qt and I found your paper confusing in how it references Qt, and in<b=
r>
claims of fact made about it.<br>
<br>
1) QT is Apple QuickTime. Qt has a lowercase &#39;t&#39;.<br>
<br>
2) You refer to Qt 4.8, but should instead refer to Qt 5. If there are any<=
br>
differences, the Qt 5 semantics/behaviors represent an updated design.<br>
<br>
3) Your paper contains the following text:<br>
<br>
=C2=A0 QT has a library that supports event handling with a base object, QE=
vent,<br>
=C2=A0 and have incorporated the Boost Library how to handle actions around=
<br>
=C2=A0 certain window features, like menus. [QT1]<br>
<br>
As an english native speaker, I do not know what this text is attempting to=
<br>
communicate. Grammatically it doesn&#39;t seem to mean anything.<br>
<br>
The [QT1] reference simply refers to a Qt documentation page which makes no=
<br>
reference to Boost.<br>
<br>
As a matter of fact, no Qt version incorporates any Boost Library for<br>
anything. For the avoidance of doubt, Qt doesn&#39;t use Boost to handle ac=
tions<br>
around certain window features, like menus.<br>
<br>
4) The paper contains the following text:<br>
<br>
=C2=A0 In order to create a custom event in QT, the developer needs to crea=
te<br>
=C2=A0 an object based on the parent event.<br>
<br>
You probably mean &#39;create an object inheriting QEvent&#39;. You have al=
ready<br>
referred to QEvent, so it would be less confusing than &#39;based on the pa=
rent<br>
event&#39;.=C2=A0 If &#39;based on the parent event&#39; is not referring t=
o inheritance of<br>
QEvent, I suggest you use different wording to communicate what it really<b=
r>
means. Strive for accuracy and clarity.<br>
<br>
5) The paper contains the following text:<br>
<br>
=C2=A0 QT has a virtual base class that registers event types defined eithe=
r by<br>
=C2=A0 QT or a developer creating custom events.=C2=A0 QT uses the Observer=
 Pattern<br>
=C2=A0 where the QApplication object notifies any events in a collection<br=
>
=C2=A0 that are registered in the base class.[QT2]<br>
<br>
At least part of this is redundant with content a few lines above.<br>
<br>
Events are not &#39;registered with the base class&#39;. I don&#39;t know w=
hat you are<br>
referring to.<br>
<br>
Again, your [QT2] reference seems to be a link to a docs page which is<br>
unrelated &#39;registering in the base class&#39; or any other claims of fa=
ct that<br>
seem implicit in what you wrote. Or, maybe I misunderstand what you wrote<b=
r>
because it is not clear as written and you could consider rewriting it.<br>
<br>
6) The paper contains the following text:<br>
<br>
=C2=A0 QT also offers an adaptation of the Boost Signal Library. The usage =
is<br>
=C2=A0 limited to a few objects, yet it does have that feature.<br>
<br>
As a claim of fact, I have no idea what you are referring to. Qt does not<b=
r>
offer an &#39;adaption of the Boost Signal Library&#39;.<br>
<br>
Again, maybe what you want to say is actually something different, and you<=
br>
should strive for more accuracy and clarity in what you write.<br>
<br>
7) Qt signals and slots are very different to events<br>
<br>
The reference to QSignalMapper doesn&#39;t seem to be relevant. Especially =
the<br>
claim that it is a strange class because it invokes one slot is itself<br>
strange - the class behaves exactly as designed. A different class can be<b=
r>
implemented to invoke multiple slots, but again that has nothing to do with=
<br>
the event system.<br>
<br>
<br>
<br>
In summary, for your next draft I suggest you get a thorough proof read fro=
m<br>
someone who is a native speaker and who is familiar with Qt to help you<br>
write accurately about it, remove things that are not relevant etc.<br>
<br>
Thanks,<br>
<br>
Steve.<br>
<span><br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals%2Bunsubscribe@isocpp.org">std-propo=
sals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br>
</span>To view this discussion on the web visit <a href=3D"https://groups.g=
oogle.com/a/isocpp.org/d/msgid/std-proposals/56f8481d.918e1c0a.fe25d.ffffae=
81%40mx.google.com" target=3D"_blank" rel=3D"noreferrer">https://groups.goo=
gle.com/a/isocpp.org/d/msgid/std-proposals/56f8481d.918e1c0a.fe25d.ffffae81=
%40mx.google.com</a>.<br>
</blockquote></div><br></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CAN1bbVKhYK-2huycVeK1m9KCZeV_ia%3DoTF=
uHgcdPjaTQiChw3Q%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAN1bbVKhYK-2hu=
ycVeK1m9KCZeV_ia%3DoTFuHgcdPjaTQiChw3Q%40mail.gmail.com</a>.<br />

--e89a8f2345758059cb052f0eb386--

.

On domingo, 27 de mar=C3=A7o de 2016 22:52:40 PDT Stephen Kelly wrote:
>   QT also offers an adaptation of the Boost Signal Library. The usage is =
=20
>   limited to a few objects, yet it does have that feature.
>=20
> As a claim of fact, I have no idea what you are referring to. Qt does not=
=20
> offer an 'adaption of the Boost Signal Library'.

More to the point, Boost contains an adaptation of Qt's signal/slot mechani=
sm,=20
which predates Boost by over a decade.

--=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

--=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp=
..org/d/msgid/std-proposals/6565280.OzVpTKslJe%40tjmaciei-mobl4.

.

Brett Searles wrote:

> Steve,
>
> Thank you for the input. I will probably take Qt out of the paper since it
> really does not match what I am trying to convey.

Ok, that sounds like an easy way to solve all of the reported problems at
once. :)

Thanks,

Steve.

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/56f96516.aa0ac20a.3c345.37a4%40mx.google.com.

.

Brett Searles wrote:

> Steve,
>
> Thank you for the input. I will probably take Qt out of the paper since it
> really does not match what I am trying to convey.

Ok, that sounds like an easy way to solve all of the reported problems at
once. :)

Thanks,

Steve.

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/56f96514.aa0ac20a.3c345.379f%40mx.google.com.

.

Considering the paper talks about event handling and signals/slots, seems o=
dd no to mention Qt, however.

Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A0portable=C2=A0Babbage=C2=A0Devi=
ce
=C2=A0 Original Message =C2=A0
From: Stephen Kelly
Sent: Monday, March 28, 2016 1:08 PM
To: std-proposals@isocpp.org
Reply To: std-proposals@isocpp.org
Subject: [std-proposals] Re: Re: About the naming of Signals and Slots (Gen=
eral Thoughts)

Brett Searles wrote:

> Steve,
>=20
> Thank you for the input. I will probably take Qt out of the paper since i=
t
> really does not match what I am trying to convey.

Ok, that sounds like an easy way to solve all of the reported problems at=
=20
once. :)

Thanks,

Steve.

--=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp=
..org/d/msgid/std-proposals/56f96516.aa0ac20a.3c345.37a4%40mx.google.com.

--=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp=
..org/d/msgid/std-proposals/20160328171317.4890705.81044.8765%40gmail.com.

.

Tony V E wrote:

> Considering the paper talks about event handling and signals/slots, seems
> odd no to mention Qt, however.

Yes, I agree that papers should have a fact-based exploration of widely used
prior art including Qt. But not having that is better than the wild
inaccuracies currently in the paper. I think I commented on literally every
sentence about Qt in the paper pointing out that what is written is wrong
unclear or misleading.

I don't think authors should write pseudo-authoritively (or trying to appear
authoritive/correct) about things they don't know about or have any
experience with just to tick the 'we considered Qt here' box :).

Thanks,

Steve.

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/56f968da.aa0ac20a.3c345.3c9f%40mx.google.com.

.

On segunda-feira, 28 de mar=C3=A7o de 2016 19:24:41 PDT Stephen Kelly wrote=
:
> Tony V E wrote:
> > Considering the paper talks about event handling and signals/slots, see=
ms
> > odd no to mention Qt, however.
>=20
> Yes, I agree that papers should have a fact-based exploration of widely u=
sed
> prior art including Qt. But not having that is better than the wild
> inaccuracies currently in the paper. I think I commented on literally eve=
ry
> sentence about Qt in the paper pointing out that what is written is wrong
> unclear or misleading.
>=20
> I don't think authors should write pseudo-authoritively (or trying to app=
ear
> authoritive/correct) about things they don't know about or have any
> experience with just to tick the 'we considered Qt here' box :).

Agreed, but for a paper about input handling and other events, things that =
are=20
required for GUI and UX, ignoring Qt is also not an option. It's like ignor=
ing=20
at least half of the prior art.

--=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

--=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp=
..org/d/msgid/std-proposals/3067670.6sv4vCusH7%40tjmaciei-mobl4.

.