- Pharo-dev - lists.pharo.org

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

by Thierry Goubier

2016-06-10 10:11 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 10 Jun 2016, at 09:47, Guille Polito <guillermopolito(a)gmail.com> > wrote: > > > > I use spotter a lot as well. > > Me too ! > > > It is actually my default entry point to the system. It superseeded the > searches in Nautilus, and most of the searches that I used to start in the > workspace. > > Indeed, same here. > > > The things I look most by name are tools (Menu entries), classes and > packages. > > > > History is of great help and I use it a lot. But it poses a problem > sometimes because it alters the order of the results, and you have to wait > for the complete search to finish. If you do not do that, it happens what > Max explained: you type, hit <down>,<enter> and suddenly the UI refreshed > and you finished doing something else. > > > > Also, regarding the ordering of results, sometimes It bothers me that > they are sorted by category and not by relevance of the item. I'll explain > myself with a concrete case: > > - open spotter > > - type "Process" > > > > you get first two #menu items and then the #classes, containing the > class Process. I would have expected here to show first the element that > matched the most or with more relevance, regardless it's category. > > > > Question: Does spotter adapt to it's usage? Besides history, does it > learn what are the items with more relevance from previous usages in the > same session? > > Some simple learning would be super cool. > > > Also, from the top of my head there is at least one use case that I > cannot yet replace with spotter, and I have to use a normal > workspace/playground to do it => browse senders or implementors. While i > use senders/implementors search in spotter, sometimes I want to *browse* > them to be able to look at them, and interact with the code. However, from > spotter I can only observe results but not edit them. > > Yes, that is indeed something that I miss as well: browsing them all. > I don't use Spotter much, because I do that often: code in the result of a search for senders / implementors. Another thing that doesn't work too well with Spotter: I like to restrict the scope to a single package / group of package, either before the search, or after (making it easy to turn off large subsets of the search results). Thierry > > Sven > > > Guille > > > > -------- Original Message -------- > >> and just another thing :) > >> > >> I think search patterns are a bit naive now (just matching begin of > line). We could benefit from regex searchs and/or that search stuff made by > Damienâ¦ I do not remember the name, but it has a name) that thing that you > type âabcâ and it will find > >> - abc > >> - absoluteBinaryCapability > >> - AbstractBlooperContext > >> - etc > >> > >> I think it is a super functionality (and it was fast), that should be > included by default. > >> > >> Esteban > >> > >>> On 10 Jun 2016, at 08:55, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>> > >>> 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> 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> 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." > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > > > >

June 10, 2016

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

by Christophe Demarey

> Le 10 juin 2016 Ã 09:47, Guille Polito <guillermopolito(a)gmail.com> a Ã©crit : > > I use spotter a lot as well. It is actually my default entry point to the system. It superseeded the searches in Nautilus, and most of the searches that I used to start in the workspace. The same for me. Spotter is the fastest path to open a tool, browse a class, etc. My top searches are: classes, implementors, packages I sometime use tools and use more history. (by the way, I often hit history entries by accident) Christophe > The things I look most by name are tools (Menu entries), classes and packages. > > History is of great help and I use it a lot. But it poses a problem sometimes because it alters the order of the results, and you have to wait for the complete search to finish. If you do not do that, it happens what Max explained: you type, hit <down>,<enter> and suddenly the UI refreshed and you finished doing something else. > > Also, regarding the ordering of results, sometimes It bothers me that they are sorted by category and not by relevance of the item. I'll explain myself with a concrete case: > - open spotter > - type "Process" > > you get first two #menu items and then the #classes, containing the class Process. I would have expected here to show first the element that matched the most or with more relevance, regardless it's category. > > Question: Does spotter adapt to it's usage? Besides history, does it learn what are the items with more relevance from previous usages in the same session? > > Also, from the top of my head there is at least one use case that I cannot yet replace with spotter, and I have to use a normal workspace/playground to do it => browse senders or implementors. While i use senders/implementors search in spotter, sometimes I want to *browse* them to be able to look at them, and interact with the code. However, from spotter I can only observe results but not edit them. > > Guille > > -------- Original Message -------- >> and just another thing :) >> >> I think search patterns are a bit naive now (just matching begin of line). We could benefit from regex searchs and/or that search stuff made by Damienâ¦ I do not remember the name, but it has a name) that thing that you type âabcâ and it will find >> - abc >> - absoluteBinaryCapability >> - AbstractBlooperContext >> - etc >> >> I think it is a super functionality (and it was fast), that should be included by default. >> >> Esteban >> >>> On 10 Jun 2016, at 08:55, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>> 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 < <mailto:estebanlm@gmail.com>estebanlm(a)gmail.com <mailto:estebanlm@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 < <mailto:maxleske@gmail.com>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 < <mailto:tudor@tudorgirba.com>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 >>>>>> >>>>>> -- >>>>>> <http://www.tudorgirba.com/>www.tudorgirba.com <http://www.tudorgirba.com/> >>>>>> <http://www.feenk.com/>www.feenk.com <http://www.feenk.com/> >>>>>> >>>>>> "Value is always contextual." >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> >

June 10, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60075 Home: https://github.com/pharo-project/pharo-core

June 10, 2016

[pharo-project/pharo-core] 5fe187: 60075

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 5fe1879036aaa6f2824b3062a6b8be0f6bf6d666 https://github.com/pharo-project/pharo-core/commit/5fe1879036aaa6f2824b3062… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-10 (Fri, 10 Jun 2016) Changed paths: M FileSystem-Core.package/FileReference.class/class/instance creation/newTempFilePrefix_suffix_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60074.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60075.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60074.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60075.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R System-Sources.package/ProcessAndSessionLocalSourcesFileArray.class/README.md R System-Sources.package/ProcessAndSessionLocalSourcesFileArray.class/definition.st M System-Sources.package/SourceFileArray.class/definition.st M System-Sources.package/SourceFileArray.class/instance/initialization/initialize.st R System-Sources.package/SourceFileArray.class/instance/private - accessing file streams/localProcessReadStreamAtFileIndex_atPosition_ifPresent_ifAbsent_.st R System-Sources.package/SourceFileArray.class/instance/private - copying/localProcessReadOnlyCopy.st A System-Sources.package/SourceFileArray.class/instance/private/closeFileArray_.st M System-Sources.package/SourceFileArray.class/instance/public - file system operations/close.st M System-Sources.package/SourceFileArray.class/instance/public - file system operations/ensureOpen.st R System-Support.package/ProcessAndSessionLocalVariable.class/README.md R System-Support.package/ProcessAndSessionLocalVariable.class/definition.st R System-Support.package/ProcessAndSessionLocalVariable.class/instance/accessing/value.st R System-Support.package/ProcessAndSessionLocalVariable.class/instance/evaluating/value_.st A System-Support.package/SmalltalkImage.class/class/initialization/shutDown_.st M Tool-FileList.package/FileList.class/class/menu/contentMenu_.st Log Message: ----------- 60075 18462 FileReference>>newTempFilePrefix:suffix: https://pharo.fogbugz.com/f/cases/18462 18458 fall back debug menu in FileLists preview pane context menu https://pharo.fogbugz.com/f/cases/18458 18456 Add readOnlyQueue to SourceFilesArray https://pharo.fogbugz.com/f/cases/18456 http://files.pharo.org/image/60/60075.zip

June 10, 2016

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

by Sven Van Caekenberghe

> On 10 Jun 2016, at 09:47, Guille Polito <guillermopolito(a)gmail.com> wrote: > > I use spotter a lot as well. Me too ! > It is actually my default entry point to the system. It superseeded the searches in Nautilus, and most of the searches that I used to start in the workspace. Indeed, same here. > The things I look most by name are tools (Menu entries), classes and packages. > > History is of great help and I use it a lot. But it poses a problem sometimes because it alters the order of the results, and you have to wait for the complete search to finish. If you do not do that, it happens what Max explained: you type, hit <down>,<enter> and suddenly the UI refreshed and you finished doing something else. > > Also, regarding the ordering of results, sometimes It bothers me that they are sorted by category and not by relevance of the item. I'll explain myself with a concrete case: > - open spotter > - type "Process" > > you get first two #menu items and then the #classes, containing the class Process. I would have expected here to show first the element that matched the most or with more relevance, regardless it's category. > > Question: Does spotter adapt to it's usage? Besides history, does it learn what are the items with more relevance from previous usages in the same session? Some simple learning would be super cool. > Also, from the top of my head there is at least one use case that I cannot yet replace with spotter, and I have to use a normal workspace/playground to do it => browse senders or implementors. While i use senders/implementors search in spotter, sometimes I want to *browse* them to be able to look at them, and interact with the code. However, from spotter I can only observe results but not edit them. Yes, that is indeed something that I miss as well: browsing them all. Sven > Guille > > -------- Original Message -------- >> and just another thing :) >> >> I think search patterns are a bit naive now (just matching begin of line). We could benefit from regex searchs and/or that search stuff made by Damienâ¦ I do not remember the name, but it has a name) that thing that you type âabcâ and it will find >> - abc >> - absoluteBinaryCapability >> - AbstractBlooperContext >> - etc >> >> I think it is a super functionality (and it was fast), that should be included by default. >> >> Esteban >> >>> On 10 Jun 2016, at 08:55, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> 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> 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> 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." >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> >

June 10, 2016

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

by Guille Polito

I use spotter a lot as well. It is actually my default entry point to the system. It superseeded the searches in Nautilus, and most of the searches that I used to start in the workspace. The things I look most by name are tools (Menu entries), classes and packages. History is of great help and I use it a lot. But it poses a problem sometimes because it alters the order of the results, and you have to wait for the complete search to finish. If you do not do that, it happens what Max explained: you type, hit <down>,<enter> and suddenly the UI refreshed and you finished doing something else. Also, regarding the ordering of results, sometimes It bothers me that they are sorted by category and not by relevance of the item. I'll explain myself with a concrete case: - open spotter - type "Process" you get first two #menu items and then the #classes, containing the class Process. I would have expected here to show first the element that matched the most or with more relevance, regardless it's category. Question: Does spotter adapt to it's usage? Besides history, does it learn what are the items with more relevance from previous usages in the same session? Also, from the top of my head there is at least one use case that I cannot yet replace with spotter, and I have to use a normal workspace/playground to do it => browse senders or implementors. While i use senders/implementors search in spotter, sometimes I want to *browse* them to be able to look at them, and interact with the code. However, from spotter I can only observe results but not edit them. Guille -------- Original Message -------- > and just another thing :) > > I think search patterns are a bit naive now (just matching begin of > line). We could benefit from regex searchs and/or that search stuff > made by Damienâ¦ I do not remember the name, but it has a name) that > thing that you type âabcâ and it will find > - abc > - absoluteBinaryCapability > - AbstractBlooperContext > - etc > > I think it is a super functionality (and it was fast), that should be > included by default. > > Esteban > >> On 10 Jun 2016, at 08:55, Esteban Lorenzano <estebanlm(a)gmail.com >> <mailto:estebanlm@gmail.com>> wrote: >> >> 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 >>> <mailto:estebanlm@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

and just another thing :) I think search patterns are a bit naive now (just matching begin of line). We could benefit from regex searchs and/or that search stuff made by Damienâ¦ I do not remember the name, but it has a name) that thing that you type âabcâ and it will find - abc - absoluteBinaryCapability - AbstractBlooperContext - etc I think it is a super functionality (and it was fast), that should be included by default. Esteban > On 10 Jun 2016, at 08:55, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > 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 <mailto:estebanlm@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

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