June 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] IMPORTANT: Proposal to create a github team for Voyage and MongoTalk

by Todd Blanchard

'NoSQL' covers a lot of ground. I don't suppose anyone has done a redis interface? > On Jun 9, 2016, at 15:54, Martin Dias <tinchodias(a)gmail.com> wrote: > > > > On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > But wellâ¦ is done :) > behold the new pharo-nosql organisation! > > https://github.com/pharo-nosql <https://github.com/pharo-nosql> > > already running with travis ci (appveyor is on the way, in fact is done, I just need to modify the vm :P) > > btw, Martin: your replicaset changes broke mongotalk tests :P (first immediate positive feedback from moving there) > > pull request created! > > > Esteban > >> On 09 Jun 2016, at 20:20, Esteban A. Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: >> >> 2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias(a)gmail.com <mailto:tinchodias@gmail.com>>: >>> On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code(a)gmail.com <mailto:yanni.code@gmail.com>> wrote: >>>> On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> >>>> wrote: >> >>>>> And finally, more we move, more we have encourage to improve the tools, >>>>> complete the missing partsâ¦ >> >>>> About a year ago I tried to use git for a project, but gave up because it >>>> was not clear to me what tools and processes should be used. Having an >>>> active project to follow (like PharoNoSQL) would maybe fill in the missing >>>> git knowledge I need. >>>> >>> Yes, the same happened to me. >> >> Ditto here. >> >> I do use GitHub and Bitbucket for other projects, with branches, pull >> requests and all the jazz. >> But with Pharo I only used filetree, and I'm never know exactly how >> the changes are handled, what's all the metadata thing about, and so >> on. But maybe because I commited the same package to both an MC repo >> (STHub) and Git. >> >> Regards! >> >> >> Esteban A. Maringolo >> > >

June 10, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] Enterprise Pharo book is released!

by Alexandre Bergel

Excellent news!! Alexandre > On Jun 10, 2016, at 9:36 AM, Damien Cassou <Damien.Cassou(a)inria.fr> wrote: > > > Great news everyone: the new Pharo book is finally out! "Enterprise > Pharo: a Web Perspective" covers libraries and frameworks for > enterprises, and in particular those doing web development. > > You can download it for free or buy a printed version : > > > http://books.pharo.org/enterprise-pharo/ > > > Other books are available at http://books.pharo.org/. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 10, 2016

Re: [Pharo-dev] [ANN] Enterprise Pharo book is released!

by Tudor Girba

Great news! Cheers, Doru > On Jun 10, 2016, at 3:36 PM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > > Great news everyone: the new Pharo book is finally out! "Enterprise > Pharo: a Web Perspective" covers libraries and frameworks for > enterprises, and in particular those doing web development. > > You can download it for free or buy a printed version : > > > http://books.pharo.org/enterprise-pharo/ > > > Other books are available at http://books.pharo.org/. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal."

June 10, 2016

[ANN] Enterprise Pharo book is released!

by Damien Cassou

Great news everyone: the new Pharo book is finally out! "Enterprise Pharo: a Web Perspective" covers libraries and frameworks for enterprises, and in particular those doing web development. You can download it for free or buy a printed version : http://books.pharo.org/enterprise-pharo/ Other books are available at http://books.pharo.org/. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

June 10, 2016

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

by Tudor Girba

Hi, > On Jun 10, 2016, at 10:24 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 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). Some scoping can be easily added. For example, if we would add a Senders processor for a Package we could scope it for that package. To scope this for a group of packages is where things become more interesting. The current idea is to allow each processor to provide a typed group and provide processors in that class. For example, diving-in-category of a package category, could provide us not a plain collection, but a PackageCollection (or PackageGroup), and there we could again have processors like Senders. This is something we need to play with some more. Any related ideas? Cheers, Doru > 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." > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

June 10, 2016

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

by Tudor Girba

Hi, Indeed, this was a question I asked myself as well. And I think I figured out a way to filter most of the false positives out. The analysis goes like this: If you have a misstep, you likely want to restart Spotter and search again. In this situation it is likely that the distance between the end of the misstepped session and the starting of a new session is less than 5 seconds. For safety, letâs consider 20 seconds. To put it in perspective, 90% of Spotter sessions have less than 20 seconds. So, if we filter out all sessions that have another session coming after less than 20 seconds we get this: 'Classes'->40 'Implementors'->38 'History'->33 'Packages'->20 'Menu'->18 'Messages'->18 'Catalog Projects'->12 'Instance methods'->10 'Senders'->7 'References'->5 'Playground named pages'->5 'Pragmas'->4 'Playground cached pages'->3 'Selectors'->3 'Super instance methods'->3 'Help topics'->3 'ws.stfx.eu'->2 'Examples'->2 'GitHub Baselines'->2 'Class methods'->2 'Global variables'->1 'All subclasses'->1 'Files'->1 'Monticello Repositories'->1 'Metacello Configurations'->1 'Class instance variables'->1 'Items'->1 'Help contents'->1 'Productions'->1 'Dirty Monticello packages'->1 There are very little changes. History is still number 3, and Menu is in top 5. Cheers, Doru > On Jun 10, 2016, at 8:42 AM, 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." >> >> >> >> > -- www.tudorgirba.com www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

June 10, 2016

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

by Tudor Girba

Hi, Thanks for the feedback. More inline. > On Jun 10, 2016, at 9:47 AM, Guille Polito <guillermopolito(a)gmail.com> wrote: > > 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. This is indeed an interesting direction, but we are not ready for it yet because Spotter does not have a scoring mechanism that would work between distinct categories. Ideas in this space would be welcome. > 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? It has no learning mechanism built in. > 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. Indeed. There is an open issue for allowing editing in the preview. However, even if you can edit, we will still have the problem of the feedback to the list. For example, suppose you are looking for senders of #x, and you modify the code to no longer use #x. In this case you would want the list to update. We do not have that feedback loop. This is an area where again we would benefit from ideas of how to implement such a thing in a generic way. In any case, in the current form, Spotter is not appropriate for longer interaction because of its floating/transient nature. We need something else. It is already possible to transform a Spotter in a regular window, but we still need to play with this idea more until we get to an improved solution. Cheers, Doru > 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." >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > -- www.tudorgirba.com www.feenk.com "One cannot do more than one can do."

June 10, 2016

A question on the catalog

by Esteban Lorenzano

Hi, I was doing a pass on the catalogâ¦ I think is very negative that non-documented projects appear thereâ¦ because most people does not know what does projects are about and newcomers will find weird a project install tool with lots of projects without any description. So I was thinking on put an option âshow allâ and hide those projects by defaultâ¦ but now I think those projects SHOULD NOT BE VISIBLE AT ALL, as a way of: - offer better experience to non-power users, and - encourage people to actually document their projectsâ¦ is very annoying to have so much of them without any documentation. What do you think? cheers, Esteban

June 10, 2016

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

by Tudor Girba

Hi, > On Jun 10, 2016, at 10:55 AM, Ben Coman <btc(a)openInWorld.com> wrote: > > On Fri, Jun 10, 2016 at 4:11 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> 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 often worry one day someone will remove the Senders <meta-n> and > Implementors <meta-m> windows since Spotter *mostly* supersedes them, > but actually they fill different needs. Spotter is transient. It > opens quickly from anywhere, helps you go to what you want and then it > hides itself away. But often I have several different Senders / > Implementers windows open for hours at a time, and its nice to flip > back and forth between implementations and make edits there. For > example, I want to add a halt in every implementer. > > In the past I asked editing capability in the Spotter code window, > but with Spotters transitive nature maybe is not the best place to > make edits. Exactly :). In the current form, Spotter serves the role of opening a conversation with objects (or code). It is not yet enough for sustaining that conversation. So, we still need a solution for working with a subset of elements for longer periods of time. Cheers, Doru > cheers -ben > >> >> 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." -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

June 10, 2016

changes in latest Athens configuration

by Nicolai Hess

ConfigurationOfAthens project version:'3.9.6' see case 18445 <https://pharo.fogbugz.com/f/cases/18445/ConfigurationOfAthens-is-not-in-syn…> ConfigurationOfAthens is not in sync with current Pharo packages Why do we merge compositing modes with "paint options"? I would consider a compositing mode as a "mode" for current drawing operations and the antialiasing setting is only a "hint" for the backend, it may be completly ignored. Or am I confused with the font rendering antialiasing hint? Can we paint by set compositing mode do paint set different compositing set antialiasing mode do paint set different antialiasing mode do paint does it work that way (and would it make sense)? nicolai

June 10, 2016