Re: [Development] Control 2 : Does StackView garbage collect popped items ?

[ekke]

Am 23.02.18 um 18:25 schrieb Fabrice Salvaire:
> Dear all,
>
> I am experimenting a way to implement a wizard interface featuring a
> next and previous page navigation using QML Control 2.
>
> I tried to achieve this using StackView but I receive the error
> "TypeError: Type error' when I try to access popped items later, for
> example with console.info(popped_item_array)  It looks like a kind of
> garbage collection of the Qt object returned by push and pop.  But I
> could not figure out any explanation of this behaviour on the Qt doc
> https://doc-snapshots.qt.io/qt5-5.11/qml-qtquick-controls2-stackview.html#unwinding-items-via-pop
>
> Note: I hope I am on the right channel for such technical question.
Hi Fabrice,

the developers list is for the developers of Qt

you should use the 'interest' list (users of Qt) or ask at the Forum
https://forum.qt.io/category/12/qml-and-qt-quick

BTW: here's a blog article and demo app at github about QQC2 StackView:
https://appbus.wordpress.com/2016/05/27/stacked-pages-app/ it's from
2016 - so not all is covered but perhaps will give you some ideas

ekke
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Control 2 : Does StackView garbage collect popped items ?

[Fabrice Salvaire]

Dear all,

I am experimenting a way to implement a wizard interface featuring a 
next and previous page navigation using QML Control 2.


I tried to achieve this using StackView but I receive the error 
"TypeError: Type error' when I try to access popped items later, for 
example with console.info(popped_item_array)  It looks like a kind of 
garbage collection of the Qt object returned by push and pop.  But I 
could not figure out any explanation of this behaviour on the Qt doc 
https://doc-snapshots.qt.io/qt5-5.11/qml-qtquick-controls2-stackview.html#unwinding-items-via-pop


Note: I hope I am on the right channel for such technical question.

Cheers,

Fabrice


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Adam Treat]

"If many users spend much time doing a "thing", does that mean that this
is most important to them? Or that it is most fun to do?"

Personally, I think we can table the discussion of how to interpret 
non-existent data for a plug-in that does not exist in a thread about whether 
to open a repo.


From: Development  on 
behalf of Robert Löhning 
Sent: Friday, February 23, 2018 9:59:01 AM
To: Edward Welbourne; André Pönitz
Cc: development@qt-project.org; qt-crea...@qt-project.org; Ryein Goddard
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator

Am 23.02.2018 um 11:54 schrieb Edward Welbourne:
> André Pönitz (22 February 2018 20:05)
>> Any number for a "measured" value for rate of crashes or memory leaks
>> is uninteresting for me when I run into the problem myself reqularly.
>> And trust me, I do.
>
> I trust you.
> It is, however, possible your usage patterns of the UI are not typical;
> consequently, you'll prioritise the bugs you see most often; which might
> not be the bugs most often encountered by other users.  Analytics may
> give you the data to know the pain points everyone else is as acutely
> aware of as you are of the pain points you meet most often.
>
>> As someone who has been working on Qt Creator for more than a decade I
>> *do* know about issues in the IDE by my own use of it, by the
>> significant backlog of bug reports in JIRA, and by interacting with
>> (sometimes referred to as "talking to") actual users.
>>
>> The currently 399 open issues assigned to me personally would already
>> be enough to keep me busy for approximately a $WHILE, full time, not
>> including time spent in review processes etc.
>>
>> I certainly do not need another input channel that makes me spent time
>> on guessing how the information that "user A spent at time B an amount
>> of C minutes working on project named D" will translate into making my
>> work more efficient
>
> The proposed system provides anonymised and presumably aggregated data;
> so you won't be given, much less asked to evaluate, information about a
> specific user A doing things at a specific time B; your objection is a
> straw man.  You'd be getting data on what proportion of users spend what
> proportions of their time doing which things.  In particular, knowing
> which bugs bite most users most often might not be entirely useless when
> it comes to prioritising which bug to fix first.

If many users spend much time doing a "thing", does that mean that this
is most important to them? Or that it is most fun to do? Or does it just
mean that the design is so bad that they lose lots of time there and
can't use it efficiently?

> This won't enable you to write new features any faster or fix bugs any
> faster; but it may enable you to prioritise the things that are causing
> most pain to most users, and the things that would give the most win to
> the most users.  *That* is what analytics is good for.  The fact that it
> doesn't do a bunch of other things is beside the point, and no reason to
> reject it out of hand.
>
> Now, fortunately for you, most of the folk who use the product you work
> on are in fact software developers, so may well have similar habits to
> yours; so if the scope of this project is only Qt Creator, it may well
> be a waste of time; and, if it's intended to be a more general tool,
> this may also be a reason to *not* focus on Qt Creator as initial
> test-bed, as seems to be the present plan - that's apt to skew what we
> develop to be something that only works when the user-base thinks like
> the developers, which is not where (honest, open, ethical) analytics is
> at its best - where it reveals things to the developer that users see
> all the time, but the developer never encounters.
>
>Eddy.
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Tino Pyssysalo]

I’ll clarify little bit, as my earlier comment about “any backend” has been 
confusing. I requested a repo for a QtCreator analytics plugin, but we realized 
why not to use a similar solution in other tools as well. I want to concentrate 
on a Qt Creator plugin first to fully understand the problem domain. Once that 
is done we can discuss how to move forward with this project”. Our intention is 
usage data collection, but nothing else at this point. Obviously, we plan to 
use the collected data to improve Qt. As a concrete example, we have provided a 
lot of nice features in Qt Quick Designer in the recent Qt Creator releases, 
but we have no idea, if the use of Qt Quick Designer has changed in any way. 
This kind of data would be very valuable to us.
--
Tino



On 23/02/2018, 14.28, "Adam Treat" > 
wrote:

+1 to playground

This is open source... by all means experiment! As long as no laws are being 
broken and no licenses violated, then if their is an itch... scratch it!

The person who codes decides. We can all judge the results by looking at the 
code. Useless to have stop energy about a plug-in that does not yet exist. It 
could be great or it could be a lousy failure, but opening up a playgrounds 
repo costs no one anything.


From: Development  on 
behalf of Simon Hausmann 
Sent: Friday, February 23, 2018 3:00:33 AM
To: Pasi Keränen; Tino Pyssysalo; Tuukka Turunen; qt-crea...@qt-project.org; 
development@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator


Hi,



Given that no plan has been presented about how this is intended to work in 
terms of backend or API scope, I stand with my -1 for a qt/ or qt-creator/ 
repo. If there exists no plan yet but the desire to experiment, then I'm with 
Pasi here and would suggest a repository in the playground scope. I think 
either analytics or telemetry make sense to have in the name. Firebase for 
example uses the term analytics in their API and Mozilla uses the term 
telemetry for the service of collecting performance and usage info for Firefox.





Simon


From: Pasi Keränen
Sent: Friday, February 23, 2018 8:53:33 AM
To: Maurice Kalinowski; Tino Pyssysalo; Simon Hausmann; Tuukka Turunen; 
qt-crea...@qt-project.org; development@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator


Hi,



Repos can be relocated to new homes if really needed, but I think it’s fair to 
say more generic location is definitely preferred from Qt 3D Studio point of 
view.



To make this even easier I’d even start with a playground repo if nothing else 
can be found. Qt has always been (despite our vocal and sometimes a bit harsh 
dialogue) inclusive, so it should be fine to go and experiment with all things 
UI related. Just to see if something is worth the effort or not.



Regards,

Pasi



From: Development  on 
behalf of Maurice Kalinowski 
Date: Friday, 23 February 2018 at 9.33
To: Tino Pyssysalo , Simon Hausmann 
, Tuukka Turunen , 
"qt-crea...@qt-project.org" , 
"development@qt-project.org" 
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator



“The idea is to develop a generic library/plugin, which anyone could use for 
analytics”



If that is the case, then qt-creator/telemetry is the wrong repository to ask 
for. If you are aiming at something generic, then it should be qt/



Maurice



Von: Qt-creator 
[mailto:qt-creator-bounces+maurice.kalinowski=qt...@qt-project.org] Im Auftrag 
von Tino Pyssysalo
Gesendet: Thursday, February 22, 2018 2:59 PM
An: Simon Hausmann ; Tuukka Turunen 
; qt-crea...@qt-project.org; development@qt-project.org
Betreff: Re: [Qt-creator] [Development] Requesting repository for telemetry 
plugin in Qt Creator



Hi,



The idea is to develop a generic library/plugin, which anyone could use for 
analytics. The backend can be any storage and The Qt Company does not provide 
that.



We plan to use the same backend, which we already use in online installers to 
collect statistics about installations. At least in case of Qt Creator, the 
plan is to make some analysis results available for the community. Obviously, 
we do not do that for our commercial tooling.



Analytics is opt-in and disabled by default in Qt Creator. We plan to ask user 
in the installer, if the user wish to participate in Qt UX improvement. If the 
answers is no, the analytics plugin is never installed.  When the creator is 
started for the first time, it will show a dialog, consisting a 

[Development] Qt 5.11 Beta1 snapshot available

[Jani Heikkinen]

Hi,
First Qt 5.11 Beta1 snapshot available via online installer. Please take a tour 
to see what is working and what not

Have a nice weekend!

br,
jani
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Prebuilt 32-bit versjon for MSVC 2017

[Roland Winklmeier]

2018-02-21 13:44 GMT+01:00 Harald Kjølberg :

>
> Hi,
>
> Currently Qt ships with 32-bit binaries for MSVC 2015, but not for MSVC
> 2017. The Qt Company have received requests for adding prebuilt 32-bit
> binaries also for MSVC 2017. By adding more prebuilt binaries, we increase
> the complexity, and add to the overall maintenance of our QA system. Our
> preferred approach would be to add binaries for MSVC 2017 and remove the
> binaries for MSVC 2015, as the numbers of binaries in the build remains the
> same. It will still be possible to manually build Qt for MSVC 2015, in the
> same way as it is possible to manually build for MSVC 2017 today. Feedback
> and viewpoints are much appreciated and will enable us to make the best
> possible decision.
>

I'm using MSVC 2017 with Qt5 2015 prebuilt binaries. I never had issues
with this combination so far, but still would appreciate to have the also
have the 32 bit binaries prebuilt with 2017.
So I'm happy to hear that this is considered.

A little bit offtopic:
I think those discussions about prebuilt binaries would be less
controversal, if it would be easier to produce custom Qt installers. I'm
aware that I can build 32 bit with MSVC 2017 on my own, but creating an
installer for my colleagues is a mystery to me. Yes, its easy enough to
_build_ Qt yourself. I regularly do that. But its a pain to produce any
kind of installers to share it with team members or relocate the built. I
would produce more custom prebuilts of Qt, if the documentation about how
to create custom installers is up to date and accurate. I tried once to
follow http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/README
but it was so much dependent on the Qt CI infrastructure (shares, node
names etc), hard to follow and presumably outdated (it referenced Qt 5.5).

R.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Prebuilt 32-bit versjon for MSVC 2017

[Markus Maier]

Hello,

just to add my opinion as a current user of the MSVC 2015 32 bit binaries.

When selecting an MSVC version to use with Qt, one should keep in mind that
Microsoft tends to change things in the compilers even in minor releases. I
had quite some issues with one of the updates of MSVC2013 which broke
things in my code together with a prebuilt version of Qt. Something similar
might happen again when Microsoft fixes the bug mentioned by Thiago.

That's why I decided for my projects to always stick with the MSVC version
before the current version, where updates are not likely to break something
in builds anymore. I believe the same reasons should also apply for
choosing a MSVC version for prebuilt 32 bit binaries.

Another point might be: whoever uses prebuilt 32 bit binaries now and wants
to switch to a static build of Qt would currently be forced to downgrade
the compiler because MSVC 2017 as of now doesn't support static builds of
Qt (QTBUG-59721).

Best regards
Markus Maier
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Robert Löhning]

Am 23.02.2018 um 11:54 schrieb Edward Welbourne:

André Pönitz (22 February 2018 20:05)

Any number for a "measured" value for rate of crashes or memory leaks
is uninteresting for me when I run into the problem myself reqularly.
And trust me, I do.


I trust you.
It is, however, possible your usage patterns of the UI are not typical;
consequently, you'll prioritise the bugs you see most often; which might
not be the bugs most often encountered by other users.  Analytics may
give you the data to know the pain points everyone else is as acutely
aware of as you are of the pain points you meet most often.


As someone who has been working on Qt Creator for more than a decade I
*do* know about issues in the IDE by my own use of it, by the
significant backlog of bug reports in JIRA, and by interacting with
(sometimes referred to as "talking to") actual users.

The currently 399 open issues assigned to me personally would already
be enough to keep me busy for approximately a $WHILE, full time, not
including time spent in review processes etc.

I certainly do not need another input channel that makes me spent time
on guessing how the information that "user A spent at time B an amount
of C minutes working on project named D" will translate into making my
work more efficient


The proposed system provides anonymised and presumably aggregated data;
so you won't be given, much less asked to evaluate, information about a
specific user A doing things at a specific time B; your objection is a
straw man.  You'd be getting data on what proportion of users spend what
proportions of their time doing which things.  In particular, knowing
which bugs bite most users most often might not be entirely useless when
it comes to prioritising which bug to fix first.


If many users spend much time doing a "thing", does that mean that this 
is most important to them? Or that it is most fun to do? Or does it just 
mean that the design is so bad that they lose lots of time there and 
can't use it efficiently?



This won't enable you to write new features any faster or fix bugs any
faster; but it may enable you to prioritise the things that are causing
most pain to most users, and the things that would give the most win to
the most users.  *That* is what analytics is good for.  The fact that it
doesn't do a bunch of other things is beside the point, and no reason to
reject it out of hand.

Now, fortunately for you, most of the folk who use the product you work
on are in fact software developers, so may well have similar habits to
yours; so if the scope of this project is only Qt Creator, it may well
be a waste of time; and, if it's intended to be a more general tool,
this may also be a reason to *not* focus on Qt Creator as initial
test-bed, as seems to be the present plan - that's apt to skew what we
develop to be something that only works when the user-base thinks like
the developers, which is not where (honest, open, ethical) analytics is
at its best - where it reveals things to the developer that users see
all the time, but the developer never encounters.

Eddy.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Adam Treat]

+1 to playground

This is open source... by all means experiment! As long as no laws are being 
broken and no licenses violated, then if their is an itch... scratch it!

The person who codes decides. We can all judge the results by looking at the 
code. Useless to have stop energy about a plug-in that does not yet exist. It 
could be great or it could be a lousy failure, but opening up a playgrounds 
repo costs no one anything.


From: Development  on 
behalf of Simon Hausmann 
Sent: Friday, February 23, 2018 3:00:33 AM
To: Pasi Keränen; Tino Pyssysalo; Tuukka Turunen; qt-crea...@qt-project.org; 
development@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator


Hi,


Given that no plan has been presented about how this is intended to work in 
terms of backend or API scope, I stand with my -1 for a qt/ or qt-creator/ 
repo. If there exists no plan yet but the desire to experiment, then I'm with 
Pasi here and would suggest a repository in the playground scope. I think 
either analytics or telemetry make sense to have in the name. Firebase for 
example uses the term analytics in their API and Mozilla uses the term 
telemetry for the service of collecting performance and usage info for Firefox.



Simon


From: Pasi Keränen
Sent: Friday, February 23, 2018 8:53:33 AM
To: Maurice Kalinowski; Tino Pyssysalo; Simon Hausmann; Tuukka Turunen; 
qt-crea...@qt-project.org; development@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator


Hi,



Repos can be relocated to new homes if really needed, but I think it’s fair to 
say more generic location is definitely preferred from Qt 3D Studio point of 
view.



To make this even easier I’d even start with a playground repo if nothing else 
can be found. Qt has always been (despite our vocal and sometimes a bit harsh 
dialogue) inclusive, so it should be fine to go and experiment with all things 
UI related. Just to see if something is worth the effort or not.



Regards,

Pasi



From: Development  on 
behalf of Maurice Kalinowski 
Date: Friday, 23 February 2018 at 9.33
To: Tino Pyssysalo , Simon Hausmann 
, Tuukka Turunen , 
"qt-crea...@qt-project.org" , 
"development@qt-project.org" 
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator



“The idea is to develop a generic library/plugin, which anyone could use for 
analytics”



If that is the case, then qt-creator/telemetry is the wrong repository to ask 
for. If you are aiming at something generic, then it should be qt/



Maurice



Von: Qt-creator 
[mailto:qt-creator-bounces+maurice.kalinowski=qt...@qt-project.org] Im Auftrag 
von Tino Pyssysalo
Gesendet: Thursday, February 22, 2018 2:59 PM
An: Simon Hausmann ; Tuukka Turunen 
; qt-crea...@qt-project.org; development@qt-project.org
Betreff: Re: [Qt-creator] [Development] Requesting repository for telemetry 
plugin in Qt Creator



Hi,



The idea is to develop a generic library/plugin, which anyone could use for 
analytics. The backend can be any storage and The Qt Company does not provide 
that.



We plan to use the same backend, which we already use in online installers to 
collect statistics about installations. At least in case of Qt Creator, the 
plan is to make some analysis results available for the community. Obviously, 
we do not do that for our commercial tooling.



Analytics is opt-in and disabled by default in Qt Creator. We plan to ask user 
in the installer, if the user wish to participate in Qt UX improvement. If the 
answers is no, the analytics plugin is never installed.  When the creator is 
started for the first time, it will show a dialog, consisting a list of 
collected data items and an option to enable/disable the plugin. There will be 
a new output pane, which shows collected data, conversions methods, if any 
used, and transmitted data to the user.

--

Tino





On 22/02/2018, 15.26, "Simon Hausmann" 
> wrote:



Hi,



Can you provide a bit more information about how this plugin / frontend fits 
into the Qt project? Where is the collected data sent to and how is it 
accessible to the community?



(-1 from me, as I think this needs to be clarified)



Simon



From: Development 
>
 on behalf of Tuukka Turunen >
Sent: Thursday, February 22, 2018 

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Volker Krause]

On Friday, 23 February 2018 11:45:01 CET Simon Hausmann wrote:
> I just had a look at KUserFeedback and I'm impressed.
> 
> Looks like a really good combination of very useful providers, UI,
> administration and server bits - all in one relatively small package. And
> for those not liking the PHP server part, it appears that that would be a
> piece that is relatively easy to replace - although the code looks very
> clean.

I don't like the PHP part either, it was just the easiest technology to deploy 
on the available servers at the time. The interface is very simple JSON/REST 
though, so it's indeed easy to explore alternatives.

> Also very cool that you're using this in production for GammaRay.
> 
> /That/ is something that would be awesome as part of the Qt project IMHO.
> Sensible scope, production tested and easy to use. (But I can totally
> understand that it might make more sense to remain in the KDE frameworks)

Contribution of the entire KUserFeedback framework under the Qt CLA seems 
unlikely, but as indicated during previous discussions, a conversation about 
finding a more acceptable FOSS license to address the commercial user concerns 
is certainly possible.

Regards,
Volker


> 
> From: Development 
> on behalf of Volker Krause  Sent: Friday, February
> 23, 2018 10:20:23 AM
> To: development@qt-project.org; qt-crea...@qt-project.org
> Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry
> plugin in Qt Creator
> 
> Hi,
> 
> as numerous people have asked me to comment on this by now, let me just do
> that here publicly (representing KDE's KUserFeedback, not KDAB):
> 
> Tino is well aware of KUserFeedback, we discussed that last year already in
> detail. So it definitely was considered as a possible solution for this.
> I do not know why it was ultimately decided to implement a new framework, in
> particular if that's due to conceptual or technical reasons, or licensing.
> 
> 
> With the KDAB hat back on, we do use KUserFeedback in GammaRay since mid
> last year, and it has so far provided a few useful insights, in particular
> regarding to what extend we still need to support ancient Qt versions. But
> as with any data, it's not the ultimate answer to all questions, and you
> need to be very careful how to interpret it obviously. We have so far not
> received any negative feedback with e.g. privacy concerns, but the approach
> KUserFeedback takes there by default (and that we followed in GammaRay) is
> intentionally very restrained.
> 
> Regards,
> Volker
> 
> On Thursday, 22 February 2018 14:58:55 CET Tino Pyssysalo wrote:
> > Hi,
> > 
> > The idea is to develop a generic library/plugin, which anyone could use
> > for
> > analytics. The backend can be any storage and The Qt Company does not
> > provide that.
> > 
> > We plan to use the same backend, which we already use in online installers
> > to collect statistics about installations. At least in case of Qt Creator,
> > the plan is to make some analysis results available for the community.
> > Obviously, we do not do that for our commercial tooling.
> > 
> > Analytics is opt-in and disabled by default in Qt Creator. We plan to ask
> > user in the installer, if the user wish to participate in Qt UX
> > improvement. If the answers is no, the analytics plugin is never
> > installed.
> > 
> >  When the creator is started for the first time, it will show a dialog,
> > 
> > consisting a list of collected data items and an option to enable/disable
> > the plugin. There will be a new output pane, which shows collected data,
> > conversions methods, if any used, and transmitted data to the user.
> 
>  --
> 
> > Tino
> > 
> > 
> > On 22/02/2018, 15.26, "Simon Hausmann"
> > > wrote:
> > 
> > 
> > Hi,
> > 
> > 
> > 
> > Can you provide a bit more information about how this plugin / frontend
> > fits into the Qt project? Where is the collected data sent to and how is
> > it accessible to the community?
> > 
> > 
> > 
> > (-1 from me, as I think this needs to be clarified)
> > 
> > 
> > 
> > Simon
> > 
> > 
> > From: Development
> > 
> > on behalf of Tuukka Turunen 
> 
>  Sent: Thursday,
> 
> > February 22, 2018 2:14:14 PM
> > To: Tino Pyssysalo; qt-crea...@qt-project.org; development@qt-project.org
> > Subject: Re: [Development] [Qt-creator] Requesting repository for
> > telemetry
> > plugin in Qt Creator
> > 
> > 
> > 
> > 
> > Hi,
> > 
> > 
> > 
> > +1 for creating the repo, but what about qt/qtanalytics as a name? This
> > item could be useful also for other applications.
> > 
> > 
> > 
> > Yours,
> > 
> >  Tuukka
> > 
> > From: Qt-creator 
> > on behalf of Tino Pyssysalo 

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Edward Welbourne]

André Pönitz (22 February 2018 20:05)
> Any number for a "measured" value for rate of crashes or memory leaks
> is uninteresting for me when I run into the problem myself reqularly.
> And trust me, I do.

I trust you.
It is, however, possible your usage patterns of the UI are not typical;
consequently, you'll prioritise the bugs you see most often; which might
not be the bugs most often encountered by other users.  Analytics may
give you the data to know the pain points everyone else is as acutely
aware of as you are of the pain points you meet most often.

> As someone who has been working on Qt Creator for more than a decade I
> *do* know about issues in the IDE by my own use of it, by the
> significant backlog of bug reports in JIRA, and by interacting with
> (sometimes referred to as "talking to") actual users.
>
> The currently 399 open issues assigned to me personally would already
> be enough to keep me busy for approximately a $WHILE, full time, not
> including time spent in review processes etc.
>
> I certainly do not need another input channel that makes me spent time
> on guessing how the information that "user A spent at time B an amount
> of C minutes working on project named D" will translate into making my
> work more efficient

The proposed system provides anonymised and presumably aggregated data;
so you won't be given, much less asked to evaluate, information about a
specific user A doing things at a specific time B; your objection is a
straw man.  You'd be getting data on what proportion of users spend what
proportions of their time doing which things.  In particular, knowing
which bugs bite most users most often might not be entirely useless when
it comes to prioritising which bug to fix first.

This won't enable you to write new features any faster or fix bugs any
faster; but it may enable you to prioritise the things that are causing
most pain to most users, and the things that would give the most win to
the most users.  *That* is what analytics is good for.  The fact that it
doesn't do a bunch of other things is beside the point, and no reason to
reject it out of hand.

Now, fortunately for you, most of the folk who use the product you work
on are in fact software developers, so may well have similar habits to
yours; so if the scope of this project is only Qt Creator, it may well
be a waste of time; and, if it's intended to be a more general tool,
this may also be a reason to *not* focus on Qt Creator as initial
test-bed, as seems to be the present plan - that's apt to skew what we
develop to be something that only works when the user-base thinks like
the developers, which is not where (honest, open, ethical) analytics is
at its best - where it reveals things to the developer that users see
all the time, but the developer never encounters.

Eddy.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Simon Hausmann]

I just had a look at KUserFeedback and I'm impressed.


Looks like a really good combination of very useful providers, UI, 
administration and server bits - all in one relatively small package. And for 
those not liking the PHP server part, it appears that that would be a piece 
that is relatively easy to replace - although the code looks very clean.


Also very cool that you're using this in production for GammaRay.


/That/ is something that would be awesome as part of the Qt project IMHO. 
Sensible scope, production tested and easy to use. (But I can totally 
understand that it might make more sense to remain in the KDE frameworks)



Simon


From: Development  on 
behalf of Volker Krause 
Sent: Friday, February 23, 2018 10:20:23 AM
To: development@qt-project.org; qt-crea...@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator

Hi,

as numerous people have asked me to comment on this by now, let me just do
that here publicly (representing KDE's KUserFeedback, not KDAB):

Tino is well aware of KUserFeedback, we discussed that last year already in
detail. So it definitely was considered as a possible solution for this.
I do not know why it was ultimately decided to implement a new framework, in
particular if that's due to conceptual or technical reasons, or licensing.


With the KDAB hat back on, we do use KUserFeedback in GammaRay since mid last
year, and it has so far provided a few useful insights, in particular
regarding to what extend we still need to support ancient Qt versions. But as
with any data, it's not the ultimate answer to all questions, and you need to
be very careful how to interpret it obviously. We have so far not received any
negative feedback with e.g. privacy concerns, but the approach KUserFeedback
takes there by default (and that we followed in GammaRay) is intentionally
very restrained.

Regards,
Volker

On Thursday, 22 February 2018 14:58:55 CET Tino Pyssysalo wrote:
> Hi,
>
> The idea is to develop a generic library/plugin, which anyone could use for
> analytics. The backend can be any storage and The Qt Company does not
> provide that.

> We plan to use the same backend, which we already use in online installers
> to collect statistics about installations. At least in case of Qt Creator,
> the plan is to make some analysis results available for the community.
> Obviously, we do not do that for our commercial tooling.

> Analytics is opt-in and disabled by default in Qt Creator. We plan to ask
> user in the installer, if the user wish to participate in Qt UX
> improvement. If the answers is no, the analytics plugin is never installed.
>  When the creator is started for the first time, it will show a dialog,
> consisting a list of collected data items and an option to enable/disable
> the plugin. There will be a new output pane, which shows collected data,
> conversions methods, if any used, and transmitted data to the user.
 --
> Tino
>
>
> On 22/02/2018, 15.26, "Simon Hausmann"
> > wrote:

>
> Hi,
>
>
>
> Can you provide a bit more information about how this plugin / frontend fits
> into the Qt project? Where is the collected data sent to and how is it
> accessible to the community?

>
>
> (-1 from me, as I think this needs to be clarified)
>
>
>
> Simon
>
> 
> From: Development 
> on behalf of Tuukka Turunen 
 Sent: Thursday,
> February 22, 2018 2:14:14 PM
> To: Tino Pyssysalo; qt-crea...@qt-project.org; development@qt-project.org
> Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry
> plugin in Qt Creator

>
>
>
> Hi,
>
>
>
> +1 for creating the repo, but what about qt/qtanalytics as a name? This item
> could be useful also for other applications.

>
>
> Yours,
>
>
>
>  Tuukka
>
>
>
> From: Qt-creator  on
> behalf of Tino Pyssysalo 
 Date: Thursday, 22
> February 2018 at 13.04
> To: "qt-crea...@qt-project.org" 
> Subject: [Qt-creator] Requesting repository for telemetry plugin in Qt
> Creator

>
>
> Description:
>
>
>
> Telemetry plugin (frontend) to collect usage data from Qt Creator to help
> improving Qt, Qt features, and Qt tools.

> Non-personal data items, such as duration the user spent in design mode,
> will be collected in a way, which is completely transparent to the user.

>
>
> Responsible: Tino Pyssysalo
>
>
>
> Repository: qt-creator/plugin-telemetry
>
>
>
>
>
> ---
>
> Tino Pyssysalo
>
> Senior Manager
>
>
>
> The Qt Company
>
> Hämeenkatu 14 C 25
>
> 33100 Tampere, Finland
>
> tino.pyssys...@qt.io
>
> +358 40 8615475
>
> http://qt.io

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Tuukka Turunen]

Hi,

Use of KUserFeedback is problematic due to its license. Adding 3rd party L/GPL 
components is something I do not want to do (already wrote "we", but let's use 
"I" instead to avoid need to define what is meant by we :) The reason for 
avoiding adding any 3rd party components with viral licenses is coming from the 
commercial licensee needs.

If KUserFeedback does what is needed from the discussed Qt add-on module, and 
the persons who wrote it are interested in contributing it to Qt, that could be 
one approach. 

That said, I have not looked into KUserFeedback myself beyond licensing.

Yours,

Tuukka 

On 23/02/2018, 11.22, "Development on behalf of Volker Krause" 
 wrote:

Hi,

as numerous people have asked me to comment on this by now, let me just do 
that here publicly (representing KDE's KUserFeedback, not KDAB):

Tino is well aware of KUserFeedback, we discussed that last year already in 
detail. So it definitely was considered as a possible solution for this.
I do not know why it was ultimately decided to implement a new framework, 
in 
particular if that's due to conceptual or technical reasons, or licensing.


With the KDAB hat back on, we do use KUserFeedback in GammaRay since mid 
last 
year, and it has so far provided a few useful insights, in particular 
regarding to what extend we still need to support ancient Qt versions. But 
as 
with any data, it's not the ultimate answer to all questions, and you need 
to 
be very careful how to interpret it obviously. We have so far not received 
any 
negative feedback with e.g. privacy concerns, but the approach 
KUserFeedback 
takes there by default (and that we followed in GammaRay) is intentionally 
very restrained.

Regards,
Volker

On Thursday, 22 February 2018 14:58:55 CET Tino Pyssysalo wrote:
> Hi,
> 
> The idea is to develop a generic library/plugin, which anyone could use 
for
> analytics. The backend can be any storage and The Qt Company does not
> provide that.
 
> We plan to use the same backend, which we already use in online installers
> to collect statistics about installations. At least in case of Qt Creator,
> the plan is to make some analysis results available for the community.
> Obviously, we do not do that for our commercial tooling.
 
> Analytics is opt-in and disabled by default in Qt Creator. We plan to ask
> user in the installer, if the user wish to participate in Qt UX
> improvement. If the answers is no, the analytics plugin is never 
installed.
>  When the creator is started for the first time, it will show a dialog,
> consisting a list of collected data items and an option to enable/disable
> the plugin. There will be a new output pane, which shows collected data,
> conversions methods, if any used, and transmitted data to the user.
 --
> Tino
> 
> 
> On 22/02/2018, 15.26, "Simon Hausmann"
> > wrote:
 
> 
> Hi,
> 
> 
> 
> Can you provide a bit more information about how this plugin / frontend 
fits
> into the Qt project? Where is the collected data sent to and how is it
> accessible to the community?
 
> 
> 
> (-1 from me, as I think this needs to be clarified)
> 
> 
> 
> Simon
> 
> 
> From: Development 

> on behalf of Tuukka Turunen 
 Sent: Thursday,
> February 22, 2018 2:14:14 PM
> To: Tino Pyssysalo; qt-crea...@qt-project.org; development@qt-project.org
> Subject: Re: [Development] [Qt-creator] Requesting repository for 
telemetry
> plugin in Qt Creator
 
> 
> 
> 
> Hi,
> 
> 
> 
> +1 for creating the repo, but what about qt/qtanalytics as a name? This 
item
> could be useful also for other applications.
 
> 
> 
> Yours,
> 
> 
> 
>  Tuukka
> 
> 
> 
> From: Qt-creator  
on
> behalf of Tino Pyssysalo 
 Date: Thursday, 22
> February 2018 at 13.04
> To: "qt-crea...@qt-project.org" 
> Subject: [Qt-creator] Requesting repository for telemetry plugin in Qt
> Creator
 
> 
> 
> Description:
> 
> 
> 
> Telemetry plugin (frontend) to collect usage data from Qt Creator to help
> improving Qt, Qt features, and Qt tools.
 
> Non-personal data items, such as duration the user spent in design mode,
> will be collected in a way, which is completely transparent to the user.
 
> 
> 
 

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Tobias Hunger]

Hi Pasi,

On Fri, Feb 23, 2018 at 10:33 AM, Pasi Keränen  wrote:

> I object to using “Spyware” term in this context. Spyware is SW that does
> things behind your back.

I noticed that my mail could be read in the way you read it pretty
much right after sending it. I need to apologize for expressing myself
so poorly!

What I meant to say that it is possible to write a spyware plugin
(following pretty much exactly what you lay out below) for creator or
any one Qt application that will collect basically everything about a
user and to feed that into a database on the internet somewhere in a
couple of weeks. On the other hand the task of writing a framework
that does anonymized data collection that follows all the relevant
data protection laws and standards and that pushes it to a server that
is easy to manage and set up is an entirely different scope. I wanted
to find out where our discussion is between these two poles.

I did not intend to imply that what we are discussing here is spyware.

> Siphons contact information, user account info etc.
> without telling you. We’re NOT talking about such use cases here! I don’t
> think anyone in The Qt Company wants to do such things. From what I hear the
> intention is to track certain things in an open, transparent manner,
> respecting the communitys clear wish to keep things in the open and for the
> benefit of our end users.

I am sorry for giving the impression that I thought anybody here is
considering spyware. That was not my intention and I want to apologize
to anybody that got that impression.



Best Regards,
Tobias
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Pasi Keränen]

Hi Tobias,

I planned to stay out of this, but
-1 since I am totally confused about the scope of this project at this point.
So are we talking about a generic telemetry framework for Qt applications or 
about watching Qt Creator users specifically?
Tino started by making the claim that this is a generic library and then kept 
listing Qt Creator specific integrations. You focus entirely onto the generic 
part, leaving out creator completely.
What exactly are we talking about here?

My understanding at this point is that this is meant to be a telemetry 
framework for Qt applications and first integration point that has been in 
discussions is Qt Creator. I intentionally left Qt Creator out as I don’t feel 
comfortable talking what they need/don’t need. So instead I concentrated on 
what I see Qt 3D Studio needs as I feel much more comfortable to talk about 
that based on our experiences, our engagements with customers and the usability 
and UI work we’ve done so far in Qt 3D Studio project.

I’m always in favor of iterative development as you very very rarely understand 
the scope and needs at the beginning. So I understand the need to have a 
“reference integration to try out” even if we talk about aiming towards generic 
telemetry plugin. And it seems quite obvious from these discussions that we 
don’t yet know ourselves a lot about how to collect data, what type of data is 
to be collected and how to process it. We seem to be a bit divided in to 
individuals thinking this is inherently bad and morally dubious. And 
individuals (like myself) who see this as great idea to be able to get more 
data on how people use our tools. Not just from big customers and people who 
come to our events. But also from people out there in universities, small 
companies, startups, the people we rarely meet in person.

Once we have understanding on what exactly are we after, then it would be good 
to move towards a generic Qt framework prototype. Maybe integrate against a 
known and trusted third party framework, add features to the API iteratively 
based on learnings and iterations. Then move on to publish this as tech preview 
and while we investigate integrating against another 3rd party framework so 
that we end up with a truly generic, Qt-like wrapper for specific functionality.

A Qt creator spyware plug-in (which does more than what we discuss here I 
hope:-) would be a matter of a couple of weeks to do, putting a generic 
framework into place with all the bits and pieces for that to be actually 
useful in a wide list of possible contexts is a very different beast.

I object to using “Spyware” term in this context. Spyware is SW that does 
things behind your back. Siphons contact information, user account info etc. 
without telling you. We’re NOT talking about such use cases here! I don’t think 
anyone in The Qt Company wants to do such things. From what I hear the 
intention is to track certain things in an open, transparent manner, respecting 
the communitys clear wish to keep things in the open and for the benefit of our 
end users.


This is great initiative and very much the way today's app and application 
industry works. UX studies performed by UX experts have been minimized and 
targeted for specific (usually new/experimental) features or upcoming new 
software (like we did with Qt 3D Studio back in last spring). And the mass 
information on "how do our users use the SW? do they find the stuff we've put 
in there? how often they hit a wall in doing sequence X? how many crashes do 
they experience when doing Y?" is collected via automated telemetry. It is 
great as it brings data from the actual user in their actual work and you can 
then use that to concentrate on functionality that really matters to your 
users. Making stuff they repeat hundred times a week easier and faster, making 
them more productive.

I see value in this approach when you can do lots of small releases fast. So 
you can do evaluate the effect of small changes by doing one change to evaluate 
per release and measure how that effects usage.
We can not do more than two releases per year in Qt. Is this approach even 
applicable to us?

Qt 3D Studio plans to do 4 releases per year, so for us this is definitely 
applicable. Qt Creator does also more than 2 releases a year so perhaps this 
could be useful for them as well, but as I said. I’m not comfortable talking on 
their behalf on this.

I want to also point out that answering any of the questions you used as an 
example require *way* more information than I am even remotely comfortable to 
collect.


This is where we definitely differ as individuals. I use software from Apple, 
Adobe etc. and I’m 100% fine giving them information on my usage statistics as 
it means the SW might get better over time for me. If e.g. Blender would some 
day ask me “are you ok for us to track your usage of the SW” I’d be 100% ok to 
do that as I see that it definitely could improve a lot from observing users. I 

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Volker Krause]

Hi,

as numerous people have asked me to comment on this by now, let me just do 
that here publicly (representing KDE's KUserFeedback, not KDAB):

Tino is well aware of KUserFeedback, we discussed that last year already in 
detail. So it definitely was considered as a possible solution for this.
I do not know why it was ultimately decided to implement a new framework, in 
particular if that's due to conceptual or technical reasons, or licensing.


With the KDAB hat back on, we do use KUserFeedback in GammaRay since mid last 
year, and it has so far provided a few useful insights, in particular 
regarding to what extend we still need to support ancient Qt versions. But as 
with any data, it's not the ultimate answer to all questions, and you need to 
be very careful how to interpret it obviously. We have so far not received any 
negative feedback with e.g. privacy concerns, but the approach KUserFeedback 
takes there by default (and that we followed in GammaRay) is intentionally 
very restrained.

Regards,
Volker

On Thursday, 22 February 2018 14:58:55 CET Tino Pyssysalo wrote:
> Hi,
> 
> The idea is to develop a generic library/plugin, which anyone could use for
> analytics. The backend can be any storage and The Qt Company does not
> provide that.
 
> We plan to use the same backend, which we already use in online installers
> to collect statistics about installations. At least in case of Qt Creator,
> the plan is to make some analysis results available for the community.
> Obviously, we do not do that for our commercial tooling.
 
> Analytics is opt-in and disabled by default in Qt Creator. We plan to ask
> user in the installer, if the user wish to participate in Qt UX
> improvement. If the answers is no, the analytics plugin is never installed.
>  When the creator is started for the first time, it will show a dialog,
> consisting a list of collected data items and an option to enable/disable
> the plugin. There will be a new output pane, which shows collected data,
> conversions methods, if any used, and transmitted data to the user.
 --
> Tino
> 
> 
> On 22/02/2018, 15.26, "Simon Hausmann"
> > wrote:
 
> 
> Hi,
> 
> 
> 
> Can you provide a bit more information about how this plugin / frontend fits
> into the Qt project? Where is the collected data sent to and how is it
> accessible to the community?
 
> 
> 
> (-1 from me, as I think this needs to be clarified)
> 
> 
> 
> Simon
> 
> 
> From: Development 
> on behalf of Tuukka Turunen 
 Sent: Thursday,
> February 22, 2018 2:14:14 PM
> To: Tino Pyssysalo; qt-crea...@qt-project.org; development@qt-project.org
> Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry
> plugin in Qt Creator
 
> 
> 
> 
> Hi,
> 
> 
> 
> +1 for creating the repo, but what about qt/qtanalytics as a name? This item
> could be useful also for other applications.
 
> 
> 
> Yours,
> 
> 
> 
>  Tuukka
> 
> 
> 
> From: Qt-creator  on
> behalf of Tino Pyssysalo 
 Date: Thursday, 22
> February 2018 at 13.04
> To: "qt-crea...@qt-project.org" 
> Subject: [Qt-creator] Requesting repository for telemetry plugin in Qt
> Creator
 
> 
> 
> Description:
> 
> 
> 
> Telemetry plugin (frontend) to collect usage data from Qt Creator to help
> improving Qt, Qt features, and Qt tools.
 
> Non-personal data items, such as duration the user spent in design mode,
> will be collected in a way, which is completely transparent to the user.
 
> 
> 
> Responsible: Tino Pyssysalo
> 
> 
> 
> Repository: qt-creator/plugin-telemetry
> 
> 
> 
> 
> 
> ---
> 
> Tino Pyssysalo
> 
> Senior Manager
> 
> 
> 
> The Qt Company
> 
> Hämeenkatu 14 C 25
> 
> 33100 Tampere, Finland
> 
> tino.pyssys...@qt.io
> 
> +358 40 8615475
> 
> http://qt.io
> 
> 
> 
> The future is Written with Qt
>

smime.p7s
Description: S/MIME cryptographic signature
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Tobias Hunger]

Hi Pasi,

On Feb 23, 2018 08:05, "Pasi Keränen"  wrote:

Hi there,

+1 for having a generic telemetry plugin in Qt.


I planned to stay out of this, but

-1 since I am totally confused about the scope of this project at this
point.

So are we talking about a generic telemetry framework for Qt applications
or about watching Qt Creator users specifically?

Tino started by making the claim that this is a generic library and then
kept listing Qt Creator specific integrations. You focus entirely onto the
generic part, leaving out creator completely.

What exactly are we talking about here?

A Qt creator spyware plug-in (which does more than what we discuss here I
hope:-) would be a matter of a couple of weeks to do, putting a generic
framework into place with all the bits and pieces for that to be actually
useful in a wide list of possible contexts is a very different beast.

This is great initiative and very much the way today's app and application
industry works. UX studies performed by UX experts have been minimized and
targeted for specific (usually new/experimental) features or upcoming new
software (like we did with Qt 3D Studio back in last spring). And the mass
information on "how do our users use the SW? do they find the stuff we've
put in there? how often they hit a wall in doing sequence X? how many
crashes do they experience when doing Y?" is collected via automated
telemetry. It is great as it brings data from the actual user in their
actual work and you can then use that to concentrate on functionality that
really matters to your users. Making stuff they repeat hundred times a week
easier and faster, making them more productive.


I see value in this approach when you can do lots of small releases fast.
So you can do evaluate the effect of small changes by doing one change to
evaluate per release and measure how that effects usage.

We can not do more than two releases per year in Qt. Is this approach even
applicable to us?

I want to also point out that answering any of the questions you used as an
example require *way* more information than I am even remotely comfortable
to collect.

I see definite need for this in Qt 3D Studio so please don’t make this just
with Qt Creator in mind. Also, in my humble opinion, in order to be
relevant in today's UI development, Qt should also offer this kind of a
plug-in to our customers. A ready-to-go plug-in that automatically ensures
the data is collected in a way that fulfills data privacy acts and respects
the privacy of the user would be great. Especially for startups and smaller
companies, but also for bigger companies wanting to switch to the modern
way of doing UI development. It is not as easy to do as one might think at
glance.


I agree that having a general framework has value to some customers.

Such a framework would need to be integrated into big solutions like Google
analytics or something similar so the users can actually evaluate the
collected data and cross-reference that to other data they collect. Just
dumping data into some server somewhere does not help anybody.

Will the server-side code be part of this project by the way?

What about evaluation of the collected data? Is that in scope for this
project, too?

I would ask anyone who has not done work with usability and user experience
people in the past to give this way of working a chance. I've worked 7
years in application development while we grew usability knowledge in the
team over that time. The first time I got to observe a real world user
working with our software in actual real world situation was eye opening.
We had gotten so many important things wrong in our idealistic thinking and
forgotten to handle certain cases that occur on the field. Also you become
blind to your own creations faults as you just know how the software works.
It's just a fact of life.


Sure. We do way too little validation of what we do against the real world
usage.

Let us do some usability studies, let us talk to users, let us do surveys,
let's evaluate all the data users provide to us on the mailing list, the
bug tracker, the forums, stack overflow and in lots of other places. We do
have a very active and supportive community of users and customers, let us
use the feedback they provide already!

Collecting some semi-random data from a self-selected group of users and
dumping that onto a server somewhere is next to useless compared to all the
other options we have already. Even in an ideal situation (which we do not
have within Qt!), metrics are not comparable to a real user study where you
actually watch users doing their thing.

This is even more true when not leaving out any information that can be
used to identify individual users from the collected data, which we
obviously will do.

Best Regards,
Tobias
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Simon Hausmann]

Hi,


Given that no plan has been presented about how this is intended to work in 
terms of backend or API scope, I stand with my -1 for a qt/ or qt-creator/ 
repo. If there exists no plan yet but the desire to experiment, then I'm with 
Pasi here and would suggest a repository in the playground scope. I think 
either analytics or telemetry make sense to have in the name. Firebase for 
example uses the term analytics in their API and Mozilla uses the term 
telemetry for the service of collecting performance and usage info for Firefox.



Simon


From: Pasi Keränen
Sent: Friday, February 23, 2018 8:53:33 AM
To: Maurice Kalinowski; Tino Pyssysalo; Simon Hausmann; Tuukka Turunen; 
qt-crea...@qt-project.org; development@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator


Hi,



Repos can be relocated to new homes if really needed, but I think it’s fair to 
say more generic location is definitely preferred from Qt 3D Studio point of 
view.



To make this even easier I’d even start with a playground repo if nothing else 
can be found. Qt has always been (despite our vocal and sometimes a bit harsh 
dialogue) inclusive, so it should be fine to go and experiment with all things 
UI related. Just to see if something is worth the effort or not.



Regards,

Pasi



From: Development  on 
behalf of Maurice Kalinowski 
Date: Friday, 23 February 2018 at 9.33
To: Tino Pyssysalo , Simon Hausmann 
, Tuukka Turunen , 
"qt-crea...@qt-project.org" , 
"development@qt-project.org" 
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator



“The idea is to develop a generic library/plugin, which anyone could use for 
analytics”



If that is the case, then qt-creator/telemetry is the wrong repository to ask 
for. If you are aiming at something generic, then it should be qt/



Maurice



Von: Qt-creator 
[mailto:qt-creator-bounces+maurice.kalinowski=qt...@qt-project.org] Im Auftrag 
von Tino Pyssysalo
Gesendet: Thursday, February 22, 2018 2:59 PM
An: Simon Hausmann ; Tuukka Turunen 
; qt-crea...@qt-project.org; development@qt-project.org
Betreff: Re: [Qt-creator] [Development] Requesting repository for telemetry 
plugin in Qt Creator



Hi,



The idea is to develop a generic library/plugin, which anyone could use for 
analytics. The backend can be any storage and The Qt Company does not provide 
that.



We plan to use the same backend, which we already use in online installers to 
collect statistics about installations. At least in case of Qt Creator, the 
plan is to make some analysis results available for the community. Obviously, 
we do not do that for our commercial tooling.



Analytics is opt-in and disabled by default in Qt Creator. We plan to ask user 
in the installer, if the user wish to participate in Qt UX improvement. If the 
answers is no, the analytics plugin is never installed.  When the creator is 
started for the first time, it will show a dialog, consisting a list of 
collected data items and an option to enable/disable the plugin. There will be 
a new output pane, which shows collected data, conversions methods, if any 
used, and transmitted data to the user.

--

Tino





On 22/02/2018, 15.26, "Simon Hausmann" 
> wrote:



Hi,



Can you provide a bit more information about how this plugin / frontend fits 
into the Qt project? Where is the collected data sent to and how is it 
accessible to the community?



(-1 from me, as I think this needs to be clarified)



Simon



From: Development 
>
 on behalf of Tuukka Turunen >
Sent: Thursday, February 22, 2018 2:14:14 PM
To: Tino Pyssysalo; 
qt-crea...@qt-project.org; 
development@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator





Hi,



+1 for creating the repo, but what about qt/qtanalytics as a name? This item 
could be useful also for other applications.



Yours,



 Tuukka



From: Qt-creator 
>
 on behalf of Tino Pyssysalo >
Date: Thursday, 22 February 2018 at 13.04
To: "qt-crea...@qt-project.org" 
>
Subject: