Recording user actions in GTools
Hi, In order to better understand how people use the GT tools we would like to integrate, before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data. The recording of data will be opt-out: *you have to explicitly agree with sending usage data*. The first time you open a GT tool, that tool will embed a small UI asking you if you want to enable data submission. We will save the setting in the your preference directory so it will be shared between all your local images. You can change this setting at any time from the Settings Browser. For now we will only like to collect data about Spotter. *By default we will only collect anonymous data *about various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc) without collecting any data what about what query you enter or what search results you get. We would also add an optional setting for sending the query text and selected elements. We will send then the data periodically to our server and when you close the image. The data that will be send is rather small: 1000 actions require 7kb of data. Thus sending an entire day worth of recordings, if all you did that day was searching, should be around 1MB of data. The recording does not influence the performance of Spotter. Spotter already generates all events of interest as announcements. To enable recording we just register a subscriber with the Spotter announcer and store the events of interest. We would like to get your opinion on this. Cheers, GT team
Absolutely no problem for me. By the way, I even have no problem to divulge my identity if this help. Cheers, Alexandre
On Feb 26, 2015, at 12:10 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
Hi,
In order to better understand how people use the GT tools we would like to integrate, before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data.
The recording of data will be opt-out: you have to explicitly agree with sending usage data. The first time you open a GT tool, that tool will embed a small UI asking you if you want to enable data submission. We will save the setting in the your preference directory so it will be shared between all your local images. You can change this setting at any time from the Settings Browser.
For now we will only like to collect data about Spotter. By default we will only collect anonymous data about various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc) without collecting any data what about what query you enter or what search results you get. We would also add an optional setting for sending the query text and selected elements.
We will send then the data periodically to our server and when you close the image.
The data that will be send is rather small: 1000 actions require 7kb of data. Thus sending an entire day worth of recordings, if all you did that day was searching, should be around 1MB of data.
The recording does not influence the performance of Spotter. Spotter already generates all events of interest as announcements. To enable recording we just register a subscriber with the Spotter announcer and store the events of interest.
We would like to get your opinion on this.
Cheers, GT team
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On 26/02/15 16:10, Andrei Chis wrote:
The recording of data will be opt-out: *you have to explicitly agree with sending usage data*.
Uhhm. That's called opt-in. A practical issue: I have projects/images where it is absolutely no problem, and projects where I definitely don't want it. All local images is not a good setting. For certain directories would work. Stephan
On Thu, Feb 26, 2015 at 8:39 PM, Stephan Eggermont <stephan@stack.nl> wrote:
On 26/02/15 16:10, Andrei Chis wrote:
The recording of data will be opt-out: *you have to explicitly agree with sending usage data*.
Uhhm. That's called opt-in.
Yes, I confused them.
A practical issue: I have projects/images where it is absolutely no problem, and projects where I definitely don't want it. All local images is not a good setting. For certain directories would work.
You will be able to change this settings in each individual image. You will further have a default setting that will be persisted to your preference folder that will apply to all new images. We need this so we do not ask every time you open a new image. Does this address your situation? Would you not want to send data from some images because of privacy issues? By default we only collect data that does not contain class names, method names or any code snippet. The only concrete information consists in category names: "Methods", "Classes", "History", etc. Cheers, Andrei
Stephan
What I often really want to do is to scope my search. find who is sending changed: in that class X. and I know that we can do it but no idea how. Stef Le 27/2/15 15:44, Andrei Chis a écrit :
On Thu, Feb 26, 2015 at 8:39 PM, Stephan Eggermont <stephan@stack.nl <mailto:stephan@stack.nl>> wrote:
On 26/02/15 16:10, Andrei Chis wrote:
The recording of data will be opt-out: *you have to explicitly agree with sending usage data*.
Uhhm. That's called opt-in.
Yes, I confused them.
A practical issue: I have projects/images where it is absolutely no problem, and projects where I definitely don't want it. All local images is not a good setting. For certain directories would work.
You will be able to change this settings in each individual image. You will further have a default setting that will be persisted to your preference folder that will apply to all new images. We need this so we do not ask every time you open a new image.
Does this address your situation?
Would you not want to send data from some images because of privacy issues? By default we only collect data that does not contain class names, method names or any code snippet. The only concrete information consists in category names: "Methods", "Classes", "History", etc.
Cheers, Andrei
Stephan
Hi Stef, In the latest version that is ready for integration, diving into a category is a visible button. Also, each button has a tooltip that shows the keybinding as well to enable learnability. Cheers, Doru On Fri, Feb 27, 2015 at 3:59 PM, stepharo <stepharo@free.fr> wrote:
What I often really want to do is to scope my search. find who is sending changed: in that class X. and I know that we can do it but no idea how.
Stef
Le 27/2/15 15:44, Andrei Chis a écrit :
On Thu, Feb 26, 2015 at 8:39 PM, Stephan Eggermont <stephan@stack.nl> wrote:
On 26/02/15 16:10, Andrei Chis wrote:
The recording of data will be opt-out: *you have to explicitly agree with sending usage data*.
Uhhm. That's called opt-in.
Yes, I confused them.
A practical issue: I have projects/images where it is absolutely no problem, and projects where I definitely don't want it. All local images is not a good setting. For certain directories would work.
You will be able to change this settings in each individual image. You will further have a default setting that will be persisted to your preference folder that will apply to all new images. We need this so we do not ask every time you open a new image.
Does this address your situation?
Would you not want to send data from some images because of privacy issues? By default we only collect data that does not contain class names, method names or any code snippet. The only concrete information consists in category names: "Methods", "Classes", "History", etc.
Cheers, Andrei
Stephan
-- www.tudorgirba.com "Every thing has its own flow"
before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data.
various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc)
If there are no tooltips what shortcuts to use people cannot dive-in and there is nothing to record :)... so please please :) But I certainly don't mind. Peter
26. 2. 2015 v 19:04, Peter Uhnák <i.uhnak@gmail.com>:
before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data.
various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc) If there are no tooltips what shortcuts to use people cannot dive-in and there is nothing to record :)... so please please :)
There are already tooltips, but likely in a version which is about to be released for Pharo 4: You can try Moose 5.1 for now. Cheers, Juraj
+ 1 If you need the proof that people do not remember the bindings why not logging. But to me this is obvious. THere is not way of discovering them expect by try and error. I always have the feeling that I use it the wrong way because I do not know the magic shortcuts. Frustrated. Le 26/2/15 23:04, Peter Uhnák a écrit :
before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data.
various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc)
If there are no tooltips what shortcuts to use people cannot dive-in and there is nothing to record :)... so please please :) But I certainly don't mind.
Peter
no objection from me, whatever help you guys improve the tools, helps me ;) On Thu, Feb 26, 2015 at 5:10 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
Hi,
In order to better understand how people use the GT tools we would like to integrate, before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data.
The recording of data will be opt-out: *you have to explicitly agree with sending usage data*. The first time you open a GT tool, that tool will embed a small UI asking you if you want to enable data submission. We will save the setting in the your preference directory so it will be shared between all your local images. You can change this setting at any time from the Settings Browser.
For now we will only like to collect data about Spotter. *By default we will only collect anonymous data *about various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc) without collecting any data what about what query you enter or what search results you get. We would also add an optional setting for sending the query text and selected elements.
We will send then the data periodically to our server and when you close the image.
The data that will be send is rather small: 1000 actions require 7kb of data. Thus sending an entire day worth of recordings, if all you did that day was searching, should be around 1MB of data.
The recording does not influence the performance of Spotter. Spotter already generates all events of interest as announcements. To enable recording we just register a subscriber with the Spotter announcer and store the events of interest.
We would like to get your opinion on this.
Cheers, GT team
participants (8)
-
Alexandre Bergel -
Andrei Chis -
Juraj Kubelka -
kilon alios -
Peter Uhnák -
Stephan Eggermont -
stepharo -
Tudor Girba