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 voc
“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.k
Hi there,
+1 for having a generic telemetry plugin in Qt.
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 (li
On Thu, Feb 22, 2018 at 01:58:55PM +, Tino Pyssysalo wrote:
> Hi,
>
> The idea is to develop a generic library/plugin, which anyone could use for
> analytics.
I see no reason why this can't be done as part of e.g. the commercial Qt
offering, with customers being free to deploy that if they fe
Another point: if you do collect usage data, please bear in mind that
sometimes a feature can be used very rarely, but still be vital. In other
words, do not consider a feature as "unnecessary" or "can be deprecated" if
it is not used often.
For example, I mostly do mobile and desktop apps, but I
On Thu, Feb 22, 2018 at 04:42:55PM +0300, Konstantin Tokarev wrote:
> 22.02.2018, 16:39, "Ryein Goddard" :
> > This might be nice to make pretty charts to show to managers, but to be
> > completely honest I think it is 100% useless.
I fully subscribe to that.
> > If you don't know what people
>
Hi Andy,
yes, non-Qt Company people have a voice. This discussion here is taking
place in the Qt Project, not just the Qt Company.
Cheers,
Robert
Am 22.02.2018 um 14:39 schrieb Andy:
If non-Qt Company people have a voice, I'm with Simon. More info is needed.
Do you see this shipping as a b
Hi,
Thanks for the update, this is starting to make more sense to me.
So do I understand correctly that you'd like to have one API that you could use
from a proprietary Qt Creator plugin (for commercial tooling) as well as from
the installer framework, and the repository that you're requestin
It would be nice if you can explain what data you want to collect and how it
will be help the creator development. In my view it is quite hard to collect
data about not implemented features, so you could only provide information
about what feature is used. So the data could be used to see what s
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
Hi,
For the charts it's indeed not so relevant what kind of charts we can
visualize. That is an implementation detail indeed. But whether visualization
data in charts is relevant to the users of Qt and whether we would like to make
this part of the Qt project is certainly a question we'd clari
On Thu, Feb 22, 2018 at 8:47 AM, Tuukka Turunen
wrote:
>
>
> Hi Simon,
>
>
>
> Is that an item to decide at repo creation time or something to address
> later during implementation / code review? For example consider requesting
> a repo for qt/qtcharts – should we have known what data users want
> Well, there are things that are hard to report via survey, e.g. rate of
> crashes or memory leaking in clangbackend
We have a crash handler in the works, which is much more useful than this. And
memory leaks can simply be investigated simply by debugging. I don't see how
this plugin could he
Hi Simon,
Is that an item to decide at repo creation time or something to address later
during implementation / code review? For example consider requesting a repo for
qt/qtcharts – should we have known what data users want to visualize with it
before having a repository (or only during the im
I think memory leaks and different backends should be tested by Qt.
Customers/Users are not your beta testers.
On 02/22/2018 08:42 AM, Konstantin Tokarev wrote:
22.02.2018, 16:39, "Ryein Goddard" :
This might be nice to make pretty charts to show to managers, but to be
completely honest I th
22.02.2018, 16:39, "Ryein Goddard" :
> This might be nice to make pretty charts to show to managers, but to be
> completely honest I think it is 100% useless. If you don't know what people
> are using your software for, or how then you aren't communicating with them.
> You know once upon a t
If non-Qt Company people have a voice, I'm with Simon. More info is needed.
Do you see this shipping as a built-in plugin for Qt Creator?
If so, would this data collection be opt-in?
How is the user informed about exactly what is being collected and how the
data is used?
---
Andy Maloney // h
This might be nice to make pretty charts to show to managers, but to be
completely honest I think it is 100% useless. If you don't know what
people are using your software for, or how then you aren't communicating
with them. You know once upon a time companies just talked with people
to figur
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
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-creator@qt-project.org"
S
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: Tin
Hello,
The beta version of Qt Creator 4.6 has been released
(https://blog.qt.io/blog/2018/02/07/qt-creator-4-6-beta-released/) and we are
approaching the release candidate (https://wiki.qt.io/Qt_Creator_Releases).
I've documented the changes I am aware of, but I need your help to make sure
tha
22 matches
Mail list logo
