- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] spotter usage - a rough analysis of categories

by Esteban Lorenzano

Ah, and I forget one very important: the menu! I almost do not use the older menu anymore :) Esteban > On 10 Jun 2016, at 08:54, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > I need to enable data collect ;) > > in my case, Iâm a happy Spotter userâ¦ I even have a plugin I made for my own that fits my way of work with repositoriesâ¦ anyway, I wanted to point: > > - I use a lot Classes/Methods/Packages... and catalog > - never used Senders/References/Pragmas because I do not find them easily (then is easier to search the class, then hit references) > - some categories seems confusing > - some other are not âfor extensive useâ but they are very useful: files, monticello package, playground > - this is more for the playground: I never understood why we need a difference between cached pages and named ones (a cached can just be named cached-1â¦ etc) > > I would be even happier is Yuriy extends his GitHub baseline plugin to scan subdirectories (most github projects keep mc data into a subdirectory) :) > > cheers! > Esteban > >> On 10 Jun 2016, at 08:42, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: >> >> Hi Doru, >> >> I just want to point out that history may possibly be a bit of a false positive. When I open spotter, type and hit enter quickly I sometimes hit an entry from history that I didnât intend to (one annoying example of this is ProcessBrowser which I regularly hit accidentally when searching for Process). >> >> Cheers, >> Max >> >> >>> On 10 Jun 2016, at 00:56, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>> >>> Hi, >>> >>> Juraj, Andrei and I did a rough analysis collected from 94 computers over the past 7 months. Of these, only 42 recorded more than 9 sessions so we only focused on these. It can be because the rest switched off the data collection in the meantime. We also excluded the computers of the GT team members. >>> >>> Of these 34 used the dive-in feature. That is, these users used at least one contextual search. >>> >>> We looked at the event of acting on an element (pressing Enter), and we collected the parent category. Acting on an item indicates that intent of search. There are 35 categories used in total, with 8 being used by 10 people (25% of the studied population) or more. Below you can see also the amount of computers using it: >>> >>> <spotter-categories-distribution.png> >>> >>> 'Classes'->40 >>> 'Implementors'->38 >>> 'History'->34 >>> 'Menu'->24 >>> 'Packages'->23 >>> 'Messages'->19 >>> 'Catalog Projects'->12 >>> 'Instance methods'->10 >>> 'Senders'->9 >>> 'Pragmas'->6 >>> 'References'->5 >>> 'Playground named pages'->5 >>> 'Playground cached pages'->4 >>> 'Help topics'->4 >>> 'Examples'->3 >>> 'Super instance methods'->3 >>> 'Selectors'->3 >>> 'ws.stfx.eu <http://ws.stfx.eu/>'->2 >>> 'GitHub Baselines'->2 >>> 'Dirty Monticello packages'->2 >>> 'Class methods'->2 >>> 'Global variables'->1 >>> 'All subclasses'->1 >>> 'Example Subjects'->1 >>> 'Files'->1 >>> 'Monticello Repositories'->1 >>> 'Metacello Configurations'->1 >>> 'Class instance variables'->1 >>> 'Items'->1 >>> 'Tags'->1 >>> 'Help contents'->1 >>> 'Monticello Package'->1 >>> 'Instance variables'->1 >>> 'Productions'->1 >>> 'Methods'->1 >>> >>> Also, in this analysis, some of the categories appear also at deeper levels (Senders, Implementors, References, Instance methods). >>> >>> As expected, Classes and Implementors are on top. Yet, the third is History, and it is also interesting to see that there is a high usage of a search through the World menu elements, but also of the Packages. >>> >>> We also note that there is quite a long tail, and this seems to confirm the hypothesis that different people have different needs and that these differences should be supported by the IDE. >>> >>> This analysis was carried out using the code that Juraj and Andrei put together for analyzing the data from the event recorder. >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> www.feenk.com <http://www.feenk.com/> >>> >>> "Value is always contextual." >>> >>> >>> >>> >> >

June 10, 2016

Re: [Pharo-dev] spotter usage - a rough analysis of categories

by Esteban Lorenzano

I need to enable data collect ;) in my case, Iâm a happy Spotter userâ¦ I even have a plugin I made for my own that fits my way of work with repositoriesâ¦ anyway, I wanted to point: - I use a lot Classes/Methods/Packages... and catalog - never used Senders/References/Pragmas because I do not find them easily (then is easier to search the class, then hit references) - some categories seems confusing - some other are not âfor extensive useâ but they are very useful: files, monticello package, playground - this is more for the playground: I never understood why we need a difference between cached pages and named ones (a cached can just be named cached-1â¦ etc) I would be even happier is Yuriy extends his GitHub baseline plugin to scan subdirectories (most github projects keep mc data into a subdirectory) :) cheers! Esteban > On 10 Jun 2016, at 08:42, Max Leske <maxleske(a)gmail.com> wrote: > > Hi Doru, > > I just want to point out that history may possibly be a bit of a false positive. When I open spotter, type and hit enter quickly I sometimes hit an entry from history that I didnât intend to (one annoying example of this is ProcessBrowser which I regularly hit accidentally when searching for Process). > > Cheers, > Max > > >> On 10 Jun 2016, at 00:56, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> Juraj, Andrei and I did a rough analysis collected from 94 computers over the past 7 months. Of these, only 42 recorded more than 9 sessions so we only focused on these. It can be because the rest switched off the data collection in the meantime. We also excluded the computers of the GT team members. >> >> Of these 34 used the dive-in feature. That is, these users used at least one contextual search. >> >> We looked at the event of acting on an element (pressing Enter), and we collected the parent category. Acting on an item indicates that intent of search. There are 35 categories used in total, with 8 being used by 10 people (25% of the studied population) or more. Below you can see also the amount of computers using it: >> >> <spotter-categories-distribution.png> >> >> 'Classes'->40 >> 'Implementors'->38 >> 'History'->34 >> 'Menu'->24 >> 'Packages'->23 >> 'Messages'->19 >> 'Catalog Projects'->12 >> 'Instance methods'->10 >> 'Senders'->9 >> 'Pragmas'->6 >> 'References'->5 >> 'Playground named pages'->5 >> 'Playground cached pages'->4 >> 'Help topics'->4 >> 'Examples'->3 >> 'Super instance methods'->3 >> 'Selectors'->3 >> 'ws.stfx.eu <http://ws.stfx.eu/>'->2 >> 'GitHub Baselines'->2 >> 'Dirty Monticello packages'->2 >> 'Class methods'->2 >> 'Global variables'->1 >> 'All subclasses'->1 >> 'Example Subjects'->1 >> 'Files'->1 >> 'Monticello Repositories'->1 >> 'Metacello Configurations'->1 >> 'Class instance variables'->1 >> 'Items'->1 >> 'Tags'->1 >> 'Help contents'->1 >> 'Monticello Package'->1 >> 'Instance variables'->1 >> 'Productions'->1 >> 'Methods'->1 >> >> Also, in this analysis, some of the categories appear also at deeper levels (Senders, Implementors, References, Instance methods). >> >> As expected, Classes and Implementors are on top. Yet, the third is History, and it is also interesting to see that there is a high usage of a search through the World menu elements, but also of the Packages. >> >> We also note that there is quite a long tail, and this seems to confirm the hypothesis that different people have different needs and that these differences should be supported by the IDE. >> >> This analysis was carried out using the code that Juraj and Andrei put together for analyzing the data from the event recorder. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> www.feenk.com <http://www.feenk.com/> >> >> "Value is always contextual." >> >> >> >> >

June 10, 2016

Re: [Pharo-dev] Playground and text evaluation printing result default.

by stepharo

>>> Hi Stef, >>> >>> Thanks for the feedback. Sorry for the long email, but I you raised several issues and I thought it is worth addressing them. >>> >>> The feature we are talking about came into being after several suggestions on this mailing list (and quite some long discussions) that had the scenario of keeping track of several executions. In the first version of the Playground it was not possible to paste directly in the playground. We did not impose anything, it was the contrary. >> and the result is that I can spend time removing spurrious comments. >>> From your email I see that you would rather prefer the variant of embedding the text as is after pressing Enter. Is this correct? >>> >>> Here is another variant: >>> - Cmd+p >>> - Cmd+v ==> paste the string directly in the editor without comments >> why not. >> but this is confusing with copy paste. >> So will you corrupt the current selection. > Hmm. I do not see this one, so I need a bit more explanations. Here is what I understand: > - in the old editor, the behavior was that when you pressed Cmd+p, the printed text got selected > - in my proposal, you press Cmd+p,Cmd+v and you get exactly the same text selected. We should stop to have this emacs plague. And I can have something in my paste buffer and printing should not remove it. 'KJHJKKJ' cmd C cmd v -> 'KJHJKKJ' 1+3 cmd p should not destroy nor paste 'KJHJKKJ' > Did I misunderstand something? > > One note: Cmd+v would not imply copying to the clipboard. > > >> So should I trade copy/paste with getting a value printed. >> May be cmd+r for raw > This is tempting. How about Cmd+Shift+p (force print-it)? Please consider that shift does not exist. It forces thumb to do a bad gymnastic and for me it simply ***hurt*** physically so I never use bindings in Spotter with shift since I want to make sure that I can continue to type on a keyboard. > > This brings us to the cmd+shift issue. I wanted to ask for a longer time how do you press Cmd+Shift+n for references? Is there a difference in how you use the keyboard in that case? Please note that I am not mocking you. I want to know. left thumb (finder 1) on cmd left finger 4 on shift and right finger 2 This position does not hurt but is not confortable because lock upper case is just above. >>> ... >>> This discussion is one of those. We wanted to solve the most often appearing case in which we use Cmd+p as a way to preview quickly the result. Pasting the code in the existing playground is an edge case for Cmd+p, not the primary case. >> how did you measure it? >> Because for me this is always the inverse. > I watched people deleting the printed code so many times, including me that this became frustrating enough to trigger a new solution. Then when we released the playground 2 years ago, people liked it and they only announced the need for a way to keep track of execution results. I know. Now remember the dancing bear and the woman that was asked to try a new keyboard and that was sad that she could not adapt. >>>> ... >>> Letâs do a remote session and I watch you do things. This week I am available this Thursday morning or Friday after 11. >> I'm not available. Going to hard rock concert with teenagers. > Have fun :). How about next week on Monday? I could around 16h > > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing has its own flow." > > > > > > >

June 10, 2016

Re: [Pharo-dev] System Browser UX analysis - double key shortcuts

by Esteban Lorenzano

wellâ¦ supposedly a revamp of the shorcuts mechanism will happen sometime during 6.0 development (if I find the time to work on it, or someone jumps in, of course :P) the idea with this is to centralise actions (using command pattern) and then users just declare what they will be usingâ¦ then *all tools* in system with same shortcuts will share actions. external packages should also have the possibility of install their actionsâ¦ this can create collisions, but wellâ¦ (btw, same âuser install/declareâ idea should be taken for icons and others, as a way to avoid the stupid coupling of packages we have now) Esteban > On 10 Jun 2016, at 08:34, stepharo <stepharo(a)free.fr> wrote: > > Hi ben > > I never liked the double keys, but when they got introduced by camillo and ben the goal was to be able to fully > > navigate wihout having to touch the mouse. So from this goal point of view it was a nice attempt. > > Now we should be able > > to let user decide > > to have the same double keys in the other pane to avoid to create a mode. > > Stef > > Le 10/6/16 Ã 03:33, Ben Coman a Ã©crit : >> I happened to be back using a Squeak image to run the VM simulator and >> wanted to report my experience that it was a *joy* to again be able to >> use <ctrl-x> to delete methods from the System Browser. Over the past >>> 12 months rather than complain about the double-key shortcuts, I've >> given myself time to adapt - but in practice I've adapted by always >> using the context menu rather than the double key shortcut. I don't >> understand the advantage of the double-key shortcuts here and why the >> same <ctrl-x> shortcut can't work in each of the four System Browser >> panes, since the "context" is provided by which pane is selected. >> >> I do recognise the value of double-keys for global shortcuts, since >> you need the first to select the tool to provide context for the >> second key. >> >> It would be nice to get some UX stastics for the System Browser about >> the predominance of shortcut versus menu usage for different people. >> >> cheers -ben >> >> > >

June 10, 2016

Re: [Pharo-dev] spotter usage - a rough analysis of categories

by Max Leske

Hi Doru, I just want to point out that history may possibly be a bit of a false positive. When I open spotter, type and hit enter quickly I sometimes hit an entry from history that I didnât intend to (one annoying example of this is ProcessBrowser which I regularly hit accidentally when searching for Process). Cheers, Max > On 10 Jun 2016, at 00:56, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Juraj, Andrei and I did a rough analysis collected from 94 computers over the past 7 months. Of these, only 42 recorded more than 9 sessions so we only focused on these. It can be because the rest switched off the data collection in the meantime. We also excluded the computers of the GT team members. > > Of these 34 used the dive-in feature. That is, these users used at least one contextual search. > > We looked at the event of acting on an element (pressing Enter), and we collected the parent category. Acting on an item indicates that intent of search. There are 35 categories used in total, with 8 being used by 10 people (25% of the studied population) or more. Below you can see also the amount of computers using it: > > <spotter-categories-distribution.png> > > 'Classes'->40 > 'Implementors'->38 > 'History'->34 > 'Menu'->24 > 'Packages'->23 > 'Messages'->19 > 'Catalog Projects'->12 > 'Instance methods'->10 > 'Senders'->9 > 'Pragmas'->6 > 'References'->5 > 'Playground named pages'->5 > 'Playground cached pages'->4 > 'Help topics'->4 > 'Examples'->3 > 'Super instance methods'->3 > 'Selectors'->3 > 'ws.stfx.eu <http://ws.stfx.eu/>'->2 > 'GitHub Baselines'->2 > 'Dirty Monticello packages'->2 > 'Class methods'->2 > 'Global variables'->1 > 'All subclasses'->1 > 'Example Subjects'->1 > 'Files'->1 > 'Monticello Repositories'->1 > 'Metacello Configurations'->1 > 'Class instance variables'->1 > 'Items'->1 > 'Tags'->1 > 'Help contents'->1 > 'Monticello Package'->1 > 'Instance variables'->1 > 'Productions'->1 > 'Methods'->1 > > Also, in this analysis, some of the categories appear also at deeper levels (Senders, Implementors, References, Instance methods). > > As expected, Classes and Implementors are on top. Yet, the third is History, and it is also interesting to see that there is a high usage of a search through the World menu elements, but also of the Packages. > > We also note that there is quite a long tail, and this seems to confirm the hypothesis that different people have different needs and that these differences should be supported by the IDE. > > This analysis was carried out using the code that Juraj and Andrei put together for analyzing the data from the event recorder. > > Cheers, > Doru > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > www.feenk.com > > "Value is always contextual." > > > >

June 10, 2016

Re: [Pharo-dev] Privacy sendDiagnosticsAndUsageData should be ternary, not binary

by stepharo

Andrei for the shortcut reporter we put a number of show. Like that the user will be reminder a number > > of times and the system will get calm. May be you could do the same > > > In a new image the message to send usage data is shown only once. > Indeed we could add a counter but that would have to maintain state > between images. I would not. Incremental thinking. >> >> So the proper behavior (imho) should be: >> >> ask Privacy for the settingâ¦ if the setting is not defined, >> then show a popup. >> If the setting is defined then respect it and do not show >> another popup. >> >> >> The current behaviour with showing the notification in Spotter >> and Nautilus should be a temporary one. >> Ideally we just need a single uniform way of showing this >> notification plus the option to control >> and see the data that each tool wants to record at a >> fined-grained level. >> >> >> Also it would be nice to know what happens with the data. >> >> >> We store it on a server and use it for various analyses. > what can you tell us on processor use in Spotter. > > > Not right at this moment. I'm way to busy with other urgent things. > Some older results were discussed here: > http://scg.unibe.ch/scgbib?query=Kube15a&display=abstract > Just for these result to carry more value we still need more people to > send data. > Right now few do. > > Cheers, > Andrei > > >> It is also publicly available: GTEventTool default download. >> >> I mean my projects are open source so "sendSourceCode" >> shouldn't be an issueâ¦ but what you can possibly learn from it? >> Why not just analyze the content of SmalltalkHub/GitHub? >> >> >> Because if you have the setting enabled it does not always work >> to map different actions that with the code that you are working on. >> >> Cheers, >> Andrei >> >> >> Peter >> >> > >

June 10, 2016

Re: [Pharo-dev] System Browser UX analysis - double key shortcuts

by stepharo

Hi ben I never liked the double keys, but when they got introduced by camillo and ben the goal was to be able to fully navigate wihout having to touch the mouse. So from this goal point of view it was a nice attempt. Now we should be able to let user decide to have the same double keys in the other pane to avoid to create a mode. Stef Le 10/6/16 Ã 03:33, Ben Coman a Ã©crit : > I happened to be back using a Squeak image to run the VM simulator and > wanted to report my experience that it was a *joy* to again be able to > use <ctrl-x> to delete methods from the System Browser. Over the past >> 12 months rather than complain about the double-key shortcuts, I've > given myself time to adapt - but in practice I've adapted by always > using the context menu rather than the double key shortcut. I don't > understand the advantage of the double-key shortcuts here and why the > same <ctrl-x> shortcut can't work in each of the four System Browser > panes, since the "context" is provided by which pane is selected. > > I do recognise the value of double-keys for global shortcuts, since > you need the first to select the tool to provide context for the > second key. > > It would be nice to get some UX stastics for the System Browser about > the predominance of shortcut versus menu usage for different people. > > cheers -ben > >

June 10, 2016

System Browser UX analysis - double key shortcuts

by Ben Coman

I happened to be back using a Squeak image to run the VM simulator and wanted to report my experience that it was a *joy* to again be able to use <ctrl-x> to delete methods from the System Browser. Over the past >12 months rather than complain about the double-key shortcuts, I've given myself time to adapt - but in practice I've adapted by always using the context menu rather than the double key shortcut. I don't understand the advantage of the double-key shortcuts here and why the same <ctrl-x> shortcut can't work in each of the four System Browser panes, since the "context" is provided by which pane is selected. I do recognise the value of double-keys for global shortcuts, since you need the first to select the tool to provide context for the second key. It would be nice to get some UX stastics for the System Browser about the predominance of shortcut versus menu usage for different people. cheers -ben

June 10, 2016

Re: [Pharo-dev] spotter usage - a rough analysis of categories

by Alexandre Bergel

Impressive analysis! This is worth to discuss these findings in an academic venue. Alexandre > On Jun 9, 2016, at 6:56 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Juraj, Andrei and I did a rough analysis collected from 94 computers over the past 7 months. Of these, only 42 recorded more than 9 sessions so we only focused on these. It can be because the rest switched off the data collection in the meantime. We also excluded the computers of the GT team members. > > Of these 34 used the dive-in feature. That is, these users used at least one contextual search. > > We looked at the event of acting on an element (pressing Enter), and we collected the parent category. Acting on an item indicates that intent of search. There are 35 categories used in total, with 8 being used by 10 people (25% of the studied population) or more. Below you can see also the amount of computers using it: > > <spotter-categories-distribution.png> > > 'Classes'->40 > 'Implementors'->38 > 'History'->34 > 'Menu'->24 > 'Packages'->23 > 'Messages'->19 > 'Catalog Projects'->12 > 'Instance methods'->10 > 'Senders'->9 > 'Pragmas'->6 > 'References'->5 > 'Playground named pages'->5 > 'Playground cached pages'->4 > 'Help topics'->4 > 'Examples'->3 > 'Super instance methods'->3 > 'Selectors'->3 > 'ws.stfx.eu'->2 > 'GitHub Baselines'->2 > 'Dirty Monticello packages'->2 > 'Class methods'->2 > 'Global variables'->1 > 'All subclasses'->1 > 'Example Subjects'->1 > 'Files'->1 > 'Monticello Repositories'->1 > 'Metacello Configurations'->1 > 'Class instance variables'->1 > 'Items'->1 > 'Tags'->1 > 'Help contents'->1 > 'Monticello Package'->1 > 'Instance variables'->1 > 'Productions'->1 > 'Methods'->1 > > Also, in this analysis, some of the categories appear also at deeper levels (Senders, Implementors, References, Instance methods). > > As expected, Classes and Implementors are on top. Yet, the third is History, and it is also interesting to see that there is a high usage of a search through the World menu elements, but also of the Packages. > > We also note that there is quite a long tail, and this seems to confirm the hypothesis that different people have different needs and that these differences should be supported by the IDE. > > This analysis was carried out using the code that Juraj and Andrei put together for analyzing the data from the event recorder. > > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "Value is always contextual." > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 9, 2016

spotter usage - a rough analysis of categories

by Tudor Girba

Hi, Juraj, Andrei and I did a rough analysis collected from 94 computers over the past 7 months. Of these, only 42 recorded more than 9 sessions so we only focused on these. It can be because the rest switched off the data collection in the meantime. We also excluded the computers of the GT team members. Of these 34 used the dive-in feature. That is, these users used at least one contextual search. We looked at the event of acting on an element (pressing Enter), and we collected the parent category. Acting on an item indicates that intent of search. There are 35 categories used in total, with 8 being used by 10 people (25% of the studied population) or more. Below you can see also the amount of computers using it: 'Classes'->40 'Implementors'->38 'History'->34 'Menu'->24 'Packages'->23 'Messages'->19 'Catalog Projects'->12 'Instance methods'->10 'Senders'->9 'Pragmas'->6 'References'->5 'Playground named pages'->5 'Playground cached pages'->4 'Help topics'->4 'Examples'->3 'Super instance methods'->3 'Selectors'->3 'ws.stfx.eu'->2 'GitHub Baselines'->2 'Dirty Monticello packages'->2 'Class methods'->2 'Global variables'->1 'All subclasses'->1 'Example Subjects'->1 'Files'->1 'Monticello Repositories'->1 'Metacello Configurations'->1 'Class instance variables'->1 'Items'->1 'Tags'->1 'Help contents'->1 'Monticello Package'->1 'Instance variables'->1 'Productions'->1 'Methods'->1 Also, in this analysis, some of the categories appear also at deeper levels (Senders, Implementors, References, Instance methods). As expected, Classes and Implementors are on top. Yet, the third is History, and it is also interesting to see that there is a high usage of a search through the World menu elements, but also of the Packages. We also note that there is quite a long tail, and this seems to confirm the hypothesis that different people have different needs and that these differences should be supported by the IDE. This analysis was carried out using the code that Juraj and Andrei put together for analyzing the data from the event recorder. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Value is always contextual."

June 9, 2016